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

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

Chapter 1. Preparing to install Red Hat OpenShift GitOps

Read the following information about sizing requirements and prerequisites before you install Red Hat OpenShift GitOps on OpenShift Container Platform. Sizing requirements also provides the sizing details for the default ArgoCD instance that is instantiated by the Red Hat OpenShift GitOps Operator.

1.1. Sizing requirements for GitOps
复制链接

Red Hat OpenShift GitOps is a declarative way to implement continuous deployment for cloud-native applications. Through GitOps, you can define and configure the CPU and memory requirements of your application.

Every time you install the Red Hat OpenShift GitOps Operator, the resources on the namespace are installed within the defined limits. If the default installation does not set any limits or requests, the Operator fails within the namespace with quotas. Without enough resources, the cluster cannot schedule ArgoCD related pods. The following table details the resource requests and limits for the default workloads:

Expand
WorkloadCPU requestsCPU limitsMemory requestsMemory limits

openshift-gitops-application-controller

250m

2

1024Mi

2048Mi

applicationset-controller

250m

2

512Mi

1024Mi

openshift-gitops-server

125m

500m

128Mi

256Mi

openshift-gitops-repo-server

250m

1

256Mi

1024Mi

openshift-gitops-redis

250m

500m

128Mi

256Mi

openshift-gitops-dex-server

250m

500m

128Mi

256Mi

openshift-gitops-redis-ha-haproxy

250m

500m

128Mi

256Mi

Optionally, you can also use the ArgoCD custom resource with the oc command to see the specifics and modify them: 

oc edit argocd <name of argo cd> -n namespace
Copy to Clipboard Toggle word wrap

1.1.1. Sizing requirements for argocd-redis
复制链接

During the capacity planning stage for your application in the Red Hat OpenShift GitOps Operator, you must ensure that an adequate amount of resources, such as memory, CPU, and storage, are allocated for the argocd-redis pod.

The default memory limit for the Redis pod might not be enough to manage a large number of resources. In these instances, you must increase the memory limit, monitor the memory metrics, and change the memory configuration while the application deployment scales up.

The following command shows the example of the memory configuration for a Redis pod in the openshift-gitops namespace: 

$ oc get argocd -n openshift-gitops openshift-gitops -o json | jq '.spec.redis.resources'
Copy to Clipboard Toggle word wrap

Example Output

{
    "limits": {
1 

        "cpu": "500m",
        "memory": "256Mi"
  },
  "requests": {
2 

    "cpu": "250m",
    "memory": "128Mi"
  }
}
Copy to Clipboard Toggle word wrap

1
The highest resource limit threshold allocated to the pod.
2
The lowest resource limit threshold allocated to the pod.

The following example command changes the memory configuration for a Redis pod. The highest resource limit threshold is set to 8 GiB and the lowest is set to 256 MiB. 

$ oc patch argocd -n openshift-gitops openshift-gitops --type json -p '[{"op": "replace", "path":  \
  "/spec/redis/resources/limits/memory", "value": "8Gi"}, {"op": "replace", "path": \
  "/spec/redis/resources/requests/memory", "value": "256Mi"}]'
Copy to Clipboard Toggle word wrap

Example Output

argocd.argoproj.io/openshift-gitops patched
Copy to Clipboard Toggle word wrap

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

Theme

© 2025 Red Hat