"Ingress NGINX was not a minor component. Depending on the analysis, between 41 and 50 percent of internet-facing Kubernetes clusters used it. It shipped as the default ingress controller in RKE2, IBM Cloud Kubernetes Service, and Alibaba ACK, among others."
"The retirement deadline created a near-simultaneous migration event across the industry, and at KubeCon CloudNativeCon Europe, Traefik Labs announced that IBM Cloud, Nutanix, OVHcloud, SUSE, TIBCO, and additional platform vendors have each independently selected Traefik Proxy as their replacement."
"The technical case for Traefik's selection rests primarily on compatibility. Most ingress controllers require teams to rewrite their Ingress resources when migrating away from ingress NGINX, because each controller interprets annotations differently."
The Kubernetes community officially retired Ingress NGINX due to under-resourcing and accumulated technical debt. With no further releases or security patches, organizations using it face vulnerabilities. The retirement prompted a widespread migration, with major platform vendors like IBM Cloud and SUSE selecting Traefik Proxy as their replacement. Traefik's compatibility, including a specific NGINX Provider for easier migration, played a crucial role in its adoption. This transition marks a significant shift in the Kubernetes ecosystem as organizations adapt to the retirement of a widely used component.
Read at TNW | Business
Unable to calculate read time
Collection
[
|
...
]