From 413fde6bad807129e4407e68d3a56da418efcbc3 Mon Sep 17 00:00:00 2001 From: Debargho Ghosh Date: Tue, 9 Aug 2022 13:13:34 +0530 Subject: [PATCH] clarify scope of infra made review changes made review changes made review changes changed title added abstract made review changes --- ...-control-plane-workload-on-infra-nodes.adoc | 10 +++++++--- modules/go-add-infra-nodes.adoc | 18 ++++++++++++++++-- 2 files changed, 23 insertions(+), 5 deletions(-) diff --git a/cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc b/cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc index a9369712d529..4c3f848a2924 100644 --- a/cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc +++ b/cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc @@ -6,9 +6,13 @@ include::_attributes/common-attributes.adoc[] toc::[] -You can use infrastructure nodes to isolate infrastructure workloads for two primary purposes: +You can use infrastructure nodes to prevent additional billing cost against subscription counts. -* Prevent incurring billing costs against subscription counts. -* Separate maintenance and management. +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. + +[NOTE] +==== +Any other Argo CD instances installed to user namespaces are not eligible to run on Infrastructure nodes. +==== include::modules/go-add-infra-nodes.adoc[leveloffset=+1] diff --git a/modules/go-add-infra-nodes.adoc b/modules/go-add-infra-nodes.adoc index 317fc03d707b..28e0437832e9 100644 --- a/modules/go-add-infra-nodes.adoc +++ b/modules/go-add-infra-nodes.adoc @@ -4,7 +4,21 @@ :_content-type: PROCEDURE [id="add-infra-nodes_{context}"] -= Adding infrastructure nodes += Moving GitOps workloads to infrastructure nodes + +You can move the default workloads installed by the {gitops-title} to the infrastructure nodes. The workloads that can be moved are: + +* `kam deployment` +* `cluster deployment` (backend service) +* `openshift-gitops-applicationset-controller deployment` +* `openshift-gitops-dex-server deployment` +* `openshift-gitops-redis deployment` +* `openshift-gitops-redis-ha-haproxy deployment` +* `openshift-gitops-repo-sever deployment` +* `openshift-gitops-server deployment` +* `openshift-gitops-application-controller statefulset` +* `openshift-gitops-redis-server statefulset` + .Procedure @@ -20,7 +34,7 @@ $ oc label node node-role.kubernetes.io/infra= ---- $ oc edit gitopsservice -n openshift-gitops ---- -. In the `GitOpsService` CR file, add `runOnInfra` toggle to the `spec` section and set it to `true`: +. 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: + [source,yaml] ----