Skip to content

Commit dc8c9bc

Browse files
authored
Merge pull request #33680 from my-git9/mygit3
[zh] Update cloud/ccm-example.yaml
2 parents 498bcd3 + 1051cea commit dc8c9bc

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

content/zh/examples/admin/cloud/ccm-example.yaml

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
1-
# This is an example of how to setup cloud-controller-manager as a Daemonset in your cluster.
2-
# It assumes that your masters can run pods and has the role node-role.kubernetes.io/master
3-
# Note that this Daemonset will not work straight out of the box for your cloud, this is
4-
# meant to be a guideline.
1+
# 这是一个如何将 cloud-controller-manager 安装为集群中的 Daemonset 的示例。
2+
# 本例假定你的主控节点可以运行 pod 并具有角色 node-role.kubernetes.io/master
3+
# 请注意,这里的 Daemonset 不能直接在你的云上工作,此例只是一个指导。
54

65
---
76
apiVersion: v1
@@ -42,28 +41,32 @@ spec:
4241
serviceAccountName: cloud-controller-manager
4342
containers:
4443
- name: cloud-controller-manager
45-
# for in-tree providers we use k8s.gcr.io/cloud-controller-manager
46-
# this can be replaced with any other image for out-of-tree providers
44+
# 对于树内驱动,我们使用 k8s.gcr.io/cloud-controller-manager
45+
# 镜像可以替换为其他树外驱动的镜像
4746
image: k8s.gcr.io/cloud-controller-manager:v1.8.0
4847
command:
4948
- /usr/local/bin/cloud-controller-manager
50-
- --cloud-provider=[YOUR_CLOUD_PROVIDER] # Add your own cloud provider here!
49+
- --cloud-provider=[YOUR_CLOUD_PROVIDER] # 在此处添加你自己的云驱动!
5150
- --leader-elect=true
5251
- --use-service-account-credentials
53-
# these flags will vary for every cloud provider
52+
# 这些标志因每个云驱动而异
5453
- --allocate-node-cidrs=true
5554
- --configure-cloud-routes=true
5655
- --cluster-cidr=172.17.0.0/16
5756
tolerations:
58-
# this is required so CCM can bootstrap itself
57+
# 这一设置是必需的,为了让 CCM 可以自行引导
5958
- key: node.cloudprovider.kubernetes.io/uninitialized
6059
value: "true"
6160
effect: NoSchedule
62-
# this is to have the daemonset runnable on master nodes
63-
# the taint may vary depending on your cluster setup
61+
# 这些容忍度使得守护进程能够在控制平面节点上运行
62+
# 如果你的控制平面节点不应该运行 pod,请删除它们
63+
- key: node-role.kubernetes.io/control-plane
64+
operator: Exists
65+
effect: NoSchedule
6466
- key: node-role.kubernetes.io/master
67+
operator: Exists
6568
effect: NoSchedule
66-
# this is to restrict CCM to only run on master nodes
67-
# the node selector may vary depending on your cluster setup
69+
# 这是为了限制 CCM 仅在主节点上运行
70+
# 节点选择器可能因你的集群设置而异
6871
nodeSelector:
6972
node-role.kubernetes.io/master: ""

0 commit comments

Comments
 (0)