Replies: 1 comment
-
I understand your use case. I am adding a note to the backlog about it; what I am thinking is to allow a config setting for the path of a yaml file with overrides for the Helm chart. I can't promise when I can do this though since I have several things planned for the next release and am quite busy with the day job at the moment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've successfully set up multiple clusters with Cilium as CNI, yet the current customization are quite limited. We are using Cilium as an ingress controller, and changed the helm values for Cilium like this, which is working very well:
Unfortunately, any invocation of
hetzner-k3s
to perform cluster changes (e.g. changing node count) resets the helm values for cilium, which also - besides other changes - removes the Load Balancer for Cilium's Ingress Controller and therefore stops all Ingresses from working until the Ingress Controller is activated and the Load Balancer is re-created again.I would propose that the possible configuration values for Cilium are extended to the ones visible in the screenshot. Some values, like the load balancer annotations, can be automatically set if using Cilium as an Ingress Controller, as the LB would not work otherwise anyway.
For reference, the currently possible values are being defined here.
Beta Was this translation helpful? Give feedback.
All reactions