Tracked topic
… In most cases, you can check to find out whether or not you rely on Ingress NGINX by running kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx with cluster administrator permissions. …
… Also, note that Ingress-NGINX and NGINX Ingress are two separate Ingress controllers. Ingress-NGINX is an Ingress controller maintained and governed by the Kubernetes community that is retiring March 2026. NGINX Ingress is an Ingress controller by F5. …
… Its goal is to migrate supported Ingress configuration and behavior identify unsupported configuration and suggest alternatives reevaluate and potentially discard undesirable configuration The rest of the section shows you how to safely migrate the following Ingress-NGINX configuration apiVersion :… …
… Ingress NGINX retirement To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee have retired Ingress NGINX on March 24, 2026. …
… Using a WebSocket client like websocat , an attacker can reach the kubelet 's /exec endpoint directly on port 10250 and execute arbitrary commands: websocat --insecure \ --header "Authorization: Bearer $TOKEN " \ --protocol v4.channel.k8s.io \ "wss:// $NODE IP :10250/exec/default/nginx/nginx?output… …
… Other notable changes Ingress NGINX retirement To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee have retired Ingress NGINX on March 24, 2026. …
… Ingress NGINX retirement For years, the Ingress NGINX controller has been a popular choice for routing traffic into Kubernetes clusters. …
… In alphabetical order: Agentgateway Airlock Microgateway GKE Gateway HAProxy Ingress kgateway NGINX Gateway Fabric Traefik Proxy Get involved Wondering when a feature will be added? …