NGINX sometimes does not take ownership of Ingress objects
Summary
We're noticing more frequently that NGINX sometimes does not take ownership of related Ingress objects.
Symptoms
- Ingresses don't have an associated IP address.
- Tests fail because they can't resolve the domain.
- External DNS doesn't create a record for a domain.
Workarounds
Almost every time, the workaround is to delete the NGINX Pod. When a new one starts, it successfully takes ownership of the Ingress and gives it the IP address.
Related issues
Related to #4866
As well as: