minikube: kubelet resolv-conf is not overriding

Current status: OS: Ubuntu 18.0.4 Minikube version: 1.10.x Driver: none On former versions, the minikube is auto setting extra-config to “kubelet.resolv-conf=/run/systemd/resolve/resolv.conf” only when kubelet.resolv.conf is not set. But once it is set, then auto setting is ignored, and the specified conf was overriding.

On version 1.10.x, the minikube is auto setting extra-config to “kubelet.resolv-conf=/run/systemd/resolve/resolv.conf” always. i.e. the specified resolv conf is appending to the systemd resolv conf.

v1.9.0 $minikube start

...
Preparing Kubernetes v1.18.0 on Docker 19.03.8 ...
 - kubelet.resolv-conf= /run/systemd/resolve/resolv.conf 
...

$minikube start --extra-config=kubelet.resolv-conf=/home/zuul/.minikube/k8s_resolv.conf

...
Preparing Kubernetes v1.18.0 on Docker 19.03.8 ...
 - kubelet.resolv-conf=/home/zuul/.minikube/k8s_resolv.conf
...

v1.10.x $minikube start

...
Preparing Kubernetes v1.18.0 on Docker 19.03.8 ...
 - kubelet.resolv-conf= /run/systemd/resolve/resolv.conf 
...

$minikube start --extra-config=kubelet.resolv-conf=/home/zuul/.minikube/k8s_resolv.conf

...
Preparing Kubernetes v1.18.0 on Docker 19.03.8 ...
 - kubelet.resolv-conf=/home/zuul/.minikube/k8s_resolv.conf
 - kubelet.resolv-conf= /run/systemd/resolve/resolv.conf 
...

Expectation kubelet.resolv-conf would be overriding. So once that is specified, then the auto setting would be ignored.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (5 by maintainers)

Most upvoted comments

Cool, then I’ll try to make a PR for this.