kube-dns doesn't expose service scoped dns names for pod IPs

[pmalek]

Problem statement

As described in https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records-1:

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale