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

kubeadm graduation requirements #63

Closed
3 of 11 tasks
mikedanese opened this issue Nov 22, 2016 · 12 comments
Closed
3 of 11 tasks

kubeadm graduation requirements #63

mikedanese opened this issue Nov 22, 2016 · 12 comments
Labels
kind/tracking-issue priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@mikedanese
Copy link
Member

mikedanese commented Nov 22, 2016

From @mikedanese on August 30, 2016 16:33

We need to decide on a scope for kubeadm that we feel comfortable strapping a beta label onto.

Beta requirements:

Beta or GA?

  • CA certificate rotation
  • join secret rotation

GA requirements:

  • TLS bootstrap GA
  • Discovery API GA

Wishlist:

  • Better support for self hosting
    • Kubelet checkpointing
  • High availability
  • Kubeconfig v2

@kubernetes/sig-cluster-lifecycle

Copied from original issue: kubernetes/kubernetes#31711

@mikedanese
Copy link
Member Author

From @lukemarsden on August 30, 2016 17:7

Thanks for this!

I think it might make sense to distinguish between items such as "phase I => beta" or "phase II => alpha", according to the phase I/II breakdown in kubernetes/kubernetes#30360 (here to save you some clicks)

@mikedanese
Copy link
Member Author

From @philips on September 9, 2016 16:22

@mikedanese Sorry to be annoying, but could we use a feature for this? https://github.com/kubernetes/features

@mikedanese
Copy link
Member Author

From @pires on October 5, 2016 9:59

Was this even looked at during yesterday's meeting?

@mikedanese
Copy link
Member Author

@pires I think we should discuss what beta means in more depth next meeting.

@mikedanese
Copy link
Member Author

From @pires on October 5, 2016 22:9

@mikedanese agreed. Added item on meeting's agenda.

@mikedanese
Copy link
Member Author

From @pires on October 15, 2016 12:37

We have agreed to have several kubeadm components with each having its own graduation requirements, right? E.g., kubeadm could be GA while kubeadm HA is alpha.

@mikedanese
Copy link
Member Author

From @pires on October 15, 2016 13:47

@mikedanese we should add testing (#34136) as a hard requirement for GA.

@mikedanese
Copy link
Member Author

Added to the beta graduation requirements,

@mikedanese
Copy link
Member Author

From @mcapuccini on November 20, 2016 15:44

Hello! Is the HA support for kubeadm under development? Will it be in K8s 1.5?

@mikedanese
Copy link
Member Author

From @luxas on November 20, 2016 18:42

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
We will probably not have full-blown HA support for v1.6.

@mikedanese
Copy link
Member Author

From @philips on November 22, 2016 19:34

@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.

@luxas luxas added kind/tracking-issue priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 25, 2016
@pipejakob pipejakob mentioned this issue Mar 2, 2017
13 tasks
@luxas
Copy link
Member

luxas commented Jun 29, 2017

I think we cover this in the features issues we've spawned, so this doesn't make as much sense anymore as it did early on. Closing...

@luxas luxas closed this as completed Jun 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/tracking-issue priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

2 participants