When I deploy a Pod, it gets a correct IP (10.42.X.X). However, sometime the Pod is restarted and gets a wriong IP (172.17.X.X.). It seems that 172.17.X.X is the docker0 bridge ip pool.
Have you an idea on why it gives sometimes a wrong ip ? Have you got the same issue ?
Hi @pcasis
we had the same issue on one cluster. Pods running on one specific worker-node got the pod IP from docker-bridge. Drain, delete and reconfigure this worker-node helped.
Maybe that’s related to Kubernetes upgrade to 1.16.3.
How can we monitor stuff like this? We came only across this issue because of application connection errors.
Good question We’ve enabled Monitoring and Logs tools (Grafana/Prometheus/Loki). But those containers are impacted by the IP issue so we can’t really investigate on it …