Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-24567 As an Installer developer, I want to modify the MCE webhook to ensure that HyperShift and CAPI components are mutually exclusive
  3. ACM-25178

Test that HyperShift and CAPI components are mutually exclusive

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • QE
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Installer Sprint 2025-68, Installer Sprint 2025-69, Installer Sprint 2025-70

       Test cases

      1. The hypershift and hypershift-local-hosting components are enabled by default and cluster-api and cluster-api-provider-aws components are disabled by default in MCE. Ensure that I can enable cluster-api and cluster-api-provider-aws components only if the hypershift components are disabled.
      2. When cluster-api and cluster-api-provider-aws components are enabled, ensure that the components work. 
        1. Disabling the hypershift components leave the CAPI and CAPA related CRDs behind. 
        2. Enabling cluster-api and cluster-api-provider-aws components will upgrade the remaining CRDs from the disabled hypershift components so CAPI and CAPA will work without having to manually clean up the CRDs after disabling hypershift components but before enabling the CAPI/CAPA components.
        3. Verification: do some CAPI/CAPA related operations like provisioning a cluster with it.
      3. Continuing from TC2, when a user wants to disable CAPI/CAPA and re-enable the hypershift components, 
        1. Disabling the CAPI/CAPA components leave the CAPI and CAPA related CRDs behind. 
        2. Re-enabling the hypershift components tries to install (downgrade) its version of CRDs. Downgrading CRDs is not allowed in kubernetes. Therefore, the hypershift operator will fail its hosted cluster operations.
        3. Verifications:
          1. Check that the hypershift operator fails its hosted cluster operations such as creating a new HCP cluster.
          2. Removing the CAPI/CAPA related CRDs before re-enabling the hypershift component resolves the problem. 
          3. We will have to document this case and which CRDs to clean up in this flow.
      4. Similar to TC3, I have MCE with CAPI/CAPA components enabled. Now I uninstall MCE and re-install MCE.
        1. Uninstallation with CAPI/CAPA enabled will leave their CRDs in the cluster.
        2. Re-installing MCE will enable hypershift components by default and CAPI/CAPA disabled. In this flow, the hypershift operator will fail because of the reason in TC3.
        3. Verifications:
          1. Check that the hypershift operator fails its hosted cluster operations such as creating a new HCP cluster.
          2. Removing the CAPI/CAPA related CRDs before re-installing MCE resolves the problem. 
          3. We will have to document this case and which CRDs to clean up in this flow.

              rh-ee-msmigiel Matthew Smigielski
              rokejungrh Roke Jung
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: