Ingress Nginx Retirement Lint

A local MCP server that maps retired ingress-nginx annotations to their Gateway API replacement fields, or reports that none exists.

What you can do

This server exposes a linting capability for Kubernetes ingress-nginx configuration. Given a retired ingress-nginx annotation, it names the Gateway API field that replaces it, or tells the user that no replacement exists. It runs locally over stdio and is intended for migration review rather than live cluster changes.

When to use it

Use it when planning or reviewing a migration away from ingress-nginx toward the Gateway API and you need to check which annotations still have a supported equivalent. It is a lookup aid for configuration review, not a deployment tool.

Requirements

Runs as a local process on the user's machine via npx from the npm package @readystack/ingress-nginx-retirement-lint. Desktop only; no web executable. No authentication, environment variables, or headers are declared.