Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-42704

Run 2 replicas of active/passive HA hypershift deployments

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, both active and passive high-availability (HA) deployments ran three replicas instead of the required two. As a result, control planes contain more pods than required which led to scaling issues. With this release, the number of replicas in active and passive HA deployments is reduced from three to two. (link:https://issues.redhat.com/browse/OCPBUGS-42704[*OCPBUGS-42704*])

      --------*cause* - Active/passive HA deployments are running 3 replicas when only 2 are necessary
      *consequence - Control planes contain more pods than required, leading to scale issues
      *fix* - Reduce the number of replicas in an active/passive HA deployment from 3 to 2
      *result* - Control planes will contain fewer pods
      Show
      * Previously, both active and passive high-availability (HA) deployments ran three replicas instead of the required two. As a result, control planes contain more pods than required which led to scaling issues. With this release, the number of replicas in active and passive HA deployments is reduced from three to two. (link: https://issues.redhat.com/browse/OCPBUGS-42704 [* OCPBUGS-42704 *]) --------*cause* - Active/passive HA deployments are running 3 replicas when only 2 are necessary *consequence - Control planes contain more pods than required, leading to scale issues *fix* - Reduce the number of replicas in an active/passive HA deployment from 3 to 2 *result* - Control planes will contain fewer pods
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-42100. The following is the description of the original issue:
      —
      Description of problem:

          HyperShift currently runs 3 replicas of active/passive HA deployments such as kube-controller-manager, kube-scheduler, etc. In order to reduce the overhead of running a HyperShift control plane, we should be able to run these deployments with 2 replicas.

In a 3 zone environment with 2 replicas, we can still use a rolling update strategy, and set the maxSurge value to 1, as the new pod would schedule into the unoccupied zone.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              jonesbry Bryan Jones
              openshift-crt-jira-prow OpenShift Prow Bot
              He Liu He Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: