Skip to content
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

Better DNS support with vm=none #3304

Closed
bhack opened this issue Nov 6, 2018 · 4 comments
Closed

Better DNS support with vm=none #3304

bhack opened this issue Nov 6, 2018 · 4 comments
Labels
area/dns DNS issues co/none-driver kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@bhack
Copy link

bhack commented Nov 6, 2018

How we could better support coredns name resolving?
For systemd we could use something like:
#2834 (comment)

For docker containers that consume Minikube services we could suggest to to use --dns= option to point to coredns ip.

/cc @balopat

@tstromberg tstromberg added area/dns DNS issues kind/feature Categorizes issue or PR as related to a new feature. co/none-driver os/linux labels Nov 6, 2018
@tstromberg
Copy link
Contributor

I'm still unsure about what this bug is about? What exactly are you asking about? The ability to resolve names from CoreDNS onto the host running minikube?

@tstromberg tstromberg added triage/needs-information Indicates an issue needs more information in order to work on it. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. and removed os/linux labels Jan 23, 2019
@bhack
Copy link
Author

bhack commented Jan 23, 2019

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2019
@tstromberg
Copy link
Contributor

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dns DNS issues co/none-driver kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants