-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kube-dns doesn't expose service scoped dns names for pod IPs #633
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
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: