无需配置/etc/hosts或minikube tunnel，如何发现minikube Ingress资源？

Great question—dealing with manual DNS entries or hanging onto a terminal running minikube tunnel is definitely a hassle, especially since your VM is local and you know the Ingress works once the hosts are set. Here are two reliable, low-fuss solutions:

1. Use Minikube's Official ingress-dns Addon #

This is the most straightforward, official way to automate DNS resolution for your Ingress resources. The addon sets up a DNS server inside your minikube cluster that responds to your Ingress hostnames, and you just need to point your local machine to use this DNS for those domains.

Steps: #

• First, enable the addon:

  minikube addons enable ingress-dns
  

• Linux (systemd-resolved):
  Create a config file to tell your system resolver to use minikube's DNS for your Ingress domains:

  sudo tee /etc/systemd/resolved.conf.d/minikube-ingress.conf <<EOF
  [Resolve]
  DNS=$(minikube ip)
  Domains=~example.com  # Replace with your Ingress domain suffix
  EOF
  

  Restart the resolver to apply changes:

  sudo systemctl restart systemd-resolved
  

• macOS:
  Use macOS's network settings to add minikube's IP as a DNS server for your domain. Alternatively, use dnsmasq (covered below) for easier management.
• Windows:
  Open your network adapter settings, add minikube's IP as a DNS server, and specify your Ingress domain as a "search domain".

The best part? If minikube restarts and changes its IP, you can just re-run the command to update the DNS entry (or set up a simple script to do it automatically).

2. Set Up a Local DNS Server (dnsmasq) #

If you want more flexibility (like handling multiple domain suffixes), a local DNS server like dnsmasq is perfect. It'll automatically map all your Ingress hostnames to minikube's IP without touching /etc/hosts.

Steps: #

• Install dnsmasq:
  • Debian/Ubuntu: sudo apt install dnsmasq
  • macOS: brew install dnsmasq
• Create a config file for minikube Ingress:

  sudo tee /etc/dnsmasq.d/minikube-ingress.conf <<EOF
  # Map all subdomains of example.com to minikube's IP
  address=/example.com/$(minikube ip)
  EOF
  

• Restart dnsmasq:
  • Linux: sudo systemctl restart dnsmasq
  • macOS: brew services restart dnsmasq
• Point your local machine to use 127.0.0.1 as the primary DNS server (this tells your system to use dnsmasq for all queries, which will forward non-Ingress requests to your default DNS).

Bonus: Auto-Update Minikube IP #

If minikube's IP changes on restart, you can create a simple script to refresh the dnsmasq config:

#!/bin/bash
sudo sed -i "s/address=\/example.com\/.*/address=\/example.com\/$(minikube ip)/" /etc/dnsmasq.d/minikube-ingress.conf
sudo systemctl restart dnsmasq  # or brew services restart dnsmasq on macOS

Save this as update-minikube-dns.sh, make it executable, and run it whenever minikube restarts.

Why This Works #

Your Ingress controller is already listening on minikube's VM IP (either via NodePort or the default Ingress port). By automating DNS resolution to map your Ingress hostnames to that IP, you skip the manual /etc/hosts edits. And since Ingress doesn't require a LoadBalancer service (which is what minikube tunnel is for), you don't need to keep that process running at all.

内容的提问来源于stack exchange，提问作者Josh Woodcock