This issue serves as an umbrella to track the kubeadm-related PRs we cherrypick into the v1.9 branch.

I've been a cherrypick lead for the kubeadm releases so far, but didn't come up with the idea to track things in a centralized manner like this before ¯_(ツ)_/¯

I propose that @timothysc function as the cherrypick lead on the kubeadm side for v1.9

I've identified a list of PRs to be cherrypicked:

• CoreDNS update to 1.0.1: Update CoreDNS version and Corefile in kubeadm kubernetes#57296
  • @xiangpengzhao please cherrypick this PR to v1.9
• Bump etcd version to 3.1.11: Build etcd image for 3.1.11 version kubernetes#57238
  • Action needed: kubeadm should bump the etcd version used on the v1.9 branch to 3.1.11 at HEAD now and backport to v1.9 ASAP. @xiangpengzhao maybe can help with such a PR
• Only fail preflight checks on known manifests: kubeadm: Only check for well-known files in preflight kubernetes#57287
  • @mattkelly please let us know if you need help with cherrypicking this PR

Individual cherrypick PRs should be created as documented here: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md

TL;DR; download https://github.com/github/hub, make sure git remote -v looks something like this and execute:

$ git remote -v
origin	git@github.com:luxas/kubernetes.git (fetch)
origin	git@github.com:luxas/kubernetes.git (push)
upstream	https://github.com/kubernetes/kubernetes (fetch)
upstream	DISABLE (push)

# Example command
GITHUB_USER=luxas hack/cherry_pick_pull.sh upstream/release-1.9 57296

The script will do everything for you, including creating the PR. You only need to get approval from @timothysc / me as kubeadm approvers and @mbohlool that is the v1.9 patch manager and then the cherrypick can be merged!