Merge pull request #48271 from shyamjvs/cluster-ip-e2e-flag
Automatic merge from submit-queue
Make cluster IP range an argument to ginkgo to fix firewall test
This should fix the failing "Firewall rule should have correct firewall rules for e2e cluster" test when using a non-default cluster IP range.
(Ref: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-enormous-cluster/13#k8sio-firewall-rule-should-have-correct-firewall-rules-for-e2e-cluster)
/cc @kubernetes/sig-network-pr-reviews @gmarek
Showing
Please
register
or
sign in
to comment