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
Copy file name to clipboardExpand all lines: README.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,14 @@ The Hetzner Cloud controller manager seamlessly integrates your Kubernetes clust
9
9
10
10
## About the Fork
11
11
12
-
In the long run, we (Syself) would like to switch to the [upstream ccm](https://github.com/syself/hetzner-cloud-controller-manager/) again.
12
+
We plan to support the [upstream hcloud
13
+
ccm](https://github.com/hetznercloud/hcloud-cloud-controller-manager/) in
14
+
[CAPH](https://github.com/syself/cluster-api-provider-hetzner/). After that, this fork is no longer
15
+
needed.
16
+
17
+
## About the Fork (old)
18
+
19
+
In the long run, we (Syself) would like to switch to the [upstream ccm](https://github.com/hetznercloud/hcloud-cloud-controller-manager/) again.
13
20
14
21
A lot of changes were made in the upstream fork, and we don't plan to merge them into our fork.
15
22
@@ -62,10 +69,16 @@ See [CAPH docs](https://syself.com/docs/caph/topics/baremetal/creating-workload-
62
69
63
70
## Usage
64
71
65
-
We recommend to mount the secret `hetzner` as volume and make it available for the container as `/etc/hetzner-secret`.
66
-
Then the credentials are automatically reloaded, when the secret changes.
67
-
When you use hot-reloading, the secret keys must be named `hcloud` (or `token`, for upstream hcloud-ccm compatibility), `robot-user`, and `robot-password`.
68
-
You see an example in the [ccm helm chart](https://github.com/syself/charts/tree/main/charts/ccm-hetzner)
72
+
We recommend to mount the secret `hetzner` as volume and make it available for the container as
73
+
`/etc/hetzner-secret`. Then the credentials are automatically reloaded, when the secret changes.
74
+
75
+
When you use hot-reloading, the secret keys must be named `hcloud` (or `token`, for upstream
76
+
hcloud-ccm compatibility), `robot-user`, and `robot-password`. You see an example in the [ccm helm
0 commit comments