Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

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

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat