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