Allow ServiceCIDR to be configured via 'service-cluster-ip-range' flag. #3463
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the k8s service CIDR is not configurable and defaults to
10.96.0.0/12
, which makesminikube tunnel
unusable for those of us whose corporate/private networks overlap with that (rather large) IP range.This PR makes ServiceCIDR configurable by adding the
--service-cluster-ip-range
flag tominikube run
(name chosen for consistency with the kube-apiserver flag of the same name).