whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update statefulset.md

Browse Source
This commit is contained in:
jay vyas
2020-07-09 17:47:08 -04:00
committed by GitHub
parent c63154c176
commit 0f8593d1b7
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/statefulset.md
+6
View File
@@ -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 `$(podname).$(governing service domain)`, where the governing service is defined
by the `serviceName` field on the StatefulSet. 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 As mentioned in the [limitations](#limitations) section, you are responsible for
creating the [Headless Service](/docs/concepts/services-networking/service/#headless-services) creating the [Headless Service](/docs/concepts/services-networking/service/#headless-services)
responsible for the network identity of the pods. responsible for the network identity of the pods.