From 18cca972a603ee8b0a637aeb0c03463f818f4617 Mon Sep 17 00:00:00 2001 From: Yury Tsarev Date: Mon, 13 Apr 2020 14:53:40 +0200 Subject: [PATCH] Document pod DNS resolution schema * 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 --- .../docs/concepts/services-networking/dns-pod-service.md | 7 +++++++ 1 file changed, 7 insertions(+) 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 8e790151f2..488208d8bb 100644 --- a/content/en/docs/concepts/services-networking/dns-pod-service.md +++ b/content/en/docs/concepts/services-networking/dns-pod-service.md @@ -66,6 +66,13 @@ of the form `auto-generated-name.my-svc.my-namespace.svc.cluster-domain.example` ## 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 Currently when a pod is created, its hostname is the Pod's `metadata.name` value.