From 0f8593d1b72c81286a82386352f17a61e6316acd Mon Sep 17 00:00:00 2001 From: jay vyas Date: Thu, 9 Jul 2020 17:47:08 -0400 Subject: [PATCH] Update statefulset.md --- .../en/docs/concepts/workloads/controllers/statefulset.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md index 4f8429d668..0611f6a9a4 100644 --- a/content/en/docs/concepts/workloads/controllers/statefulset.md +++ b/content/en/docs/concepts/workloads/controllers/statefulset.md @@ -141,6 +141,12 @@ 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. +Note initial availability of stable DNS name's responsiveness: The initial reachability of a Pod via its DNS +depends on the settings of your DNS provider. It may be 30 seconds before the DNS name for your Pod +is reachable from another Pod in your cluster. For StatefulSets which need to come online via a quorum +in a very short (< 30s) time period, consider tuning your DNS settings +or another mechanism (such as querying the Kubernetes endpoints directly for IP addresses). + 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.