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

Remove ClusterSet and ClusterSetBinding API version v1alpha1

XMLWordPrintable

    • Remove ClusterSet and ClusterSetBinding API version v1alpha1
    • False
    • None
    • False
    • To Do
    • ACM-1613 - ManagedClusterSet v1beta2 migration plan
    • ACM-1613ManagedClusterSet v1beta2 migration plan
    • 0
    • 0% 0%

      Epic Goal

      • Remove ClusterSet and ClusterSetBinding API version v1alpha1

      Why is this important?

      • We already have ClusterSet ClusterSetBinding v1beta1 version for 3 releases. It should be safe to remove the alpha version.

      Scenarios

      1. ManagedClusterSet and ManagedClusterSetBinding v1alpha1 version is removed from API

      Acceptance Criteria

      • Release note included about version removal
      • Documentation updated to use newest version
      • Technical enablement covers version removal, and which version to use
      • Tests across development and QE are updated

      Dependencies (internal and external)

      1. None

      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>

            leyan@redhat.com Le Yang
            yuhe@redhat.com Yuanyuan He
            Yuanyuan He Yuanyuan He
            Le Yang Le Yang
            Qiu Jian Qiu Jian
            Sho Weimer Sho Weimer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: