Skip to content

Commit 3ee4d60

Browse files
authored
Merge pull request #48895 from DebarghoGhosh/clarify-scope-of-infra-4319
RHDEVDOCS-4319 - Clarify scope of infra
2 parents da54346 + 3a78739 commit 3ee4d60

File tree

2 files changed

+23
-5
lines changed

2 files changed

+23
-5
lines changed

cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,13 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
You can use infrastructure nodes to isolate infrastructure workloads for two primary purposes:
9+
You can use infrastructure nodes to prevent additional billing cost against subscription counts.
1010

11-
* Prevent incurring billing costs against subscription counts.
12-
* Separate maintenance and management.
11+
You can use the {product-title} to run certain workloads on infrastructure nodes installed by the {gitops-title} Operator. This comprises the workloads that are installed by the {gitops-title} Operator by default in the `openshift-gitops` namespace, including the default Argo CD instance in that namespace.
12+
13+
[NOTE]
14+
====
15+
Any other Argo CD instances installed to user namespaces are not eligible to run on Infrastructure nodes.
16+
====
1317

1418
include::modules/go-add-infra-nodes.adoc[leveloffset=+1]

modules/go-add-infra-nodes.adoc

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,21 @@
44

55
:_content-type: PROCEDURE
66
[id="add-infra-nodes_{context}"]
7-
= Adding infrastructure nodes
7+
= Moving GitOps workloads to infrastructure nodes
8+
9+
You can move the default workloads installed by the {gitops-title} to the infrastructure nodes. The workloads that can be moved are:
10+
11+
* `kam deployment`
12+
* `cluster deployment` (backend service)
13+
* `openshift-gitops-applicationset-controller deployment`
14+
* `openshift-gitops-dex-server deployment`
15+
* `openshift-gitops-redis deployment`
16+
* `openshift-gitops-redis-ha-haproxy deployment`
17+
* `openshift-gitops-repo-sever deployment`
18+
* `openshift-gitops-server deployment`
19+
* `openshift-gitops-application-controller statefulset`
20+
* `openshift-gitops-redis-server statefulset`
21+
822
923
.Procedure
1024

@@ -20,7 +34,7 @@ $ oc label node <node-name> node-role.kubernetes.io/infra=
2034
----
2135
$ oc edit gitopsservice -n openshift-gitops
2236
----
23-
. In the `GitOpsService` CR file, add `runOnInfra` toggle to the `spec` section and set it to `true`:
37+
. In the `GitOpsService` CR file, add `runOnInfra` field to the `spec` section and set it to `true`. This field moves the workloads in `openshift-gitops` namespace to the infrastructure nodes:
2438
+
2539
[source,yaml]
2640
----

0 commit comments

Comments
 (0)