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

Document pod DNS resolution schema

Browse Source 
* Currently documentation mentions resolvable FQDNs for services only
* Documentation for pods is confusing in regards of local pod `hostname`
  wich actually does not match in-cluster DNS resolution
* This PR clarifies FQDN schema that is used for pod DNS resolution
This commit is contained in:
Yury Tsarev
2020-04-13 14:53:40 +02:00
parent 9c7a63c1ac
commit 18cca972a6
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/dns-pod-service.md
+7
View File
@@ -66,6 +66,13 @@ of the form `auto-generated-name.my-svc.my-namespace.svc.cluster-domain.example`
## Pods ## Pods
### A/AAAA records
Any pods created by a Deployment or DaemonSet have the following
DNS resolution available:
`pod-ip-address.deployment-name.my-namespace.svc.cluster-domain.example.`
### Pod's hostname and subdomain fields ### Pod's hostname and subdomain fields
Currently when a pod is created, its hostname is the Pod's `metadata.name` value. Currently when a pod is created, its hostname is the Pod's `metadata.name` value.