-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: azure support #84
base: master
Are you sure you want to change the base?
Conversation
## Technical considerations | ||
|
||
The Cluster API Azure infrastructure provider supports starting from [v1.13.0](https://github.com/kubernetes-sigs/cluster-api-provider-azure). | ||
The Azure Cluster API operator will create some additional network components for the control plane which are not needed but do not hinder the cluster from working. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is exactly something I was curious about: from my understanding, the CAPZ will create a Load Balancer that would then be used for the AzureCluster Control Plane Endpoint.
That resource would be billed despite not being used, even if you delete it since the CAPZ infrastructure controller will recreate it back, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't try to remove the componenents. I can have a deeper look into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started a PR on the azure operator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lost this message, link to the CAPZ PR: kubernetes-sigs/cluster-api-provider-azure#4611
Co-authored-by: Léonard Suslian <[email protected]>
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. |
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: kubernetes-sigs/cluster-api-provider-azure#4611