-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trusty: Handle the new var in kube-proxy manifest #24531
Conversation
GCE e2e build/test passed for commit 7772b7f. |
LGTM |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 7772b7f. |
Automatic merge from submit-queue |
@andyzheng0831: Please prepare a cherrypick PR ASAP and I'll get it merged, thanks! |
Cherry pick PR is made #24531 |
…-#24531-upstream-release-1.2 Automated cherry pick of #24531
Commit found in the "release-1.2" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…ry-pick-of-#24531-upstream-release-1.2 Automated cherry pick of kubernetes#24531
…ry-pick-of-#24531-upstream-release-1.2 Automated cherry pick of kubernetes#24531
This is to capture the kube-proxy manifest change in PR #24429.
@roberthbailey @fabioy @zmerlynn please review this change and mark it as cherry pick candidate. We need to catch up 1.2.3 release.
cc/ @dchen1107 @wonderfly @cjcullen FYI.
I have verified this fix. Without this fix, kube-proxy pod in Trusty nodes cannot be started correctly, i.e., the command line has an unhadled variable. And some other kube-system pods do not work correctly as kube-proxy is not working well. After applying this fix, kube-proxy can be started correctly, and all kube-system pods run successfully.