You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/workloads/controllers/statefulset.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,8 +148,11 @@ cluster have already sent queries for the hostname of the Pod before it was crea
148
148
Negative caching (normal in DNS) means that the results of previous failed lookups are
149
149
remembered and reused, even after the Pod is running, for at least a few seconds.
150
150
151
-
If you need to discover Pods promptly after they are created, consider querying the
152
-
Kubernetes API directly (for example, using a watch) rather than relying on DNS lookups.
151
+
If you need to discover Pods promptly after they are created, you have a few options:
152
+
153
+
- Query the Kubernetes API directly (for example, using a watch) rather than relying on DNS lookups.
154
+
- Decrease the time of caching in your Kubernetes DNS provider (tpyically this means editing the config map for CoreDNS, which currently caches for 30 seconds).
155
+
153
156
{{< /note >}}
154
157
155
158
As mentioned in the [limitations](#limitations) section, you are responsible for
0 commit comments