Consul in Azure Kubernetes Service

We have a system in an azure kubernetes cluster, consisting of 7 nodes. 3 of those nodes are consul serviers, forming a quorum. We are encountering a problem, where when the pods restart, their Ip address changes. Thus we are forced to re-configure the consul servers manually.
Is there a way to bypass this issue? As in, a dynamic configuration with consul?

If this has happened to anybody else, please share the feedback!

Thanks in advance!

Hi, are you using the consul helm chart?