parent
d3497844cb
commit
2ebcf10831
|
@ -84,7 +84,7 @@ the hostname of the pod. For example, given a Pod with `hostname` set to
|
|||
The Pod spec also has an optional `subdomain` field which can be used to specify
|
||||
its subdomain. For example, a Pod with `hostname` set to "`foo`", and `subdomain`
|
||||
set to "`bar`", in namespace "`my-namespace`", will have the fully qualified
|
||||
domain name (FQDN) "`foo.bar.my-namespace.svc.cluster.local`".
|
||||
domain name (FQDN) "`foo.bar.my-namespace.pod.cluster.local`".
|
||||
|
||||
Example:
|
||||
|
||||
|
@ -141,7 +141,7 @@ record for the Pod's fully qualified hostname.
|
|||
For example, given a Pod with the hostname set to "`busybox-1`" and the subdomain set to
|
||||
"`default-subdomain`", and a headless Service named "`default-subdomain`" in
|
||||
the same namespace, the pod will see its own FQDN as
|
||||
"`busybox-1.default-subdomain.my-namespace.svc.cluster.local`". DNS serves an
|
||||
"`busybox-1.default-subdomain.my-namespace.pod.cluster.local`". DNS serves an
|
||||
A record at that name, pointing to the Pod's IP. Both pods "`busybox1`" and
|
||||
"`busybox2`" can have their distinct A records.
|
||||
|
||||
|
|
Loading…
Reference in New Issue