Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

I guess this commit will fix the error occuring with "kube-push" if the bearer token is already present, but it will not fix it the token was not present (if the cluster was created before e2c79ea was merged)

Labelling this PR as size/XS

Taking this PR review since its vagrant...

Thanks for the PR. I verified this fixed kube-push.

@k8s-bot ok to test
@k8s-bot test this

pr builder appears to be missing, activating due to 'lgtm' label.

GCE e2e build/test failed for commit 08541dc.

• 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.

@k8s-bot test this issue: #21487

@derekwaynecarr Could you please re-test this pull request?

@k8s-bot test this please github issue: #IGNORE (jenkins issues)

GCE e2e build/test failed for commit 08541dc.

• 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.

I can confirm this fixes kube-push.sh. Thanks.

@k8s-bot test this please github issue: #IGNORE (jenkins issues)

GCE e2e build/test passed for commit 08541dc.

• Build Log
• Test Artifacts
• Internal Jenkins Results

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

Automatic merge from submit-queue