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

remove section saying static pods can't have health checks (#15956)

Browse Source 
* remove section saying static pods can't have health checks

* fix nits
This commit is contained in:
relyt0925
2019-10-09 08:03:51 -05:00
committed by Kubernetes Prow Robot
parent 37efc6092a
commit 7927610e05
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/static-pod.md
+3 -4
View File
@@ -12,14 +12,13 @@ content_template: templates/task
*Static Pods* are managed directly by the kubelet daemon on a specific node, *Static Pods* are managed directly by the kubelet daemon on a specific node,
without the {{< glossary_tooltip text="API server" term_id="kube-apiserver" >}} without the {{< glossary_tooltip text="API server" term_id="kube-apiserver" >}}
observing them. observing them.
Unlike Pods that are managed by the control plane (eg, a Unlike Pods that are managed by the control plane (for example, a
{{< glossary_tooltip text="Deployment" term_id="deployment" >}}; {{< glossary_tooltip text="Deployment" term_id="deployment" >}});
instead, the kubelet watches each static Pod (and restarts it if it crashes). 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. 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. on the Kubernetes API server for each static Pod.
This means that the Pods running on a node are visible on the API server, This means that the Pods running on a node are visible on the API server,
but cannot be controlled from there. but cannot be controlled from there.