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 #31711

Closed
11 tasks
mikedanese opened this issue Aug 30, 2016 · 12 comments
Closed
11 tasks

kubeadm graduation requirements #31711

mikedanese opened this issue Aug 30, 2016 · 12 comments
Labels
area/kubeadm sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects

Comments

@mikedanese
Copy link
Member

mikedanese commented Aug 30, 2016

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

@k8s-github-robot k8s-github-robot added area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. labels Aug 30, 2016
@mikedanese mikedanese added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Aug 30, 2016
@lukemarsden
Copy link
Contributor

lukemarsden commented Aug 30, 2016

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 #30360 (here to save you some clicks)

@philips
Copy link
Contributor

philips commented Sep 9, 2016

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

@pires
Copy link
Contributor

pires commented Oct 5, 2016

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.

@pires
Copy link
Contributor

pires commented Oct 5, 2016

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

@pires
Copy link
Contributor

pires commented Oct 15, 2016

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.

@pires
Copy link
Contributor

pires commented Oct 15, 2016

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

@mikedanese
Copy link
Member Author

Added to the beta graduation requirements,

@mcapuccini
Copy link

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

@luxas
Copy link
Member

luxas commented Nov 20, 2016

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.

@philips
Copy link
Contributor

philips commented Nov 22, 2016

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

@mikedanese
Copy link
Member Author

This issue was moved to kubernetes/kubeadm#63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubeadm sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
No open projects
kubeadm
New features/Design goals
Development

No branches or pull requests

7 participants