@luxas thank you very much for helping improve coordination with kubeadm!

@luxas we have a kubeadm-related feature tracking issue at the features repo - kubernetes/enhancements#11.

Any updates planned for 1.8 to be reflected at the features repo?

[MILESTONENOTIFIER] Milestone Labels Complete

@luxas @roberthbailey @timothysc

Issue label settings:

• sig/cluster-lifecycle: Issue will be escalated to these SIGs if needed.
• priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels.
• kind/feature: New functionality.

@idvoretskyi I've done the required modifications to the release notes and splitted the "kubeadm upgrades with selfhosting" feature to one for upgrading and one for self-hosting as they mature separately

Update, https://github.com/kubernetes/kubeadm/milestone/3 contains four items:

• Enabling upgrade e2e tests (assignees: @jessicaochen @jamiehannaford @luxas)
• Making sure the kubelet doesn't panic (potential release-blocker): kubelet built from master panics: "invalid memory address or nil pointer dereference" #52242 (assignee: @dixudx @luxas to verify)
• Merging kubeadm: Use the release-1.8 branch by default #52085 (assignee: @abgworrall )
• Writing various docs, non-blocking for your tracking, but anyway, in the works.

@jdumars ACK? The most important one is 2), not sure what to do there in the meantime.

ack - I'll keep an eye on this as best I can. Please let me know directly if things change for better or worse. I have a lot of irons in the fire at the moment. :)

@luxas looks like there are 5 items now :)

@luxas - we need to determine (today if possible) if any of the kubeadm work is truly release blocking. If so, please add the release-blocker label and update this issue with relevant issues/PRs. Thanks!

Nope, the things that were outstanding were fixed in the go. I manually tested kubeadm v1.8.0-rc.1 packages on all possible and impossible OSes and configurations as well successfully (well, I had to tweak the docs a bit, but anyway 😄)

We're gonna have some nonblocking cherrypicks to v1.8 (for instance we found that the kubelet asks for a cert although it has one already when cert rotation is enabled, etc), and small UX improvements, but we had nothing that truly blocked the release in the end, which is awesome!

I think this can now be closed 🎉 🌯