ACK will end maintenance for the Nginx Ingress Controller add-on on November 30, 2026, following the upstream Ingress NGINX project retirement.
Change details
The Kubernetes SIG Network and the Kubernetes Security Response Committee announced the retirement of the Ingress NGINX project, with maintenance through March 2026. After that date, no new versions, bug fixes, or security patches for new vulnerabilities will be released. See Ingress NGINX Retirement: What You Need to Know.
Because the NGINX Ingress controller add-on depends on continued upstream maintenance and is not covered by an SLA, ACK will end maintenance on November 30, 2026. Until that date, ACK will continue providing essential support and patches for critical vulnerabilities.
Impact assessment
If you deployed Nginx Ingress Controller from Add-ons or Marketplace, gradually migrate to one of the suggested alternatives. Continued use carries these risks, including but not limited to:
-
API or functional incompatibilities as Kubernetes evolves.
-
No new features or performance optimizations.
-
No security patches, increasing exposure to vulnerabilities.
Recommended alternatives
Migrate to one of the following Ingress solutions for long-term stability and security:
-
APIG Ingress: Cloud-native API Gateway solution, ideal for API management and microservices. See Migrate a self-managed NGINX Ingress to a cloud-native API Gateway.
-
ALB Ingress: Unified cluster ingress using Application Load Balancer (ALB). See Migrate from self-managed NGINX to ALB Ingress.
Other options:
-
Gateway API: Gateway API is the official Kubernetes traffic management standard with enhanced security and extensibility. See Gateway API management.