Ingress-NGINX Retirement Lint

It reads a Kubernetes Ingress manifest and, for every nginx.ingress.kubernetes.io annotation on it, names the Gateway API field that replaces it — HTTPRoute filters, backendRef weights, route timeouts. When there is no core equivalent, such as external auth or source-range allow lists, it says so and flags the finding as an error rather than a warning.

Platform and DevOps engineers holding Ingress YAML on AKS, EKS or GKE clusters that still route through ingress-nginx. It is aimed at the person writing the migration change ticket, who has to state which routing behaviour survives the move to Gateway API and which behaviour has to be rebuilt somewhere else first.

Grep finds annotation names; it does not know which ones have a Gateway API core equivalent. A chatbot will confidently translate an annotation that has no replacement at all, because inventing a plausible field name is exactly what it is good at. This runs a fixed rule set of 30 checks, so the same manifest gives the same answer twice.

Free lints the file you have open, with every finding, line number and replacement field. That is a complete job — nothing is hidden or watermarked. The full version changes scope and ownership: it sweeps every manifest in the workspace in one pass and writes a migration report file you keep and attach to a change ticket.

A freelance Kubernetes consultant bills around $150 an hour, and reading one cluster's ingress manifests annotation by annotation is roughly a day of that work. The bundled two-object fixture alone returns 24 findings, 12 of them errors, which is the shape of what a reviewer would have to write out by hand.