Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
I keep getting 400 Bad Request from Kubernetes with ingress-nginx helm chart
I’m running through the community example How To Set Up an Nginx Ingress on DigitalOcean Kubernetes Using Helm.
I’m using Kubernetes maintained chart rather than stable, since that seems like the most “official” chart, using this
controller: publishService: enabled: true service: annotations: service.beta.kubernetes.io/do-loadbalancer-enable-proxy-protocol: 'true' defaultBackend: enable: true
I can see the load balancer in the DO control panels, and I’ve set up what I think are the correct DNS records:
A hw1.recfab.net <load balancer IP> 3600 TTL A hw2.recfab.net <load balancer IP> 3600 TTL
I keep getting the default NGINX 400 Bad Request page when I hit hw1.recfab.net
, orhw2.recfab.net`. I’ve checked the controller logs, and the service pod logs. I’m pretty sure the requests aren’t reaching the pods, but not sure why.
I’ve tried the Troubleshooting guide, and poked around with
kubectl as well as the ingress-nginx kubectl plugin.
I have not been able to figure this out and I don’t know what else to try. I’m sure it’s something simple, but crucial, so hopefully someone here has a solution.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×