From 7267a33db7c39564de884f083da1b5def6d36b78 Mon Sep 17 00:00:00 2001 From: scjane Date: Tue, 14 Feb 2017 14:15:27 +0800 Subject: [PATCH] Update static-pods.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Some of the serial numbers of the ordered list in the "Static pod creation" section are incorrect because items in the list are segmented by code blocks. I think this can be solved in at least the following ways: 1.Remove the ordered list style and just use plain text each beginning with "1", "2"，...,or "step 1", "step 2"，... (My modofication adopts this one) 2.Replace the ordered list with an unordered list in which each item beginning with "step 1", "step 2"，... 3.Use HTML tags, such as
    ,
  1. to give the lists involved Are there any other better ways for this problem? I would be appreciated to know. --- docs/admin/static-pods.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/admin/static-pods.md b/docs/admin/static-pods.md index 8c9e482d0d..7ac6e7c890 100644 --- a/docs/admin/static-pods.md +++ b/docs/admin/static-pods.md @@ -20,13 +20,13 @@ The configuration files are just standard pod definition in json or yaml format For example, this is how to start a simple web server as a static pod: -1. Choose a node where we want to run the static pod. In this example, it's `my-node1`. +1.Choose a node where we want to run the static pod. In this example, it's `my-node1`. ```shell [joe@host ~] $ ssh my-node1 ``` -2. Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: +2.Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: ```shell [root@my-node1 ~] $ mkdir /etc/kubernetes.d/ @@ -48,7 +48,7 @@ spec: EOF ``` -2. Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. On Fedora edit `/etc/kubernetes/kubelet` to include this line: +3.Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. On Fedora edit `/etc/kubernetes/kubelet` to include this line: ```conf KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/" @@ -56,7 +56,7 @@ KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manife Instructions for other distributions or Kubernetes installations may vary. -3. Restart kubelet. On Fedora, this is: +4.Restart kubelet. On Fedora, this is: ```shell [root@my-node1 ~] $ systemctl restart kubelet