Replies: 2 comments 2 replies
-
Thanks @maggie44, we will do that. But about your use case, did you try external-dns (via helm), super useful and works great with cloudflare too. |
Beta Was this translation helpful? Give feedback.
-
I guess in my brain i thought if i delegated a zone from Cloudflare to Hetzner that these scripts would create DNS needed using the cluster name/domain as the prefix. for example mycluster.domain.com being delegated from cloudflare to hetzner would have cp.mycluster.domain.com for control plane and the hostsname.mycluster.domain.com for dns names - is there any interest in such a pattern? or Is the idea to use external-dns and be done with it? :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In the Hetzner control panel there is the option of adding labels to servers. This feature is already used for some elements of the Terraform deployment, where labels are added to indicate whether a server is a control plane or node (
role=control_plane
for example).It would be nice to be able to add our own labels to this. The current
labels
option for the node pools and control planes only applies to the k3 and not to Hetzner.There is a previous request here for background:
#375
The
extra_hetzner_labels
suggestion seems like it would make sense.My use case is for other Terraform and scripts that interact with the Hetzner API. It reads the current state of the services and then adds DNS entries for node pools to Cloudflare.
Beta Was this translation helpful? Give feedback.
All reactions