-
Notifications
You must be signed in to change notification settings - Fork 708
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
tracking issue for HA to GA #2081
Comments
IMO kubeadm HA
Instead I think that GA criteria should be related to robustness and flexibility. WRT to this on top of my mind the etcd learner feature can be used both for improving robustness and as a sync mechanism for improving reliable parallel joins |
/subscribe 🙃 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
@neolit123 wdyt about graduating this feature? As far as I'm concerned we have two point still on the table
Both of them are nice to have, but at the same time they requires investigation and I don't see use getting on them in the near future. So I'm starting to wonder if we have to go GA with the current implementation, which is now stable since a couple of versions, and reconsider the points above eventually in future |
i guess this is already supported within the limits of our hardcoded timeouts / retries on join.
i see what you mean, but maybe we can ask contributors to investigate learners mode and someone could create a prototype before going GA without it: another item in the OP here is instance specific config: |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/lifecycle frozen |
long term we need to enumerate what tasks remain for HA support to be considered GA by the kubeadm project.
some ideas:
RFE: use learner mode for joining etcd members #1793
Allow usage of KubeletConfiguration next to JoinConfiguration on kubeadm join #1682
tracking issue at k/e:
kubernetes/enhancements#357
tracking issue for HA to Beta:
#1567
Beta KEPS:
https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/0015-kubeadm-join-control-plane.md
https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/20190122-Certificates-copy-for-kubeadm-join--control-plane.md
The text was updated successfully, but these errors were encountered: