Choose Minikube's Internal NO_PROXY Ranges for Its Active Driver
Use the profile's actual network and service range; a historical subnet from another driver is not a universal bypass list.
When Minikube needs a proxy for Internet downloads, keep the cluster's own destinations direct. Choose bypasses from the active profile and driver, rather than copying one subnet from another machine.
Minikube documents these defaults:
| Use | Default range |
|---|---|
| Some VM drivers | 192.168.59.0/24 |
| kvm2 | 192.168.39.0/24 |
| Docker driver's first cluster | 192.168.49.0/24 |
| Service cluster IPs | 10.96.0.0/12 |
Add the applicable ranges and local destinations to NO_PROXY, adjusting them for custom networks. A broad 192.168.0.0/16 does not necessarily describe the profile's required routes.
For a running profile, minikube ip gives its address. List that address explicitly when the participating browser or other client's bypass parser lacks CIDR support.
Keep this internal-route choice separate from the download phase. Host-side downloads and the node runtime's image pulls can use different environments. A binary download succeeding on the host does not establish that the runtime received its proxy configuration.