cluster-api-control-plane-provider-kamaji

cluster-api-control-plane-provider-kamaji copied to clipboard

I tested the controller with azure and it worked out of the box. There are only some additional network components for the control plane which are not needed but also don#t hinder the cluster form working.

azure PR: https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/4611

I'm very keen on getting this supported by Kamaji, I'm just worried about the extra LBs we could get allocated since CAPZ doesn't allow skipping the generation of the Kubernetes API Server endpoint.

@rpahli I'm wondering if you're up to attending a CAPZ office hours meeting, explaining what we're looking to achieve, and finding a consensus in having the chance of disabling the LB reconciliation, at least for the API Server, it would be great.

Of course, I can co-lead the initiative with you, I'm not throwing you 🙃

My PR is currently in draft because the tests are missing. But I already using an operator form this build in our setup to provisions azure clusters with Kamaji.

Do you have some feedback from the CAPZ team regarding this feature?

Yes I think I can attend an office hours meetings and it would be great if you can co lead this event. 🙃

👋🏻 @rpahli I'd like to help you here with this, may I ask you to get in touch? You can find my contacts from LinkedIn, or by extracting the email address I use to sign my commits.

@rpahli sorry, I hadn't the time to give it a try, just wondering if there is some progress on this to get this merged soon, maybe with v0.13.0

We can skip the commit_lint, I'm going to squash the changes in a single commit.

lgtm