Cluster API Operator Quickstart

[dtzar]

What would you like to be added (User Story)?

As an operator, I would like to have quickstart instructions install cluster API and all dependencies utilizing the Cluster API Operator so that I can have a more scalable, GitOps-friendly, and better overall lifecycle for my CAPI management cluster(s).

Detailed Description

Would like to have an alternate path to the current quickstart guidance which only utilizes the operator (not clusterctl). This is important to have in the cluster API project book for visibility.

Anything else you would like to add?

Rough proposal would be to have a separate quickstart flow/path/page linked to at the top of the existing clusterctl quickstart page. Open for discussion on this thread.

Label(s) to be applied

/kind feature
/kind documentation
/area documentation

[killianmuldoon]

/triage accepted

Sounds like a good idea. Do we know if the current CAPI operator Getting Started is up to date? If we could separate out a doc like that in the operator repo we would be able to embed it in the CAPI book. This is similar to what we're doing for the autoscaler today.

[dtzar]

I like the embed idea! The getting started is up to date, but not streamlined for being embeded as a CAPI book quickstart. I'd be happy to help with this.
Step 1 - refactor getting started in operator repo
Step 2 - PR to CAPI to add a new quickstart which has that article embeded.

[alexander-demicev]

I would like to work on that. Yes, we try to keep the operator's docs up to date.
/assign