kubectl api-resources shows no Middleware kind under any API group, so this manifest could never apply and was blocking the entire core Kustomization. The Ingress annotation referencing it has been a pre-existing no-op; CORS is actually handled by nginx-queue-proxy.conf and each app's own CORS middleware. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>