I’m still going back and forth on the design but we can move the design/implementation discussion to the PR.
> Can you elaborate on how the kubernetes side of this approach will work?
In Kubernetes, each pod (think container) is assigned a unique podIP which is routable within the cluster. This PodIP can change each time a Pod is restarted/scheduled/moved etc. Its also the only ip address that can be bound inside the pod. Obviously using PodIP and public_addr is problematic for MONs since its not stable.
Kubernetes also supports a “service” which is essentially a static IP address allocated and is routable cluster wide (serviceIP to podIP). You can associate the service with a pod (based on pod name, labels etc.). The networking layer will ensure that routes are updated even when the pod moves/restarted etc.
So the idea is to set public_addr to the podIP (also possible with public_network) and mon_advertise_addr to serviceIP.
��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
