Chapter 1. Running GitOps control plane workloads on infrastructure nodes

Procedure

1. Label existing nodes as infrastructure by running the following command:

   $ oc label node <node-name> node-role.kubernetes.io/infra=

2. Edit the GitOpsService custom resource (CR) to add the infrastructure node selector:

   $ oc edit gitopsservice -n openshift-gitops

3. 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:

   apiVersion: pipelines.openshift.io/v1alpha1
   kind: GitopsService
   metadata:
     name: cluster
   spec:
     runOnInfra: true

4. Optional: Apply taints and isolate the workloads on infrastructure nodes and prevent other workloads from scheduling on these nodes.

   $ oc adm taint nodes -l node-role.kubernetes.io/infra
   infra=reserved:NoSchedule infra=reserved:NoExecute

5. Optional: If you apply taints to the nodes, you can add tolerations in the GitOpsService CR:

   spec:
     runOnInfra: true
     tolerations:
     - effect: NoSchedule
       key: infra
       value: reserved
     - effect: NoExecute
       key: infra
       value: reserved