Expose ingress hosts with mDNS

[calind]

This is a feature request for exposing ingresses when using minikube tunnel.

The hosts can be exposed by having minikube answer for mDNS requests for domains ending in .local with the IPs set in the ingress status.

[calind]

This can be implemented as a stand-alone controller running with host netowrk. Do you think that this can make it to the addons?

[tstromberg]

I think so. I'd be happy to review any PR's which make this happen.

[fejta-bot]

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[woodcockjosh]

I would rather not have to run minikube tunnel to access a host $(minikube ip) which is already available. What if I have several minikube instances? I have to run minikube tunnel for every host? Instead I would propose that the ingress resources be made available on the host os and mapped to the appropriate minikube ip.

@calind here is a controller ready to become a plugin which resolves the ingress hosts to the minikube ip. https://gitlab.com/cryptexlabs/public/development/minikube-ingress-dns

You still have to add manually the file
/etc/resolvers/minikube-minikube-test
with the contents

domain test
nameserver 192.168.99.169
search_order 1
timeout 5

where192.168.99.169 is your minikube ip

If either one or both of these proposals are accepted we can eliminate manually adding this file to /etc/resolvers/:
#5494
#5498

[woodcockjosh]

Ingress DNS addon provides a DNS server for ingress resources on the host OS: #5507

[priyawadhwa]

@woodcockjosh has this issue been resolved by #5507?

[fejta-bot]

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.