Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-1583

Do not delete HyperShift operator if there are Hosted Clusters

XMLWordPrintable

    • False
    • None
    • False
    • qa-ack
    • Hide
      *Removing the hypershift ManagedClusterAddon does not uninstall the hypershift operator from the managed cluster if there are hosted clusters.
      *Removing the hypershift ManagedClusterAddon should uninstall the hypershift operator from the managed cluster if there is no hosted cluster.
      Show
      *Removing the hypershift ManagedClusterAddon does not uninstall the hypershift operator from the managed cluster if there are hosted clusters. *Removing the hypershift ManagedClusterAddon should uninstall the hypershift operator from the managed cluster if there is no hosted cluster.
    • ACM-635 - HyperShift
    • Sprint 17, SF Ready/Refined Backlog

      Value Statement

      This prevents uninstallation of HyperShift addon operator when there are hosted clusters on the hosting cluster.

       

      Deleting the HyperShift addon operator today deletes the HyperShift operator (if it is installed by the addon), regardless if there are existing Hosted Clusters.

       

      The deletion of the HyperShift addon operator should be enhanced to check if there are existing Hosted Clusters. Only delete the HyperShift operator if there are no Hosted Clusters.

      Acceptance Criteria

      • Removing the hypershift ManagedClusterAddon does not uninstall the hypershift operator from the managed cluster if there are hosted clusters.
      • Removing the hypershift ManagedClusterAddon should uninstall the hypershift operator from the managed cluster if there is no hosted cluster.

      Definition of Done for Engineering Story Owner (Checklist)

      Development Complete

      • Code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • Unit/function tests have been automated and incorporated into build.
      • 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • Create an informative documentation issue using the Customer Portal_doc_issue template, and ensure doc acceptance criteria is met. Link the development issue to the doc issue.
      • Provide input to the QE team, and ensure QE acceptance criteria (established between story owner and QE focal) is met.

      Support Readiness

      • The must-gather script has been updated.

            phwu@redhat.com Philip Wu
            phwu@redhat.com Philip Wu
            Juliana Hsu Juliana Hsu (Inactive)
            Roke Jung Roke Jung
            David Huynh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified