Is Cilium Blocking Ingress Nginx Access?
Asked by
CuriousExplorer47
I'm trying to deploy an application on my OVHcloud VPS using Kubernetes and Ingress. While the app is running and accessible from within the server, I'm getting a 'connection refused' error when I try to access it from any external machines. I noticed that Cilium is installed instead of kube-proxy, which I suspect may have happened as a default during the Kubernetes installation. Could Cilium be blocking the Ingress from forwarding requests to external ports?
Additionally, I observed some unusual configurations for Cilium, such as `kube-proxy-replacement: "false"` even with kube-proxy not being present. It's possible that there are other configuration changes that might help. I've already double-checked the firewall settings and they're all correct. Any insights or suggestions would be greatly appreciated—I've been stuck on this for about a week!
Answers
It sounds like you're facing a classic issue with networking in Kubernetes. You might want to either add kube-proxy to your setup or enable Cilium's eBPF kube-proxy replacement feature. That should help with your Ingress connection problems.
By the way, what load balancer are you using for the ingress-nginx-controller?
Reply to this answer
Add your answer
Answers are reviewed before publication.
AppDev101: Thanks for the tips! I'm using the LoadBalancer service for my ingress-nginx-controller. I didn't build it myself, just applied the configuration from the k8s/ingress-nginx GitHub repository.