Dramatically Simplify Kubernetes Cluster Creation (kubeadm umbrella issue).

[jbeda]

Description

Creating a new Kubernetes cluster is too hard. We need to simplify the number and types of actions to get a production cluster up and running.

Note that this is different from bringing up a development cluster (single node ala monokube or minikube) or automation around cluster creation (https://github.com/kubernetes/community/wiki/Roadmap:-Cluster-Deployment).

If we do this right, the number of manual steps to get a cluster running should be minimal. This will have the added benefit of making other deployment scenarios (dev cluster, cluster automation) simpler and smaller.

As part of this, we should make simplifying assumptions and have opinionated defaults. An example would be embedding etcd and picking an easy to use network technology. Certificates and trust should be established automatically.

Progress Tracker

• [x] Before Alpha
  • [x] Design Approval
  • [x] Design Proposal. This goes under docs/proposals. Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation. Paste link to merged design proposal here: https://github.com/kubernetes/kubernetes/pull/30360
  • [x] Initial API review (if API). Maybe same PR as design doc. PR-NUMBER
    • Any code that changes an API (/pkg/apis/...)
    • cc @kubernetes/api
  • [x] Write (code + tests + docs) then get them merged. https://github.com/kubernetes/kubernetes/pull/33262
  • [x] Code needs to be disabled by default. Verified by code OWNERS
  • [x] Minimal testing
  • [x] Minimal docs https://github.com/kubernetes/kubernetes.github.io/pull/1265
    • cc @kubernetes/docs on docs PR
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
    • New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io
  • [x] Update release notes
• [x] Before Beta
  • [x] Testing is sufficient for beta
  • [ ] User docs with tutorials
  • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
  • cc @kubernetes/docs on docs PR
  • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • [x] Thorough API review
  • cc @kubernetes/api
• [ ] Before Stable
  • [ ] docs/proposals/foo.md moved to docs/design/foo.md
  • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • [ ] Soak, load testing
  • [ ] detailed user docs and examples
  • cc @kubernetes/docs
  • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

_FEATURESTATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers. FEATURE_STATUS: IN_DEVELOPMENT

More advice:

Design

• Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

• Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
• As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the http://github.com/kubernetes/kubernetes repository, and sometimes http://github.com/kubernetes/contrib, or other repos.
• When you are done with the code, apply the "code-complete" label.
• When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will check that the code matches the proposed feature and design, and that everything is done, and that there is adequate testing. They won't do detailed code review: that already happened when your PRs were reviewed. When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

• [ ] Write user docs and get them merged in.
• User docs go into http://github.com/kubernetes/kubernetes.github.io.
• When the feature has user docs, please add a comment mentioning @kubernetes/docs.
• When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

[luxas]

As discussed in the SIG, no extra docs are needed for this feature. This is an umbrella issue for the general development of kubeadm, and kubeadm is gonna be beta for quite some time yet. These docs have existed since v1.4, and will still be available of course in all future releases.

[zacharysarah]

@luxas Thanks! 🙇

[idvoretskyi]

https://github.com/kubernetes/kubernetes/pull/55901

[justaugustus]

@roberthbailey @luxas @jbeda @mikedanese Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[idvoretskyi]

@roberthbailey @luxas @jbeda @mikedanese @kubernetes/sig-cluster-lifecycle-feature-requests

There've been plans to promote kubeadm to GA in 1.11, the upcoming release. Can you let us know if these plans are still valid?

cc @justaugustus

[luxas]

@idvoretskyi We do not target GA in v1.11. We have executed very well on our path to GA though, eliminating dependencies and roadblocks. Hopefully in v1.12, but you'll never know. We are still blocked on some other parts (like kube-proxy ComponentConfig graduating to beta from sig-network). We're getting really close though :+1:

[luxas]

We're hoping this to go GA in v1.12. Let's track it as that for now and see if we meet the criteria later in this cycle.

[justaugustus]

Tracking as GA for 1.12 /kind feature

[zparnold]

Hey there! @jbeda I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[jimangel]

@roberthbailey @luxas Bump for docs ☝️

/cc @idvoretskyi

[neolit123]

/assign @timothysc

we do have good tutorials on how to setup kubeadm clusters already: https://kubernetes.io/docs/setup/independent/ (under Bootstrapping Clusters with kubeadm)

but i'm missing on historic context for this tracking issue.

[luxas]

I think we're pretty okay docs-wise from earlier releases already, but @timothysc will make the judgement if many new docs are needed or existing docs have to be updated

[zparnold]

Would be nice to have @jrondeau 's input on this as well. She's the amazing lady who does kubeadm!

On Wed, Aug 29, 2018 at 1:31 AM Lucas Käldström notifications@github.com wrote:

I think we're pretty okay docs-wise from earlier releases already, but @timothysc https://github.com/timothysc will make the judgement if many new docs are needed or existing docs have to be updated

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kubernetes/features/issues/11#issuecomment-416870728, or mute the thread https://github.com/notifications/unsubscribe-auth/AE81SLTmpvELHFDgrYyqhZHwLw8HcSotks5uVlFXgaJpZM4I8A4G .

[justaugustus]

@timothysc @luxas @Bradamant3 --

I think we're pretty okay docs-wise from earlier releases already, but @timothysc will make the judgement if many new docs are needed or existing docs have to be updated

Where did we land on this? Are the docs in a good state for 1.12? Are we still planning to land this as GA for 1.12?

cc: @zparnold @jimangel @tfogo

[neolit123]

this gets my :+1: for GA in 1.12, in terms of docs. (we do have to covert some other aspects.)

we have decent documentation in place and we haven't had major, negative feedback on the instructions for cluster creation with kubeadm which were improved a lot in 1.11. in the meantime we continue to improve the docs where possible.

pages to note: https://kubernetes.io/docs/setup/independent/install-kubeadm/ https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ https://kubernetes.io/docs/setup/independent/high-availability/

[kacole2]

Hi. This is currently being tracked for 1.13. I want to see what changes are being made for 1.13 for the feature to be considered GA/Stable.

This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:

• Docs (open placeholder PRs): 11/8
• Code Slush: 11/9
• Code Freeze Begins: 11/15
• Docs Complete and Reviewed: 11/27

Thanks!

[timothysc]

Our objective is to take kubeadm to GA this cycle.

[bogdando]

Reading into https://kubernetes.io/docs/setup/independent/high-availability/ I noticed there is now a neat config file (kubeadm-config.yaml in the guide). But I was not sure what is the status for "features flags" support for that config? Can we have init steps executed selectively yet? Or had it lost from the radar?

[dims]

@bogdando see the "full" example in the doc for featureGates: https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1alpha3/doc.go#L160-L248

[neolit123]

@bogdando

Can we have init steps executed selectively yet? Or had it lost from the radar?

yes, in 1.12 there is kubeadm alpha phase.... which handles init phases. in 1.13 these would be more widely available.

[AishSundar]

@neolit123 @roberthbailey is this still on track for GA in 1.1.3? do we have a link to list of pending PRs or issues for us to track this better?

[neolit123]

@AishSundar

i don't have powers here to update the OP. in terms of docs we are in a good state, test coverage might need some attention as much i understand the goals here.

i'm going to have to defer to @timothysc on this one.

[AishSundar]

@timothysc could you please provide a more latest update on the status of Kubeadm for GA in 1.13. Specifically around

(i) how many and which PRs (code and test) are pending (ii) latest status of docs and links to docs PR (iii) Status of failing kubeadmn tests in master blocking

With code slush nearing us on 11/9, could you provide us with an ETA of when you expect all pending things to land in master? Given we need sometime to stabilize things before Code freeze on 11/16, it might be a good idea to timebox the remaining work and make a Go/No-Go call for GA in 1.13 before Code freeze. Thanks !

@neolit123 @kacole2 @tfogo

[neolit123]

(iii) Status of failing kubeadmn tests in master blocking

this should have green runs today.

[timothysc]

@AishSundar I wish it were that simple. There are a number of PRs in flight and most of the docs will be minor changes. Progress is good, but I probably won't have a good answer for you until ~ next week. Almost all of the work is not "net-new" features but cleanup and bug fixes in shuffling for GA, which will likely span into slush.

[AishSundar]

Ack that @timothysc and thanks for the update and consolidating all the Kubeadm GA work under this issue. We will check back once in slush.

[claurence]

@timothysc Hi I'm an enhancements shadow for 1.13 - checking in on progress for this issue. Code slush is 11/9 and Code freeze is 11/15, is this issue still on track for those milestones? Thanks!

[kacole2]

@timothysc can you drop in a list of PRs we should be tracking for Kubeadm going GA? Thanks!

[neolit123]

the issue is on track, yes.

kubeadm labels are auto-applied to our PRs, too many to log and track on our side: https://github.com/kubernetes/kubernetes/pulls?q=is%3Apr+is%3Aopen+label%3Aarea%2Fkubeadm

as explained in a release team meeting these are our 2 GA items:

the list in here is a critical one: https://github.com/kubernetes/kubeadm/issues/1163

this is for the kubeadm config: https://github.com/kubernetes/kubeadm/issues/911

docs are mostly command reshuffle and are TBD.

[AishSundar]

@timothysc @neolit123 can one of you attend the Release burndown meeting next week (Mon, Wed or Fri) to give the latest update on Kubeadm GA.

[neolit123]

i can try joining today.

update on docs: for GA we only need 2 docs PRs, one already merged and one is a WIP placeholder, TBD before 19th: https://github.com/kubernetes/website/issues/10937#issuecomment-437907394

[neolit123]

update:

all feature PRs were merged. during code freeze we have time to dig for bugs. remaining docs PR is WIP: https://github.com/kubernetes/website/pull/10960

[neolit123]

our docs and all our items for 1.13 are in place. this tracking issue can finally be closed. kubeadm is now GA. :tada:

/close

[k8s-ci-robot]

@neolit123: Closing this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/11#issuecomment-443899822): >our docs and all our items for 1.13 are in place. >this tracking issue can finally be closed. >kubeadm is now GA. :tada: > >/close > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.