-
Notifications
You must be signed in to change notification settings - Fork 3
/
cloudlycke-ccm.yaml
70 lines (70 loc) · 2.26 KB
/
cloudlycke-ccm.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: cloudlycke-cloud-controller-manager
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: system:cloud-controller-manager
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: cloudlycke-cloud-controller-manager
namespace: kube-system
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
labels:
k8s-app: cloudlycke-cloud-controller-manager
name: cloudlycke-cloud-controller-manager
namespace: kube-system
spec:
selector:
matchLabels:
k8s-app: cloudlycke-cloud-controller-manager
template:
metadata:
labels:
k8s-app: cloudlycke-cloud-controller-manager
spec:
serviceAccountName: cloudlycke-cloud-controller-manager
containers:
- name: cloudlycke-cloud-controller-manager
imagePullPolicy: Always
# 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
image: mikejoh/cloudlycke-cloud-controller-manager:latest
command:
- /bin/cloudlycke-cloud-controller-manager
args:
- --v=5
- --cloud-provider=cloudlycke
- --cluster-name=kubernetes-2
- --use-service-account-credentials
- --address=127.0.0.1
# these flags will vary for every cloud provider
#- --cloud-config=""
#- --leader-elect=true
#- --allocate-node-cidrs=true
#- --configure-cloud-routes=true
#- --cluster-cidr=172.17.0.0/16
tolerations:
# this is required so CCM can bootstrap itself
- 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
effect: NoSchedule
# this is to restrict CCM to only run on master nodes
# the node selector may vary depending on your cluster setup
nodeSelector:
node-role.kubernetes.io/master: ""