이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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


You can configure CPU and memory resource requests and limits for the GitOps console plugin and its backend cluster components. Resource allocation is controlled through the GitOpsService custom resource (CR) and can be modified during creation or update. The GitOpsService controller reconciles both the backend and plugin resources. You can define separate or identical resource configurations for each component, depending on your requirements. This feature is beneficial for scenarios requiring specific resource requests and limits for components, which can effectively address memory and performance issues.

2.1. Enabling the GitOpsService custom resource

To enable resource configuration for the GitOps plugin components, specify the .spec.consolePlugin.backend.resources field for the backend component and the .spec.consolePlugin.gitopsPlugin.resources field for the GitOps console plugin. The resources section defines the requests (minimum resources) and limits (maximum resources) for each component.

Prerequisites

  • You have logged in to the OpenShift Container Platform cluster as an administrator.
  • You have installed the Red Hat OpenShift GitOps Operator on your OpenShift Container Platform cluster.

Procedure

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

    $ oc get gitopsService -A
    Copy to Clipboard Toggle word wrap
  2. Edit the GitOpsService CR by running the following command.

    $ oc edit gitopsservice cluster -n openshift-gitops
    Copy to Clipboard Toggle word wrap
  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
    Copy to Clipboard Toggle word wrap

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

Verification

  1. Ensure that the requests and limits values in the pod specifications match the configuration you have added to the GitOpsService CR.

2.2. Behavior of resource configuration

The following information describes how the GitOpsService controller applies resource values defined in the GitOpsService custom resource (CR).

  • Specified values: When you define resource values in the GitOpsService CR, the GitOpsService controller applies those values only to the components you specify. For example, if you configure resource limits only for the backend, those values apply to the backend deployment and not to the plugin.
  • Default values: If you do not define any resource values in the GitOpsService custom resource, the GitOpsService controller applies default values to all components.
Expand
Table 2.1. Default resource values
ComponentRequest CPURequest MemoryLimit CPULimit Memory

Backend

250m

128Mi

500m

256Mi

GitOps plugin

250m

128Mi

500m

256Mi

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat