You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any Pods exposed by a Service have the following DNS resolution available: pod-ipv4-address.service-name.my-namespace.svc.cluster-domain.example
This is not the case for kube-dns. We're using (generating) those dns names from EndpointSlices for inter cluster communication between services. It does work with coredns.
This is relevant for a number of users since GKE by default uses kube-dns.
Usage of service scoped dns names is preferred because it allows for wildcard certificates like *.service-name.my-namespace.svc.cluster-domain.example to be used.
Proposed solution
Serve service scoped dns names.
The text was updated successfully, but these errors were encountered:
Problem statement
As described in https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records-1:
This is not the case for
kube-dns
. We're using (generating) those dns names fromEndpointSlice
s for inter cluster communication between services. It does work with coredns.This is relevant for a number of users since GKE by default uses kube-dns.
Usage of service scoped dns names is preferred because it allows for wildcard certificates like
*.service-name.my-namespace.svc.cluster-domain.example
to be used.Proposed solution
Serve service scoped dns names.
The text was updated successfully, but these errors were encountered: