Ireland and UK enterprise technology-change research

PT-2026-063 · 20 July 2026

PlatformTrace

Enterprise platform change across Ireland and the United Kingdom.

Runtime platform migration · Completed · High confidence

CNCF migrates internal services from ingress-nginx to Envoy Gateway

CNCF moved CodiMD, GUAC and kcp ingress traffic to Envoy Gateway using Kubernetes Gateway API.

Historical record: This page predates PlatformTrace’s 25 July 2026 Ireland and United Kingdom scope. It is preserved for citation and correction history, but is excluded from active counts, search results and current market coverage. Read the archive policy.
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

  1. CNCF engineering post, 13 April 2026.

Corrections and updates

No correction is currently open. Additional CNCF cluster migrations will be treated as separate bounded events.