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/reference/command-line-tools-reference/kubelet.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ node. It can register the node with the apiserver using one of: the hostname; a
12
12
The kubelet works in terms of a PodSpec. A PodSpec is a YAML or JSON object
13
13
that describes a pod. The kubelet takes a set of PodSpecs that are provided through various mechanisms (primarily through the apiserver) and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by Kubernetes.
14
14
15
-
Other than from an PodSpec from the apiserver, there are three ways that a container manifest can be provided to the Kubelet.
15
+
Other than from a PodSpec from the apiserver, there are three ways that a container manifest can be provided to the Kubelet.
16
16
17
17
File: Path passed as a flag on the command line. Files under this path will be monitored periodically for updates. The monitoring period is 20s by default and is configurable via a flag.
0 commit comments