I've installed ingress-nginx in two namespaces: 'ingress-nginx' and 'ingress-nginx-internal'. For the external ingress, I've configured it to use a public IP, whereas for the internal one, it's set to use a private IP. I'm noticing that sometimes both ingress setups are swapping from public to private IPs, which doesn't seem right. I'm wondering if there's an issue with my Helm chart settings that's causing this. How can I properly configure ingress-nginx to manage both external and internal network traffic without these IP address issues?
2 Answers
Just curious, why are you using both internal and external ingress? I set up Traefik to manage everything on k3s with just one ingress. Seems like it simplifies things, but I'm looking to understand the benefits of your setup better.
It looks like both ingress classes are set to use the same controller value, which might be why they're conflicting. Try changing the "controller.ingressClassResource.controllerValue" in your Helm configuration to have unique values for each ingress class, like "k8s.io/ingress-nginx-pub" for the external and "k8s.io/ingress-nginx-internal" for the internal. This should resolve the issue you're facing with fluctuating IPs.
Thanks for the tip! I applied that change and it worked perfectly!
Good catch! It definitely makes debugging easier when everything's properly separated.