In case of the traefik charm, I was able to reproduce it as well with James' reproducer. The reason recreating the pod works in traefik rev110 is because it calls the k8s service patch on install/upgrade charm hooks after the pod is recreated both of which do a kubernetes service patch.
From rev 123 of traefik onwards, traefik started patching the service on every update-status hook.
However just recently, it was patched with this [1] which showed that the continuous patching was not needed and just the pebble ready event was missing. That being said, the fact still remains that juju reverts the patch.
For the IP to supply, you can give it any ips, does not matter. I have personally tested this in a single VM.
In case of the traefik charm, I was able to reproduce it as well with James' reproducer. The reason recreating the pod works in traefik rev110 is because it calls the k8s service patch on install/upgrade charm hooks after the pod is recreated both of which do a kubernetes service patch.
From rev 123 of traefik onwards, traefik started patching the service on every update-status hook.
However just recently, it was patched with this [1] which showed that the continuous patching was not needed and just the pebble ready event was missing. That being said, the fact still remains that juju reverts the patch.
For the IP to supply, you can give it any ips, does not matter. I have personally tested this in a single VM.
[1] https:/ /github. com/canonical/ traefik- k8s-operator/ pull/258