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

MCE installation pre-check required for existing hosted clusters

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • MCE 2.8.0
    • None
    • HyperShift, Installer
    • None
    • MCE installation pre-check for existing hosted clusters
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1650 - Comprehensive testing strategy for HCP to ensure compatibility across versions and environments
    • OCPSTRAT-1650Comprehensive testing strategy for HCP to ensure compatibility across versions and environments

      Epic Goal

      The goal of this epic is to help cluster service providers or cluster administrators determine whether upgrading the MCE to a newer version is safe or not based on the current inventory of "local" hosted clusters.

      Why is this important?

      Although the version requirements of the hypershift operator are documented, there will always to customers that often forget these requirements at the time of MCE upgrades and get into a situation where recovering from problems after MCE upgrade with a lot of Red Hat support and manual work. We want to prevent this potential customer pain-point.

      Scenarios

      • You have MCE 2.7 with the hypershift operator 4.17
      • Since the hypershift operator allows you to create up to n-4 hosted clusters, some of the local hosted clusters in this MCE hub cluster are OCP 4.13.
      • You upgrade to MCE 2.8 which upgrades the hypershift operator to 4.18 level.
      • Now the hypershift operator 4.18's n-4 support reaches only down to OCP 4.14. This means the hypershift operator cannot lifecycle the existing OCP 4.13 hosted clusters.

       
      We want to avoid this situation where upgrading MCE causes these n-4 hosted cluster to go outside the supported version range.

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      1. Do we do this type of checking for standalone managed OCP clusters?

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

              dbennett@redhat.com Disaiah Bennett
              rokejungrh Roke Jung
              Thuy Nguyen Thuy Nguyen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: