Epic Goal

1. The next-gen control plane can be smaller enough to provide the registration and placement capability by default. others can be configurable, including managedclusterinfo, managedserviceaccount and configuration policy.
2. The next-gen control plane can be run in different namespaces.

Why is this important?

The next-gen controlplane deploys an independent Kubernetes API server. So it can be deployed in a single cluster with multiple instances. It can address some customers' use case that have a powerful machine to deploy multiple ACM instances to manage the clusters.

Scenarios

...

Acceptance Criteria

...

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>