-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Add user-specified kubectl arguments to addons start script #30372
Add user-specified kubectl arguments to addons start script #30372
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
4 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
LGTM, @bbreslauer please sign CLA or use your @google.com email address as the author of the commit. |
@k8s-bot ok to test |
3037748
to
e82c3fb
Compare
CLAs look good, thanks! |
@k8s-bot ok to test, issue: #IGNORE |
GCE e2e build/test passed for commit e82c3fb. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
@k8s-bot ok to smoke e2e test, issue: #IGNORE |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit e82c3fb. |
Automatic merge from submit-queue |
This broke addon manager when Repro as below:
And because the following PS: Seems like it would be |
Automatic merge from submit-queue Revert #28823 and #30372 in release-1.4 branch **What this PR does / why we need it**: these two PRs were added after the kube-addon-manager was bumped to v5.1, but v5.1 is what the Kubernetes 1.4 release uses. We should match the code and functionality so we can easily rebuild the image as needed. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #43587 **Special notes for your reviewer**: I have not yet pushed a new v5.1.1 image. **Release note**: ```release-note NONE ``` (No release note, since this intentionally reverts functionality which doesn't exist in 1.4.) cc @timstclair @douglas-gibbons @bbreslauer
This is a simple way, using the same environment variable paradigm used throughout these scripts, to let a user specify kubectl arguments to the addons script.
fixes #30371
This change is