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
kubeadm graduation requirements #31711
Comments
@mikedanese Sorry to be annoying, but could we use a feature for this? https://github.com/kubernetes/features |
Was this even looked at during yesterday's meeting? |
@pires I think we should discuss what beta means in more depth next meeting. |
@mikedanese agreed. Added item on meeting's agenda. |
We have agreed to have several |
@mikedanese we should add testing (#34136) as a hard requirement for GA. |
Added to the beta graduation requirements, |
Hello! Is the HA support for kubeadm under development? Will it be in K8s 1.5? |
HA for everyone is an extremely complicated task given Kubernetes' current architecture without having a cloud provider, central loadbalancer or something like that you can rely on, but eventually we'd like to have HA support for kubeadm, yes. See the v1.6 objectives which includes steps to get closer to bare-metal HA: https://docs.google.com/document/d/1v4k7eN-eetHbbpTAG7WuioRAMsK_FVGi1yC3VIn4Inw/edit#heading=h.8dh1uxinqwag |
@luxas I think HA can be made easier if we fix the API server to advertise DNS instead of just an IP and fix the default "race" where two API servers just flip-flop forever. |
This issue was moved to kubernetes/kubeadm#63 |
We need to decide on a scope for kubeadm that we feel comfortable strapping a
beta
label onto.Beta requirements:
Beta or GA?
GA requirements:
Wishlist:
@kubernetes/sig-cluster-lifecycle
The text was updated successfully, but these errors were encountered: