Evidence boundary: This is a completed migration of CNCF's named internal-services cluster, not a statement about all CNCF-hosted infrastructure.
What was reported
CNCF replaced ingress-nginx with Envoy Gateway for three named internal services and adopted Kubernetes Gateway API resources for routing.
Verified facts
- ingress-nginx is the predecessor controller.
- Envoy Gateway is the destination.
- Kubernetes Gateway API is part of the new routing model.
- CodiMD, GUAC and kcp are within the documented scope.
What is not established
- Migration of every CNCF-hosted cluster.
- A universal replacement rule for CNCF projects or members.
- The exact retirement date of every old controller instance outside the named cluster.
PlatformTrace analysis
The event is a useful first-party production example of moving from the older Ingress-controller model toward Envoy Gateway and Gateway API without overstating the organisation-wide scope.
Sources
Corrections and updates
No correction is currently open. Additional CNCF cluster migrations will be treated as separate bounded events.