GitHub user mark-duggan added a comment to the discussion: Kubernetes traefik ingress controller not creating Public IP
@kiranchavala, thanks for the suggestion. I tried this but it didn't fix my issue. However, I did some more digging into the network configuration and I figured it out myself. I used this article on [Medium](https://weng-albert.medium.com/how-to-adjust-the-pod-ip-range-of-calico-en-bfeb1eb4f454) to reconfigure the IP Pool used by Calico from 192.168.0.0/16 to 172.16.0.0/16, which is not a range which overlaps with anything in my internal network. I think the main problem was that Calico will not nat translate anything that is targetted to a Calico IP Pool address, so the virtual router was eventually dropping the packets, I think due to a routing confusion more than anything, although this is still quite in the weeds of networking and NAT. Once I created a new IP Pool, restarted all the pods in the 192.168.0.0/16 and deleted that original IP Pool, the Cloud Controller Manager pod was able to communicate with the CloudStack API in my configuration and the Public IP/Load Balancer was provisioned GitHub link: https://github.com/apache/cloudstack/discussions/11000#discussioncomment-13453669 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
