This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge label.

Labelling this PR as size/M

GCE e2e build/test failed for commit 9755054.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

@zmerlynn Can you kindly LGTM this?
The main PR already has the cherrypick-approved label, so I think you should just remove do-not-merge and release-note-label-needed and add lgtm, release-note and maybe ok-to-merge
Thanks

@k8s-bot test this please github issue: #IGNORE

This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge label.

Removing LGTM because the release note process has not been followed.
One of the following labels is required "release-note", "release-note-none", or "release-note-action-required"
Please see: https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/release-notes.md

Ah, the bots don't really like us.
@eparis Should the cherrypick-candidate label be applied on this PR also?

@eparis we need to update the procedure to follow the current cherry pick process. I know this changed right after we 'finalized' it and apologies for that, but if we can change it so that it follows the new procedure of not requiring any accounting on the cherrypick/branch side, that would be good. Also, can you point to [cherry-pick info] - rather than the proposal - in the bot message?

Please add one of release-note|release-note-none. The main PR has the release-note label

This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge label.

Removing LGTM because the release note process has not been followed.
One of the following labels is required "release-note", "release-note-none", or "release-note-action-required"
Please see: https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/release-notes.md

@luxas: I thought you only needed it on the main PR, but the bot gets angry if it's not on both. We need to fix that, there's too many twiddles here.

I also thought it was only required on the master PR, but it doesn't seem so

GCE e2e build/test passed for commit 9755054.

• Build Log
• Test Artifacts
• Internal Jenkins Results

I think the bot will be angry if not the cherrypick-approved label is here also. Not sure if the v1.2 milestone is required.

This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge label.

Yes, this has been a very dynamic process and not all of the changes are in sync as we get things in place. There's a pending PR as well to get all of the docs in sync on this. Comments welcome

The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label?

Had the PR been opened using the scripts it would have automatically gotten the 'cherrypick-approved' label when the 'parent' PR has it.