Enable control planes of different minor versions to run on a single Hypershift management cluster.

Epic Goal

• Enable a single management cluster to run hosted control planes of different OpenShift minor versions.
• Constraint: both management and guest cluster must have the minimum supported version for Hypershift.

Why is this important?

• In a single management cluster there will be control planes in different versions depending on their upgrade cycle. It is not expected that the management cluster be upgraded at the same cadence as the guest clusters or that all guest clusters be upgraded at the same time.
• Control plane components and their corresponding configuration will differ across OpenShift minor versions.

Scenarios

1. Create guest clusters at different minor versions (ie. 4.9.5 and 4.10.0) on the same management cluster.

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):

1. …

Open questions::

1. …

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>