We have a HAproxy setup where its configurations generated automatically running inside kubernetes. It uses sticky session with targeted server private ip md5/sha hased. In case of our server restart, the private ip may change. And hence the configuration changes. But the client still holding the wrong hash value (previous ip). What is the proper way of Handle this. How can we reset/force client to use new sticky formulas.
Use the static IPs for backend servers
In our case, we can’t guarantee static IPs. Our containers are running inside Kubernetes. So, the ips are dynamically assigned.