From 6b0192ef720141f64bcf08ac712e8f4273fef6ae Mon Sep 17 00:00:00 2001 From: Javier Diaz-Montes Date: Fri, 24 Jul 2020 12:31:38 -0400 Subject: [PATCH] Adding feature status and prerequisite to new feature. --- .../en/docs/concepts/services-networking/dns-pod-service.md | 6 ++++++ 1 file changed, 6 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 9938062af3..a200587570 100644 --- a/content/en/docs/concepts/services-networking/dns-pod-service.md +++ b/content/en/docs/concepts/services-networking/dns-pod-service.md @@ -159,6 +159,12 @@ record unless `publishNotReadyAddresses=True` is set on the Service. ### Pod's setHostnameAsFQDN field {#pod-sethostnameasfqdn-field} +{{< feature-state for_k8s_version="v1.19" state="alpha" >}} + +**Prerequisites**: The `SetHostnameAsFQDN` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) +must be enabled for the +{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}} + When a Pod is configured to have fully qualified domain name (FQDN), its hostname is the short hostname. For example, if you have a Pod with the fully qualified domain name `busybox-1.default-subdomain.my-namespace.svc.cluster-domain.example`, then by default the `hostname` command inside that Pod returns `busybox-1` and the `hostname --fqdn` command returns the FQDN. When you set `setHostnameAsFQDN: true` in the Pod spec, the kubelet writes the Pod's FQDN into the hostname for that Pod's namespace. In this case, both `hostname` and `hostname --fqdn` return the Pod's FQDN.