Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2085

Ability to change `apiVIP` and `ingressVIP` on a deployed cluster

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Installer
    • False
    • False
    • undefined

      1. Proposed title of this feature request

      Ability to change  `apiVIP` and `ingressVIP` on a deployed cluster

      2. What is the nature and description of the request?

      (Shift On Stack in this specific case.)

      Ability to change the `apiVIP` and `ingressVIP` parameters defined in the install-config.yaml on a live cluster, without redeploying the cluster, so to adapt to different LBs setups.

      3. Why does the customer need this? (List the business requirements here)

      As we understand, *.apps.<clustername> in case of Shiftonstack is hardcoded in Keepalived pods, so there's no way to change it. Surely this scenario (changing `apiVIP` and `ingressVIP` is not supported).

      Reusing the VIP is not an option.

      Business justification -> If the customer will decide to stop the use of a specific LB in prod, and for example wants to switch to another, they need to be able to change the VIPs without users impact: Meaning to setup both LBs side by side with a dedicated VIP and switching the DNS to the new VIP.

      Ideally would be nice to have some kind of CM at cluster level to change these parameters.

      4. List any affected packages or components.

      • OpenShift core
      • ingress-controller
      • ingress-operator
      • QA tests

            grosenbe-redhat.com Gil Rosenberg
            rhn-support-fsoppels Fabrizio Soppelsa
            Votes:
            7 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated: