Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-1245

Allow setting replicas for argocd-repo-server and argocd-server

XMLWordPrintable

    • 5
    • False
    • False
    • Hide
      * With this update, the Operator enables you to specify the number of desired replicas for the `argocd-server` and `argocd-repo-server` components by setting the `.spec.server.replicas` and `.spec.repo.replicas` attributes in the Argo CD custom resource, respectively. If the horizontal pod autoscaler (HPA) is configured for the `argocd-server` components, it takes precedence over the Argo CD custom resource attributes. link:https://issues.redhat.com/browse/GITOPS-1245[GITOPS-1245]
      Show
      * With this update, the Operator enables you to specify the number of desired replicas for the `argocd-server` and `argocd-repo-server` components by setting the `.spec.server.replicas` and `.spec.repo.replicas` attributes in the Argo CD custom resource, respectively. If the horizontal pod autoscaler (HPA) is configured for the `argocd-server` components, it takes precedence over the Argo CD custom resource attributes. link: https://issues.redhat.com/browse/GITOPS-1245 [ GITOPS-1245 ]
    • GITOPS Sprint 209, GITOPS Sprint 208, GITOPS Sprint 210

      As a user of OpenShift GitOps, I want to be able to control the number of replicas for the argocd-server and argocd-repo-server workloads. As these workloads are stateless, the replica count can be increased to distribute the workload better among pods.

      This can be implemented independently of a full-fledged HA setup.

      Acceptance criteria:

      • Options exist in the ArgoCD CR spec to set the number of replicas for argocd-server and argocd-repo-server workloads respectively
      • The default value - if option is not specified - should be 1 replica
      • The Operator reconciles the setting into actual workloads
      • If HPA is configured for argocd-server, its setting should take precedence and replica setting for argocd-server should be ignored

            [GITOPS-1245] Allow setting replicas for argocd-repo-server and argocd-server

            Errata Tool added a comment -

            This issue has been addressed in the following products:

            Red Hat OpenShift GitOps 1.4

            Via RHEA-2022:0264 https://access.redhat.com/errata/RHEA-2022:0264

            Errata Tool added a comment - This issue has been addressed in the following products: Red Hat OpenShift GitOps 1.4 Via RHEA-2022:0264 https://access.redhat.com/errata/RHEA-2022:0264

            Rolfe Dlugy-Hegwer added a comment -

            Please provide further feedback on this release note item in the following PR: https://github.com/openshift/openshift-docs/pull/40738/files

            Further changes to the release note in this Jira will not be migrated to the PR.

            Rolfe Dlugy-Hegwer added a comment - Please provide further feedback on this release note item in the following PR: https://github.com/openshift/openshift-docs/pull/40738/files Further changes to the release note in this Jira will not be migrated to the PR.

            Borja Luengo (Inactive) added a comment - - edited

            rdlugyhe 
            We approve it from QE

            Borja Luengo (Inactive) added a comment - - edited rdlugyhe   We approve it from QE

            Jann Fischer added a comment -

            rdlugyhe Your proposal LGTM.

            bluengop@redhat.com rjeczkow rhn-support-vab Please share your concerns or approve from QE side please.

            Jann Fischer added a comment - rdlugyhe Your proposal LGTM. bluengop@redhat.com rjeczkow rhn-support-vab Please share your concerns or approve from QE side please.

            Rolfe Dlugy-Hegwer added a comment - - edited

            jfischer@redhat.com, rescott1, please review the following proposed revision:

             

            With this update, the Operator enables you to specify the number of desired replicas for the `argocd-server` and `argocd-repo-server` components by setting the `.spec.server.replicas` and `.spec.repo.replicas` attributes in the Argo CD custom resource, respectively. If the horizontal pod autoscaler (HPA) is configured for the `argocd-server` components, it takes precedence over the Argo CD custom resource attributes.

            Rolfe Dlugy-Hegwer added a comment - - edited jfischer@redhat.com , rescott1 , please review the following proposed revision:   With this update, the Operator enables you to specify the number of desired replicas for the `argocd-server` and `argocd-repo-server` components by setting the `.spec.server.replicas` and `.spec.repo.replicas` attributes in the Argo CD custom resource, respectively. If the horizontal pod autoscaler (HPA) is configured for the `argocd-server` components, it takes precedence over the Argo CD custom resource attributes.

            Jann Fischer added a comment -

            rdlugyhe This has a release note item, please check.

            Jann Fischer added a comment - rdlugyhe This has a release note item, please check.

            Regina Scott (Inactive) added a comment -

            PR here: https://github.com/argoproj-labs/argocd-operator/pull/458

            Regina Scott (Inactive) added a comment - PR here:  https://github.com/argoproj-labs/argocd-operator/pull/458

              rescott1 Regina Scott (Inactive)
              jfischer@redhat.com Jann Fischer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: