-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Full support for custom service cluster ip range #2264
Conversation
Can one of the admins verify this patch? |
@minikube-bot ok to test |
@@ -173,7 +172,7 @@ func GetHostDriverIP(api libmachine.API) (net.IP, error) { | |||
func engineOptions(config MachineConfig) *engine.Options { | |||
o := engine.Options{ | |||
Env: config.DockerEnv, | |||
InsecureRegistry: append([]string{pkgutil.DefaultServiceCIDR}, config.InsecureRegistry...), | |||
InsecureRegistry: append([]string{config.ServiceCIDR}, config.InsecureRegistry...), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 glad this was picked up in the PR :)
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale I don't believe that this PR should close due to inactivity when it offers a point of configurability that would - at least to me - be useful. My use case is this: https://stevesloka.com/2017/05/19/access-minikube-services-from-host/ |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
this one even includes a patch! it ain't rotten. |
@rodcloutier I wonder if it would be possible for you to freshen this up to make it super-simple for admins to approve? |
I just built the minikube.iso image from this branch hoping it could fix my issues with colliding network ranges (company networks spanning 172.16/12 and 10.0/8) but sadly it didn't. The issue was with routing service IPs (10.96/12) within the cluster, which always went through my host and was terminated by our company firewall instead of going to the services I actually wanted. I tried starting minikube with the following settings but it just stalls and aborts after 10 minutes or so:
I also tried removing single CIDR parameters but the result didn't change. In summary: not sure whether this PR actually fixes the issue but it would be really great if it did 😃 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Do you mind addressing the merge conflicts? I'd like to see about merging this if it's still viable. My apologies for the unnecessarily long delay in reviewing this PR. |
Any hope for resurrecting this PR from the merge conflicts? I feel like it's doing the right thing and would love to see it in minikube. Thanks for all the hard work you've put into it so far. |
I will see what I can do.
… On Feb 8, 2019, at 18:39, Thomas Strömberg ***@***.***> wrote:
Any hope for resurrecting this PR from the merge conflicts? I feel like it's doing the right thing and would love to see it in minikube. Thanks for all the hard work you've put into it so far.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
a2d844a
to
80b67ac
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rodcloutier If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
80b67ac
to
27b9943
Compare
@@ -294,15 +294,22 @@ func NewKubeletConfig(k8s config.KubernetesConfig, r cruntime.Manager) (string, | |||
return "", errors.Wrap(err, "parses feature gate config for kubelet") | |||
} | |||
|
|||
clusterDNS, err := util.GetDNSIP(k8s.ServiceCIDR) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you mention why the DNS changes are necessary in the PR comment?
@@ -43,6 +43,7 @@ type MachineConfig struct { | |||
InsecureRegistry []string | |||
RegistryMirror []string | |||
HostOnlyCIDR string // Only used by the virtualbox driver | |||
ServiceCIDR string // Use for insecure registry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why the ServiceCIDR is only to be used with the insecure registry. Can you clarify this comment?
Thank you for the contribution. Due to recent inactivity and failing tests, I am marking this PR as closed until the issues can be resolved. I really would like to see this PR come into being, so please re-open once it seems to be working. Before doing so, please run the integration tests locally: https://github.com/kubernetes/minikube/blob/master/docs/contributors/build_guide.md#integration-tests Thank you again! |
This PR intends to add full support for custom service cluster ip range.
Fixes #1536
Fixes #1747
Feel free to add some more requirements for testing.