Cherrypick tracking issue for v1.11 #958
Labels
area/releasing
kind/tracking-issue
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
This issue serves as an umbrella to track the kubeadm-related PRs we cherrypick into the v1.11 branch.
I propose that @timothysc function as the cherrypick lead on the kubeadm side
I've identified a list of PRs to be cherrypicked:
k8s.gcr.io/pause-amd64:3.1
instead ofk8s.gcr.io/pause:3.1
kubeadm tries to pullk8s.gcr.io/pause-amd64:3.1
instead ofk8s.gcr.io/pause:3.1
#962Individual 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.11 12345
The script will do everything for you, including creating the PR. You only need to get approval from @timothysc / me as kubeadm approvers and @foxish that is the v1.11 patch manager and then the cherrypick can be merged!
The text was updated successfully, but these errors were encountered: