-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
-
None
Cluster DNS not operating properly. Service names should be accessible by name across namespaces but appear not to be:
To reproduce:
Register a service in kube-system namespace.
Attempt access by-name:
{{root@dr-gfs1:/# curl cluster-registry.kube-system.svc.cluster.local:5000
curl: (6) Could not resolve host: cluster-registry.kube-system.svc.cluster.local
root@dr-gfs1:/# host cluster-registry.kube-system.svc.cluster.local
Host cluster-registry.kube-system.svc.cluster.local not found: 3(NXDOMAIN)
root@dr-gfs1:/# host cluster-registry
Host cluster-registry not found: 3(NXDOMAIN)
}}
DNS in same-namespace is OK:
{{ost cluster-registry.kube-system.svc.cluster.local
cluster-registry.kube-system.svc.cluster.local has address 10.254.109.32
}}
1.3.0 minikube is OK.... not sure if this is our misconfiguration, versioniong, or ??
{{[raila@raila cluster-registry]$ k get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default cf-test2 1/1 Running 0 14m
kube-system cf-test 1/1 Running 2 6h
kube-system cluster-registry-2n1bu 1/1 Running 1 1h
kube-system kube-addon-manager-minikubevm 1/1 Running 3 2d
kube-system kube-registry-proxy-sagyz 1/1 Running 1 5h
kube-system kubernetes-dashboard-kijjg 1/1 Running 3 2d
[raila@raila cluster-registry]$ k exec -it cf-test2 host cluster-registry.kube-system.svc.cluster.local
cluster-registry.kube-system.svc.cluster.local has address 10.0.0.38
}}
- is duplicated by
-
NDS-414 Implement DNS system-names for system services
- Closed