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

Implement Cluster API CRD Compatibility Checker Integration for HyperShift

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Implement Cluster API CRD Compatibility Checker Integration for HyperShift
    • Product / Portfolio Work
    • OCPSTRAT-1992Migrate MAPI to Cluster API for AWS (GA) - Phase 1
    • 100% To Do, 0% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • None

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • The Cluster CAPI Operator enhancement (https://github.com/openshift/enhancements/pull/1845) introduces a CRD
          Compatibility Checker to manage CRD lifecycles across multiple actors. HCP needs to integrate with this new
          mechanism.
      • Work Items:
          1. Review and understand the CRD Compatibility Checker enhancement proposal
          2. Coordinate CRD management strategy with Cluster CAPI Operator (CCAPIO)
          3. Implement mechanisms to inform CCAPIO about HCP-managed CRDs that should not be overridden
          4. Ensure proper ValidatingWebhookConfiguration setup for CRD compatibility validation
          5. Update HyperShift deployment process to work with CRDCompatibilityRequirement objects
          6. Add appropriate namespace and object selectors for webhook configurations
          7. Test CRD compatibility checks during HyperShift deployments

       

      Why is this important?

      • It is very unlikely we will be able to co-exist, and therefore need a way to handle the upgrade case safely to ensure neither side gets broken during the upgrade

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      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 - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              yanyang@redhat.com Yang Yang
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: