Minikube: `Property name kube-dns not found`

[kamilgregorczyk]

Whenever I try to enable kube-dns with minikune addons enable kube-dns I get Property name kube-dns not found eventhough this addon is listed:

➜  ~ minikube addons list
- addon-manager: enabled
- dashboard: enabled
- default-storageclass: enabled
- efk: disabled
- freshpod: disabled
- gvisor: disabled
- heapster: enabled
- ingress: disabled
- kube-dns: disabled
- metrics-server: disabled
- nvidia-driver-installer: disabled
- nvidia-gpu-device-plugin: disabled
- registry: disabled
- registry-creds: disabled
- storage-provisioner: enabled
- storage-provisioner-gluster: disabled

Environment:

Minikube version (use minikube version): v0.33.1

• OS MacOS 14.4.3
• VM Driver: virtualbox
• ISO version: ` "Boot2DockerURL": "file:///Users/kamilgregorczyk/.minikube/cache/iso/minikube-v0.33.1.iso",

[husamuddin]

I'm having the same issue

Environment:

• OS Archlinux
• Minikube: v0.33.1
• VM Driver: virtualbox

[tstromberg]

I suspect this is fallout from kube-dns being deprecated in favor of CoreDNS in Kubernetes. We'll have to take a closer look, but I suspect this addon is no longer meaningful.

[hpandeycodeit]

@tstromberg I can work on this one.
Are we looking to remove the kube-dns addon completely?

[tstromberg]

@hpandeycodeit - Yes, I don't think it makes sense to exist any longer, to be honest.

Thank you for offering!

[hkroger]

Is there a workaround to get kubernetes DNS working somehow? I am facing this issue and I also think that because of this might be that the pods cannot access any DNS either. I see that a service cannot start because it cannot resolve some non-kubernetes hostname. Can it be because of this?

[kamilgregorczyk]

I don't think so, coredns that automatically boots with minikube works
flawlessly for me. I just wanted to try out kube DNS

śr., 13 lut 2019, 11:49: Hannu Kröger [e-mail] napisał(a):

Is there a workaround to get kubernetes DNS working somehow? I am facing
this issue and I also think that because of this might be that the pods
cannot access any DNS either. I see that a service cannot start because it
cannot resolve some non-kubernetes hostname. Can it be because of this?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/3642#issuecomment-463152161,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI1koGiTndF5HZ63U3t4JV9qhlRzfY8Aks5vM-2ngaJpZM4awrY5
.

[hkroger]

Actually my problem is that coredns does not start because it gets into resolving loop because systemd-resolved has 127.0.0.53 in resolv.conf. Should I create a ticket about this?

[hpandeycodeit]

@tstromberg After I build the minikube from the source, I don't see any kube-dns addon in the list:

`
out/minikube addons list

• addon-manager: enabled
• dashboard: disabled
• default-storageclass: enabled
• efk: disabled
• freshpod: disabled
• gvisor: disabled
• heapster: disabled
• ingress: disabled
• logviewer: disabled
• metrics-server: disabled
• nvidia-driver-installer: disabled
• nvidia-gpu-device-plugin: disabled
• registry: enabled
• registry-creds: disabled
• storage-provisioner: enabled
• storage-provisioner-gluster: disabled
  `
  Looks like the code is already merged but not yet released?

[tioxy]

The version v0.33.1 had kube-dns as an addon.

As @hpandeycodeit pointed, it's already merged #3556

Updating your minikube version to >= 0.34.0 should fix it.

[tstromberg]

Marking as obsolete, as the kube-dns addon was removed in a previous release. Please re-open if you run into this again.