My Pritunl instance keeps creating a new host when the non-persist deployment container in my kubernetes cluster gets destroyed and replaced. I’m not sure if the web server gets a new unique identification recreated when the container is destroyed and recreated, which creates a new host. It is really annoying since those the new hosts don’t contain data about the previous host and it does not attach itself to the original servers that it was assigned to. So the VPN clients cannot connect after the server container is destroyed and recreated automatically. How would I solve this issue?
I am using v1.32.3897.75 0aa1cb Pritunl on Debian 12.
Thank you,
Dre