Skip to content

Commit 3a6fa8f

Browse files
Correcting DNS record for pods exposed by a Service
For pods, DNS record incorrectly specifies deployment name instead of service name. This commit corrects that.
1 parent ec54c70 commit 3a6fa8f

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

content/en/docs/concepts/services-networking/dns-pod-service.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,10 +106,9 @@ and the domain name for your cluster is `cluster.local`, then the Pod has a DNS
106106

107107
`172-17-0-3.default.pod.cluster.local`.
108108

109-
Any pods created by a Deployment or DaemonSet exposed by a Service have the
110-
following DNS resolution available:
109+
Any pods exposed by a Service have the following DNS resolution available:
111110

112-
`pod-ip-address.deployment-name.my-namespace.svc.cluster-domain.example`.
111+
`pod-ip-address.service-name.my-namespace.svc.cluster-domain.example`.
113112

114113
### Pod's hostname and subdomain fields
115114

0 commit comments

Comments
 (0)