|
| 1 | +# hcloud-cloud-controller-manager Helm Chart |
| 2 | + |
| 3 | +This Helm chart is the recommended installation method for [hcloud-cloud-controller-manager](https://github.com/hetznercloud/hcloud-cloud-controller-manager). |
| 4 | + |
| 5 | +## Quickstart |
| 6 | + |
| 7 | +First, [install Helm 3](https://helm.sh/docs/intro/install/). |
| 8 | + |
| 9 | +The following snippet will deploy hcloud-cloud-controller-manager to the kube-system namespace. |
| 10 | + |
| 11 | +```sh |
| 12 | +# Sync the Hetzner Cloud helm chart repository to your local computer. |
| 13 | +helm repo add hcloud https://charts.hetzner.cloud |
| 14 | +helm repo update hcloud |
| 15 | + |
| 16 | +# Install the latest version of the hcloud-cloud-controller-manager chart. |
| 17 | +helm install hccm hcloud/hcloud-cloud-controller-manager -n kube-system |
| 18 | + |
| 19 | +# If you want to install hccm with private networking support (see main Deployment guide for more info). |
| 20 | +helm install hccm hcloud/hcloud-cloud-controller-manager -n kube-system --set networking.enabled=true |
| 21 | +``` |
| 22 | + |
| 23 | +Please note that additional configuration is necessary. See the main [Deployment](https://github.com/hetznercloud/hcloud-cloud-controller-manager#deployment) guide. |
| 24 | + |
| 25 | +If you're unfamiliar with Helm it would behoove you to peep around the documentation. Perhaps start with the [Quickstart Guide](https://helm.sh/docs/intro/quickstart/)? |
| 26 | + |
| 27 | +### Upgrading from static manifests |
| 28 | + |
| 29 | +If you previously installed hcloud-cloud-controller-manager with this command: |
| 30 | + |
| 31 | +```sh |
| 32 | +kubectl apply -f https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/latest/download/ccm.yaml |
| 33 | +``` |
| 34 | + |
| 35 | +You can uninstall that same deployment, by running the following command: |
| 36 | + |
| 37 | +```sh |
| 38 | +kubectl delete -f https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/latest/download/ccm.yaml |
| 39 | +``` |
| 40 | + |
| 41 | +Then you can follow the Quickstart installation steps above. |
| 42 | + |
| 43 | +## Configuration |
| 44 | + |
| 45 | +This chart aims to be highly flexible. Please review the [values.yaml](./values.yaml) for a full list of configuration options. |
| 46 | + |
| 47 | +If you've already deployed hccm using the `helm install` command above, you can easily change configuration values: |
| 48 | + |
| 49 | +```sh |
| 50 | +helm upgrade hccm hcloud/hcloud-cloud-controller-manager -n kube-system --set monitoring.podMonitor.enabled=true |
| 51 | +``` |
| 52 | + |
| 53 | +### Multiple replicas / DaemonSet |
| 54 | + |
| 55 | +You can choose between different deployment options. By default the chart will deploy a single replica as a Deployment. |
| 56 | + |
| 57 | +If you want to change the replica count you can adjust the value `replicaCount` inside the helm values. |
| 58 | +If you have more than 1 replica leader election will be turned on automatically. |
| 59 | + |
| 60 | +If you want to deploy hccm as a DaemonSet you can set `kind` to `DaemonSet` inside the values. |
| 61 | +To adjust on which nodes the DaemonSet should be deployed you can use the `nodeSelector` and `additionalTolerations` values. |
0 commit comments