-
Notifications
You must be signed in to change notification settings - Fork 4.9k
-
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
Resolve domain to ingress #11903
Comments
/kind support |
Which Dunbar driver do you use? Which addons do you enable? What platform? |
I use the docker driver on a debian host |
I have the same problem. Generally I would recommend using the ingress-dns addon so you actually don't need to modify the hostsfile to resolve to ingress dns from the host machine. I use the variant where I told my local dnsmasq to redirect DNS requests for a specific domain, I use "local.k8s", to the minikube dns. That will always returns the minikube ip. So all my local ingresses use the domain "local.k8s". But while this addon supports my host machine to resolve ingress dns correctly, the minikube internal DNS is not able to resolve these internally itself, for example from other pods utilizing the ingresses service. Which is even more strange as, when I understand correctly, minikube on docker driver SHOULD use the DNS from my host machine to resolve DNS requests internally. That again is dnsmasq and should totally be able to resolve to "local.k8s". However this does not work for unknown reasons. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
My pods:
/etc/hosts
:192.168.49.2 example.test
)Now from my machine I can go to http://example.test and it works nice
Problem:
The worker pod cannot resolve
example.test
to the minikube instance.I'd like to configure example.test requests to be directed to the minikube ingress so that they can correctly dispatched to the right pod.
What I tried:
I tried using
minikube --dns-domain example.test
but it is not working.Question:
How can I set my cluster dns so that my pods resolve such domain to the cluster itself?
The text was updated successfully, but these errors were encountered: