Chapter 2. Configure resource requests and limits for GitOps plugin components

Procedure

1. Get the GitOpsService CR by running the following command.

   $ oc get gitopsservice -A

   Example output:

   NAMESPACE          NAME      AGE
   openshift-gitops   cluster   5d

2. Edit the GitOpsService CR by running the following command.

   $ oc edit gitopsservice cluster -n openshift-gitops

3. In the .spec.consolePlugin section, add the .backend.resources and .gitopsPlugin.resources fields. These sections define requests and limits for CPU and memory.

   Example configuration:

   apiVersion: pipelines.openshift.io/v1alpha1
   kind: GitOpsService
   metadata:
     name: cluster
   spec:
     consolePlugin:
       backend:
         resources:
           limits:
             cpu: 100m
             memory: 1Gi
           requests:
             cpu: 100m
             memory: 1Gi
       gitopsPlugin:
         resources:
           limits:
             cpu: 200m
             memory: 2Gi
           requests:
             cpu: 100m
             memory: 1Gi

4. Save and exit the editor.

   After you update the GitOpsService CR, the GitOpsService controller applies the specified resource requests and limits to the backend and the GitOps plugin components.

1. Verify the resource configuration:

   $ oc describe pod <pod-name> -n openshift-gitops

   Look for the Limits and Requests sections in the output and ensure they match your configuration.