From bea2c15aa3e8fcb7de29419047a300ef4e0c8b65 Mon Sep 17 00:00:00 2001 From: XsWack Date: Fri, 18 Aug 2017 09:08:48 +0800 Subject: [PATCH] Update static-pod.md Remove blank lines and unified the command line format --- docs/tasks/administer-cluster/static-pod.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/tasks/administer-cluster/static-pod.md b/docs/tasks/administer-cluster/static-pod.md index dd048d2dc5..a4c8671e87 100644 --- a/docs/tasks/administer-cluster/static-pod.md +++ b/docs/tasks/administer-cluster/static-pod.md @@ -84,7 +84,6 @@ If we look at our Kubernetes API server (running on host `my-master`), we see th [joe@my-master ~] $ kubectl get pods NAME READY STATUS RESTARTS AGE static-web-my-node1 1/1 Running 0 2m - ``` Labels from the static pod are propagated into the mirror-pod and can be used as usual for filtering. @@ -97,7 +96,6 @@ pods/static-web-my-node1 [joe@my-master ~] $ kubectl get pods NAME READY STATUS RESTARTS AGE static-web-my-node1 1/1 Running 0 12s - ``` Back to our `my-node1` host, we can try to stop the container manually and see, that kubelet automatically restarts it in a while: