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
I initially set up my production cluster with the default ingress controller traefik, which set up the helm chart for traefik.
Now I'd like to manage the traefik helmchart myself via another automation and tried to set ingress_controller = "none"
The problem is that this variable is tied to the hetzner loadbalancer and therefore terraform wants to destroy it. I tried a few procedures to avoid this, but I couldn't find a way to gracefully opt-out of the deployment of the traefik helm chart. I guess it will behave the same way with nginx.
Thanks for any hints
The text was updated successfully, but these errors were encountered:
Description
Hi folks,
I initially set up my production cluster with the default ingress controller traefik, which set up the helm chart for traefik.
Now I'd like to manage the traefik helmchart myself via another automation and tried to set
ingress_controller = "none"
The problem is that this variable is tied to the hetzner loadbalancer and therefore terraform wants to destroy it. I tried a few procedures to avoid this, but I couldn't find a way to gracefully opt-out of the deployment of the traefik helm chart. I guess it will behave the same way with nginx.
Thanks for any hints
The text was updated successfully, but these errors were encountered: