search

haproxy-ingress / charts

HAProxy Ingress helm charts
Apache License 2.0
43 stars 66 forks source link

Reload HAProxy configuration without pod restart #33

Open starteleport opened 3 years ago

starteleport commented 3 years ago

Hi!

I'm using Fluxv2 to deploy haproxy-ingress chart to my cluster. I've noticed that each time I change values that are destined for ConfigMap I have ingress controller pods recreated. AFAIK Flux just issues helm upgrade on values change, so I think it's not related to Flux itself, hence posting here.

I was wondering how could I apply HAProxy config changes without pod recreation? For example, I want to enable logs and have new configuration reloaded by HAProxy itself.

Thanks.

jcmoraisjr commented 2 years ago

Hi, it depends on where the configuration changes. For example if you change how logs are configured, you'll instruct helm to configure a distinct pod template (logging is configured as a sidecar container), and Kubernetes will reflect this reissuing new pods. Please send another examples of config change that restarts the controller, so we can verify if this is the expected behavior.