whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correcting DNS record for pods exposed by a Service

Browse Source 
For pods, DNS record incorrectly specifies deployment name
instead of service name. This commit corrects that.
This commit is contained in:
Yashodhan Mohan Bhatnagar
2022-01-17 01:39:01 +05:30
parent ec54c706de
commit 3a6fa8fea2
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/dns-pod-service.md
+2 -3
View File
@@ -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