From 1051cead17b2937d19ad2428ca1beccd40707138 Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Sun, 15 May 2022 16:22:33 +0800
Subject: [PATCH] [zh] Update cloud/ccm-example.yaml

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../zh/examples/admin/cloud/ccm-example.yaml  | 31 ++++++++++---------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/content/zh/examples/admin/cloud/ccm-example.yaml b/content/zh/examples/admin/cloud/ccm-example.yaml
index 3bce7b58fa..90bf3344cd 100644
--- a/content/zh/examples/admin/cloud/ccm-example.yaml
+++ b/content/zh/examples/admin/cloud/ccm-example.yaml
@@ -1,7 +1,6 @@
-# This is an example of how to setup cloud-controller-manager as a Daemonset in your cluster.
-# It assumes that your masters can run pods and has the role node-role.kubernetes.io/master
-# Note that this Daemonset will not work straight out of the box for your cloud, this is
-# meant to be a guideline.
+# 这是一个如何将 cloud-controller-manager 安装为集群中的 Daemonset 的示例。
+# 本例假定你的主控节点可以运行 pod 并具有角色 node-role.kubernetes.io/master
+# 请注意，这里的 Daemonset 不能直接在你的云上工作，此例只是一个指导。
 
 ---
 apiVersion: v1
@@ -42,28 +41,32 @@ spec:
       serviceAccountName: cloud-controller-manager
       containers:
       - name: cloud-controller-manager
-        # for in-tree providers we use k8s.gcr.io/cloud-controller-manager
-        # this can be replaced with any other image for out-of-tree providers
+        # 对于树内驱动，我们使用 k8s.gcr.io/cloud-controller-manager，
+        # 镜像可以替换为其他树外驱动的镜像
         image: k8s.gcr.io/cloud-controller-manager:v1.8.0
         command:
         - /usr/local/bin/cloud-controller-manager
-        - --cloud-provider=[YOUR_CLOUD_PROVIDER]  # Add your own cloud provider here!
+        - --cloud-provider=[YOUR_CLOUD_PROVIDER]  # 在此处添加你自己的云驱动！
         - --leader-elect=true
         - --use-service-account-credentials
-        # these flags will vary for every cloud provider
+        # 这些标志因每个云驱动而异
         - --allocate-node-cidrs=true
         - --configure-cloud-routes=true
         - --cluster-cidr=172.17.0.0/16
       tolerations:
-      # this is required so CCM can bootstrap itself
+      # 这一设置是必需的，为了让 CCM 可以自行引导
       - key: node.cloudprovider.kubernetes.io/uninitialized
         value: "true"
         effect: NoSchedule
-      # this is to have the daemonset runnable on master nodes
-      # the taint may vary depending on your cluster setup
-      - key: node-role.kubernetes.io/master
+      # 这些容忍度使得守护进程能够在控制平面节点上运行
+      # 如果你的控制平面节点不应该运行 pod，请删除它们
+      - key: node-role.kubernetes.io/control-plane
+        operator: Exists
         effect: NoSchedule
-      # this is to restrict CCM to only run on master nodes
-      # the node selector may vary depending on your cluster setup
+      - key: node-role.kubernetes.io/master
+        operator: Exists
+        effect: NoSchedule
+      # 这是为了限制 CCM 仅在主节点上运行
+      # 节点选择器可能因你的集群设置而异
       nodeSelector:
         node-role.kubernetes.io/master: ""