From 3a6fa8fea2322cf59a562527b091f3d341a90540 Mon Sep 17 00:00:00 2001 From: Yashodhan Mohan Bhatnagar Date: Mon, 17 Jan 2022 01:39:01 +0530 Subject: [PATCH] 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. --- .../en/docs/concepts/services-networking/dns-pod-service.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/services-networking/dns-pod-service.md b/content/en/docs/concepts/services-networking/dns-pod-service.md index aea058c7e1..4e55d8a3f4 100644 --- a/content/en/docs/concepts/services-networking/dns-pod-service.md +++ b/content/en/docs/concepts/services-networking/dns-pod-service.md @@ -106,10 +106,9 @@ and the domain name for your cluster is `cluster.local`, then the Pod has a DNS `172-17-0-3.default.pod.cluster.local`. -Any pods created by a Deployment or DaemonSet exposed by a Service have the -following DNS resolution available: +Any pods exposed by a Service have the following DNS resolution available: -`pod-ip-address.deployment-name.my-namespace.svc.cluster-domain.example`. +`pod-ip-address.service-name.my-namespace.svc.cluster-domain.example`. ### Pod's hostname and subdomain fields