False warning for not having minikube ip in NO_PROXY

[pWoLiAn]

What Happened?

I do not have any issues with my minikube setup but just wanted to report this false warning. These are my startup logs:

minikube start --vm-driver=none --kubernetes-version=v1.21.0
😄  minikube v1.34.0 on Ubuntu 20.04
❗  Kubernetes 1.21.0 has a known performance issue on cluster startup. It might take 2 to 3 minutes for a cluster to start.
❗  For more information, see: https://github.com/kubernetes/kubeadm/issues/2395
✨  Using the none driver based on user configuration
👍  Starting "minikube" primary control-plane node in "minikube" cluster
🤹  Running on localhost (CPUs=32, Memory=64278MB, Disk=301803MB) ...
ℹ️  OS release is Ubuntu 20.04.6 LTS
🌐  Found network options:
    ▪ HTTP_PROXY=<proxy>
❗  You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP (10.189.73.30).
📘  Please see https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/ for more details
    ▪ HTTPS_PROXY=<proxy>
    ▪ NO_PROXY=10.189.73.30,localhost,127.0.0.1,<redacted>
🐳  Preparing Kubernetes v1.21.0 on Docker 24.0.7 ...
    ▪ env HTTP_PROXY=<proxy>
    ▪ env HTTPS_PROXY=<proxy>
    ▪ env NO_PROXY=10.189.73.30,localhost,127.0.0.1,<redacted>
    ▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
.
.
.

As you can see, minikube is complaining that I don't have the minikube ip in my NO_PROXY env when its clearly there as it also prints the NO_PROXY env just after the warning.

Attach the log file

log.txt

Operating System

Ubuntu

Driver

None

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale