You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cloud Controller Manager (CCM) is responsible for managing node resources in cloud-based Kubernetes environments.
8
+
9
+
Key functions of the Cloud Controller Manager:
10
+
-`Node Management`: It manages nodes by initializing new nodes when they join the cluster (e.g., during scaling up) and removing nodes when they are no longer needed (e.g., during scaling down).
11
+
-`Cloud-Specific Operations`: The CCM ensures that the cloud provider's API is integrated into the Kubernetes cluster to control and automate tasks like load balancing, storage provisioning, and node lifecycle management.
| initContainers | list |`[]`| Add additional init containers to the CCM pods. ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/|
98
+
| hostAliases | list |`[]`| hostAliases Deployment pod host aliases ref: https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/|
71
99
| podAnnotations | object |`{}`| Annotations for data pods. ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/|
| nodeSelector | object |`{}`| Node labels for data pods assignment. ref: https://kubernetes.io/docs/user-guide/node-selection/|
77
106
| tolerations | list |`[{"effect":"NoSchedule","key":"node-role.kubernetes.io/control-plane","operator":"Exists"},{"effect":"NoSchedule","key":"node.cloudprovider.kubernetes.io/uninitialized","operator":"Exists"}]`| Tolerations for data pods assignment. ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/|
78
107
| affinity | object |`{}`| Affinity for data pods assignment. ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity|
79
-
80
-
----------------------------------------------
81
-
Autogenerated from chart metadata using [helm-docs v1.11.2](https://github.com/norwoodj/helm-docs/releases/v1.11.2)
108
+
| extraVolumes | list |`[]`| Additional volumes for Pods |
109
+
| extraVolumeMounts | list |`[]`| Additional volume mounts for Pods |
Copy file name to clipboardExpand all lines: packages/system/proxmox-csi/charts/proxmox-cloud-controller-manager/README.md.gotmpl
+30-6Lines changed: 30 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,12 @@
6
6
7
7
{{ template "chart.description" . }}
8
8
9
+
The Cloud Controller Manager (CCM) is responsible for managing node resources in cloud-based Kubernetes environments.
10
+
11
+
Key functions of the Cloud Controller Manager:
12
+
- `Node Management`: It manages nodes by initializing new nodes when they join the cluster (e.g., during scaling up) and removing nodes when they are no longer needed (e.g., during scaling down).
13
+
- `Cloud-Specific Operations`: The CCM ensures that the cloud provider's API is integrated into the Kubernetes cluster to control and automate tasks like load balancing, storage provisioning, and node lifecycle management.
14
+
9
15
{{ template "chart.homepageLine" . }}
10
16
11
17
{{ template "chart.maintainersSection" . }}
@@ -14,7 +20,22 @@
14
20
15
21
{{ template "chart.requirementsSection" . }}
16
22
17
-
Example:
23
+
## Requirements
24
+
25
+
You need to set `--cloud-provider=external` in the kubelet argument for all nodes in the cluster.
26
+
27
+
## Proxmox permissions
28
+
29
+
```shell
30
+
# Create role CCM
31
+
pveum role add CCM -privs "VM.Audit"
32
+
# Create user and grant permissions
33
+
pveum user add kubernetes@pve
34
+
pveum aclmod / -user kubernetes@pve -role CCM
35
+
pveum user token add kubernetes@pve ccm -privsep 0
0 commit comments