From 7927610e05b8a4201a4ea81a590a3919aeb8c6ff Mon Sep 17 00:00:00 2001 From: relyt0925 Date: Wed, 9 Oct 2019 08:03:51 -0500 Subject: [PATCH] remove section saying static pods can't have health checks (#15956) * remove section saying static pods can't have health checks * fix nits --- .../en/docs/tasks/configure-pod-container/static-pod.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/en/docs/tasks/configure-pod-container/static-pod.md b/content/en/docs/tasks/configure-pod-container/static-pod.md index 019a3b359b..1335bd55ea 100644 --- a/content/en/docs/tasks/configure-pod-container/static-pod.md +++ b/content/en/docs/tasks/configure-pod-container/static-pod.md @@ -12,14 +12,13 @@ content_template: templates/task *Static Pods* are managed directly by the kubelet daemon on a specific node, without the {{< glossary_tooltip text="API server" term_id="kube-apiserver" >}} observing them. -Unlike Pods that are managed by the control plane (eg, a -{{< glossary_tooltip text="Deployment" term_id="deployment" >}}; +Unlike Pods that are managed by the control plane (for example, a +{{< glossary_tooltip text="Deployment" term_id="deployment" >}}); instead, the kubelet watches each static Pod (and restarts it if it crashes). -There are no health checks for the containers in a static Pod. Static Pods are always bound to one {{< glossary_tooltip term_id="kubelet" >}} on a specific node. -Kubelet automatically tries to create a {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}} +The kubelet automatically tries to create a {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}} on the Kubernetes API server for each static Pod. This means that the Pods running on a node are visible on the API server, but cannot be controlled from there.