docs: add ADR for autonomous platform clusters#93
Conversation
Signed-off-by: Moritz Marby <moritz.marby@sap.com>
Signed-off-by: Moritz Marby <moritz.marby@sap.com>
Signed-off-by: Moritz Marby <moritz.marby@sap.com>
e541aba to
d6ddebf
Compare
Signed-off-by: Valentin Gerlach <valentin.gerlach@sap.com>
Signed-off-by: Valentin Gerlach <valentin.gerlach@sap.com>
Signed-off-by: Valentin Gerlach <valentin.gerlach@sap.com>
Signed-off-by: Valentin Gerlach <valentin.gerlach@sap.com>
|
That sounds like a big win! Reducing the upfront requirements is an important step. For my understanding, the requirements for an initial Platform cluster are:
Is that correct? |
Update the autonomous clusters ADR to use ocmRepoName instead of ocmComponentName, introduce an explicit OCM Repository resource, and switch component definitions from externalRef to template. Clarify how distributions instantiate per-component RGDs rather than repeating install logic. Also fix typos and normalize dashes. Signed-off-by: Moritz Marby <moritz.marby@sap.com>
Yes, thats exactly how this is intended. cluster-provider is installed through self inflating setup. So just As we need kro + ocm for the self inflating setup, it would be a chicken egg problem. I think the first iteration needs to just have this as a manual installation, but we could iterate on it and improve in future. |
3 participants
What this PR does / why we need it:
Adds an ADR proposing autonomous platform clusters as the target architecture for OpenControlPlane bootstrapping and lifecycle management.
Which issue(s) this PR fixes:
openmcp-project/backlog#555
Release note: