Skip to content

[enterprise-4.9] RHDEVDOCS-4319 - Clarify scope of infra #49401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 19, 2022
Merged

[enterprise-4.9] RHDEVDOCS-4319 - Clarify scope of infra #49401

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]
18 changes: 16 additions & 2 deletions modules/go-add-infra-nodes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -20,7 +34,7 @@ $ oc label node <node-name> 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]
----
Expand Down