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

Issue with k8s.io/docs/tasks/configure-pod-container/static-pod/ (#16189)

Browse Source 
* delete depracted  option --pod-manifest-path

* change configuration file to manifests

* update to suggested wording
This commit is contained in:
mohamed chiheb ben jemaa
2019-10-08 23:51:51 +01:00
committed by Kubernetes Prow Robot
parent 4c56c9e151
commit 849dc428db
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/static-pod.md
+1 -1
View File
@@ -53,7 +53,7 @@ You can configure a static Pod two different ways: either by using configuration
### Filesystem-hosted static Pod manifest {#configuration-files}
The configuration files are just standard Pod definitions in JSON or YAML format in a specific directory. Use `kubelet --pod-manifest-path=<the directory>` to start the kubelet or add the `staticPodPath: <the directory>` field in the [KubeletConfiguration file](/docs/tasks/administer-cluster/kubelet-config-file), which periodically scans the directory and creates/deletes static Pods as YAML/JSON files appear/disappear there.
Manifests are standard Pod definitions in JSON or YAML format in a specific directory. Use the `staticPodPath: <the directory>` field in the [KubeletConfiguration file](/docs/tasks/administer-cluster/kubelet-config-file), which periodically scans the directory and creates/deletes static Pods as YAML/JSON files appear/disappear there.
Note that the kubelet will ignore files starting with dots when scanning the specified directory.
For example, this is how to start a simple web server as a static Pod: