-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
local-up-cluster.sh: add SERVICE_CLUSTER_IP_RANGE as option #32921
local-up-cluster.sh: add SERVICE_CLUSTER_IP_RANGE as option #32921
Conversation
Signed-off-by: André Martins <[email protected]>
Can a kubernetes member verify that this patch is reasonable to test? If so, please reply with "@k8s-bot ok to test" on its own line. Regular contributors should join the org to skip this step. While we transition away from the Jenkins GitHub PR Builder plugin, "ok to test" commenters will need to be on the admin list defined in this file. |
Is it too late to merge this into |
@zmerlynn I think you have to change the labels in order for the @googlebot to catch it up |
@aanm: Fixed, sorry, I thought the munger caught approval -> auto-LGTM by now. |
Jenkins GCI Kubemark GCE e2e failed for commit f225d4a. Full PR test history. The magic incantation to run this job again is |
Automatic merge from submit-queue |
Allows the user the use an environment variable to specify the SERVICE_CLUSTER_IP_RANGE without modifying the
hack/local-up-cluster.sh
script.Signed-off-by: André Martins [email protected]
This change is