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

Update content/en/docs/concepts/workloads/controllers/statefulset.md

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
jay vyas
2020-07-12 08:20:25 -04:00
committed by GitHub
parent 0f8593d1b7
commit 167746be6f
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/statefulset.md
+10 -6
View File
@@ -141,11 +141,16 @@ 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 {{< note >}}
depends on the settings of your DNS provider. It may be 30 seconds before the DNS name for your Pod Depending on how DNS is configured in your cluster, you may not be able to look up the DNS
is reachable from another Pod in your cluster. For StatefulSets which need to come online via a quorum name for a newly-run Pod immediately. This behavior can occur when other clients in the
in a very short (< 30s) time period, consider tuning your DNS settings cluster have already sent queries for the hostname of the Pod before it was created.
or another mechanism (such as querying the Kubernetes endpoints directly for IP addresses). Negative caching (normal in DNS) means that the results of previous failed lookups are
remembered and reused, even after the Pod is running, for at least a few seconds.
If you need to discover Pods promptly after they are created, consider querying the
Kubernetes API directly (for example, using a watch) rather than relying on DNS lookups.
{{< /note >}}
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)
@@ -285,4 +290,3 @@ StatefulSet will then begin to recreate the Pods using the reverted template.
* Follow an example of [running a replicated stateful application](/docs/tasks/run-application/run-replicated-stateful-application/). * Follow an example of [running a replicated stateful application](/docs/tasks/run-application/run-replicated-stateful-application/).