Epic Goal

• Design an implement a user-facing API that defines a hosted control plane cluster and related machines. The API should contain enough detail to create and manage the day-2 global configuration of the cluster.

Why is this important?

• The user-facing API defines the requirements for creating and managing Hypershift clusters. This is a net-new feature of hosted control plane clusters. Traditional self-hosted clusters rely on various configuration CRs that live inside the cluster to manage operator behavior. In hosted control plane clusters, this configuration will live outside of the cluster in the management cluster.

Scenarios

1. Create a cluster by instantiating a new cluster CR that provides enough information to create it.
2. Manage day-2 configuration of the hosted cluster through the cluster CR
3. Destroy a hosted cluster by deleting its corresponding CR

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. What global configuration will be included in the cluster definition?
2. How will machine configuration be represented for a node pool?

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>