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

add support for adding multiple control plane for multi node #17685

Closed
medyagh opened this issue Nov 29, 2023 · 1 comment · Fixed by #17909
Closed

add support for adding multiple control plane for multi node #17685

medyagh opened this issue Nov 29, 2023 · 1 comment · Fixed by #17909
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@medyagh
Copy link
Member

medyagh commented Nov 29, 2023

What Happened?

#17681 (review)

Attach the log file

n/a

Operating System

None

Driver

None

@medyagh medyagh added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 29, 2023
@prezha prezha self-assigned this Nov 29, 2023
@prezha
Copy link
Contributor

prezha commented Jan 8, 2024

turns out that it'd be easy to "just add" yet another control-plane node to an existing cluster, whereas it's a bit trickier to fully utilise a multi-control-plane (ie, ha) cluster, requiring, amongst other things, a load-balancer for multiple apiservers and quorum for multiple etcd nodes, etc.

also, "upgrading" a non-ha cluster to one that'd become a ha cluster would currently require resetting the cluster, as the kubeadm config would have to change as well, therefore i've created a more general issue #17908 & pr #17909 (containing more details) to address adding native support for creating and managing ha clusters in minikube

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants