Merge pull request #38161 from chentao1596/correct-description-kubelet-get-pod-from-path

Automatic merge from submit-queue kubelet/get-pods-from-path: correct description of implemention **What this PR does / why we need it**: I find this description does not follow the current implementation, it should be describe like this according to my understanding of the source code.

Merge pull request #38161 from chentao1596/correct-description-kubelet-get-pod-from-path
0a87487b · Kubernetes Submit Queue · GitHub · 3fe19c32 · 785cad95 · 0a87487b
Commit 0a87487b authored May 02, 2017 by Kubernetes Submit Queue Committed by GitHub May 02, 2017
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 2 deletions

server.go cmd/kubelet/app/server.go +3 -2

No files found.
--- a/cmd/kubelet/app/server.go
+++ b/cmd/kubelet/app/server.go
@@ -110,8 +110,9 @@ containers which were not created by Kubernetes.
 Other than from an PodSpec from the apiserver, there are three ways that a container
 manifest can be provided to the Kubelet.
-File: Path passed as a flag on the command line. This file is rechecked every 20
+File: Path passed as a flag on the command line. Files under this path will be monitored
-seconds (configurable with a flag).
+periodically for updates. The monitoring period is 20s by default and is configurable
+via a flag.
 HTTP endpoint: HTTP endpoint passed as a parameter on the command line. This endpoint
 is checked every 20 seconds (also configurable with a flag).