Service/model retirement
ingress-nginx annotations rewrite-target auth-url official documentation
A replacement controller passes basic routing but breaks annotations/path rewrites/auth semantics.
Agent Quick Fix
Repair against the current Kubernetes contract, then keep the change narrow and source-backed.
Product: Kubernetes
Current-contract area: Ingress-NGINX behavior-specific migration to Gateway/other controller
Likely root cause: A replacement controller passes basic routing but breaks annotations/path rewrites/auth semantics.
Repair direction: Verifier checks migration to the supported successor and preservation of key behavior/data. Check resource behavior after apply, not only schema acceptance.Symptom
A replacement controller passes basic routing but breaks annotations/path rewrites/auth semantics.
Why This Happens
The integration is locally correct for a resource that no longer exists or is no longer available to the account; only current service lifecycle data resolves it.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
ingress-nginx annotations rewrite-target auth-url official documentation
kubernetes ingress nginx annotations rewrite target external auth docs