Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-390

Honour CVO/API server non-upgradable scenarios in HC

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • None
    • None
    • None
    • Hypershift Sprint 10, Hypershift Sprint 12, Hypershift Sprint 13, Hypershift Sprint 15, Hypershift Sprint 16
    • 0

      Context:

      There's multiple scenarios where a cluster might not be upgradable:

      • The API server decides is not upgradable based on deprecated fields.

      DoD:

      We should honour this decision and watch this condition when a new release image intent is expressed in the HC. Then we should communicate non-upgradability this in the HC conditions.

      This could also be used to signal release changes that would break kube skew policy.

      We should allow forcing an upgrade even if the status says it's not upgradable

              sjenning Seth Jennings
              agarcial@redhat.com Alberto Garcia Lamela
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: