📖 Cluster API Add-on Orchestration proposal

[Jont828]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[elmiko]

this generally makes sense and reads well to me, i just have a question about the API

[g-gaston]

This is great, just a few nit picky suggestions and questions 🙏🏻

[CecileRobertMichon]

+1, it would help to clarify by making a clear separate section for Helm Implementation

[killianmuldoon]

I think this captures the overall problem statement and solution design well- great work!

/lgtm

[sbueringer]

Great work so far. Thx for pushing this forward!

[CecileRobertMichon]

lgtm

[jackfrancis]

(I am biased, but) lgtm

[Jont828]

Squashed and pushed again!

[sbueringer]

Last two from my side:

• 📖 Cluster API Add-on Orchestration proposal #6905 (comment)
• 📖 Cluster API Add-on Orchestration proposal #6905 (comment)

[sbueringer]

Thank you!

/lgtm

[CecileRobertMichon]

/lgtm

[Jont828]

@sbueringer @fabriziopandini @CecileRobertMichon It looks like the discussion is wrapping up. Should we start a lazy consensus timer to get this merged?

[CecileRobertMichon]

+1 on starting lazy consensus

Let's set the lazy consensus for 7 days from now, Wednesday, October 12, 2022?

/approve
/hold

[fabriziopandini]

/lgtm

[Jont828]

Sounds good to me! Thanks to everyone who helped review this doc!

[fabriziopandini]

Lazy consensus expired,
Great work!
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon, fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [CecileRobertMichon,fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/hold cancel
:)

[ossfellow]

While a nice solution, in my opinion this proposal suffers from 2 problems:

1. It doesn’t integrate with the GitOps ecosystem, and in that sense is only useful for bootstrapping a GitOps engine in the newly created cluster.
2. As the reference implementation shows, the concrete implementations either cannot or would require substantial work (including CRD changes) to capture or employ the richness of combining multiple package management tools (e.g. Helm and Kustomize), which the community has spent years to develop.

The Runtime Hooks proposal avoids both issues, allowing the existing user solutions to get triggered as needed (e.g. bootstrap a CNI and a GitOps engine and let it take over), and let the Kubernetes community invest in other work areas, instead of recreating solutions the community has spent years to develop and improve.