Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2515

Remove CloudControllerOwner condition from CCMO and KCMO

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • CLOUD Sprint 250, CLOUD Sprint 251

      Background

      As part of the migration to external cloud providers, the CCMO and KCMO used a CloudControllerOwner condition to show which controller owned the controllers.

      This is no longer required and can be removed.

      Steps

      • Remove code from CCMO that looks for and gates on the KCMO condition
      • Ensure CCMO clears the condition
      • Ensure KCMO clears the condition

      Stakeholders

      • Cluster Infra
      • Workloads team

      Definition of Done

      • Clusters upgraded to 4.16 do not have a CloudControllerOwner condition set on the KCMO or CCMO ClusterOperators
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

              mimccune@redhat.com Michael McCune
              joelspeed Joel Speed
              Zhaohua Sun Zhaohua Sun
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: