From fe0ea239bc99434219c505f283fd2d8174d98cc9 Mon Sep 17 00:00:00 2001 From: Matt McNaughton Date: Wed, 13 Feb 2019 05:00:51 -0500 Subject: [PATCH] Improve stateful set dns docs (#12564) Address the issue raised in https://github.com/kubernetes/kubernetes/issues/73808, where it became clear it would be helpful for there to be a reminder for the user that they are responsible for managing the StatefulSet which provides DNS names for the pods in a StatefulSet. --- content/en/docs/concepts/workloads/controllers/statefulset.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md index 0e3a4e85698e9..e83a4f3c8bea6 100644 --- a/content/en/docs/concepts/workloads/controllers/statefulset.md +++ b/content/en/docs/concepts/workloads/controllers/statefulset.md @@ -134,6 +134,10 @@ As each Pod is created, it gets a matching DNS subdomain, taking the form: `$(podname).$(governing service domain)`, where the governing service is defined by the `serviceName` field on the StatefulSet. +As mentioned in the [limitations](#limitations) section, you are responsible for +creating the [Headless Service](/docs/concepts/services-networking/service/#headless-services) +responsible for the network identity of the pods. + Here are some examples of choices for Cluster Domain, Service name, StatefulSet name, and how that affects the DNS names for the StatefulSet's Pods.