Closed vhosakot closed 6 years ago
build PR
Green gate with no dangling kube-dns
!
Having dangling, pod-less resources is just bad design lol. The k8s dev confirmed this.
The dangling kube-dns
service's port 53 conflicts with the NodePort 53 in the host network. Meenakshi saw this issue too:
[vagrant@k8master ~]$ kubectl describe service kube-dns -n=kube-system | grep 'IP:\|Target'
IP: 10.96.0.10
TargetPort: 53/UDP
TargetPort: 53/TCP
[vagrant@k8master ~]$ kubectl run -i --tty busybox --image=busybox
/ # cat /etc/resolv.conf | grep nameserver
nameserver 10.96.0.10
/ # nslookup localhost
Server: 10.96.0.10
Address 1: 10.96.0.10
Name: localhost
Address 1: ::1 localhost
Address 2: 127.0.0.1 localhost
README.md already updated in this PR too at https://github.com/contiv/netplugin/blob/master/install/k8s/README.md#using-contiv.
kube-dns
is pod-less, endpoint-less, backend-less, useless and dangling incontiv/netplugin
's vagrant dev setup. This is a bit confusing and makes the user think that contiv useskube-dns
when it does not.Contiv uses its own custom DNS in k8s:
https://github.com/contiv/netplugin/blob/master/docs/dns.md
The k8s dev confirmed that if we're using external/custom DNS in k8s and deleting the
kube-dns
deployment, we need to delete all the remaining dangling, pod-lesskube-dns
k8s resources (service, serviceaccount, clusterrolebinding
andendpoint
) too, so that they do not conflict with the contiv's external/custom DNS in any way.Signed-off-by: Vikram Hosakote vhosakot@cisco.com