# HaProxy Ingress Controller (DaemonSet Vs.StatefulSet)

**URL:** <https://discourse.haproxy.org/t/haproxy-ingress-controller-daemonset-vs-statefulset/7192>\
**Category:** Help!\
**Created:** [December 10, 2021, 3:14pm UTC](https://discourse.haproxy.org/t/haproxy-ingress-controller-daemonset-vs-statefulset/7192 "2021-12-10T15:14:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anavarro](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/anavarro/32/1590_2.png) [@anavarro](https://discourse.haproxy.org/u/anavarro)\
**Post date:** [December 10, 2021, 3:14pm UTC](https://discourse.haproxy.org/t/haproxy-ingress-controller-daemonset-vs-statefulset/7192/1 "2021-12-10T15:14:15Z")

</div>

I have a Kubernetes Cluster with HaProxy Load Balancer and Ingress Controller.

On Servers I could just add/remove a configs to the haproxy.cfg then reload/restart the haproxy service

However, in kubernetes I’ve had to redeploy haproxy when changes had to be done to a Pod(s) then redeploy those pods again to update haproxy to point traffic there. Is there an easier way to redeploy or update haproxy without taking down and redeploying Pods every time?