Skip to content
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

Enable creating kubeadm and RKE2 cluster in CAPZ #100

Open
alexander-demicev opened this issue Sep 12, 2024 · 2 comments
Open

Enable creating kubeadm and RKE2 cluster in CAPZ #100

alexander-demicev opened this issue Sep 12, 2024 · 2 comments
Assignees

Comments

@alexander-demicev
Copy link
Member

There is a problem at the moment with CAPZ, it's only able to watch one type of bootstrap config object https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/main.go#L259, this makes it impossible running 2 bootstrap providers at the same time if users are utilizing machine pools.

@furkatgofurov7
Copy link
Contributor

The problem and corresponding flag was introduced to fix rancher/turtles#483 where the controller was exclusively watching Kubeadm resources and not allowing the use of any other bootstrap provider. It is interesting use case though, I am curious if any other infra providers support such a use case and how they handle it.

@kkaempf kkaempf added the kind/enhancement New feature or request label Oct 1, 2024
@anmazzotti anmazzotti self-assigned this Jan 28, 2025
@anmazzotti anmazzotti moved this from Team Backlog to In Progress (8 max) in CAPI / Turtles Jan 28, 2025
@anmazzotti anmazzotti moved this from In Progress (8 max) to PR to be reviewed in CAPI / Turtles Feb 3, 2025
@alexander-demicev alexander-demicev moved this from PR to be reviewed to Blocked in CAPI / Turtles Feb 3, 2025
@kkaempf
Copy link

kkaempf commented Feb 4, 2025

@alexander-demicev what exactly is this waiting on ? (upstream GH issue ?, upstream pr ?, ...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked
Development

Successfully merging a pull request may close this issue.

4 participants