Kubernetes is being rethought
- Companies are questioning whether Kubernetes should be the default orchestration layer for every workload. - Kubernetes 1.36 emphasizes security, removes older defaults and signals the end of Ingress NGINX support. - The shift favors selective platform choices that reduce operational overhead for large consumer services (infoworld.com) (msbiro.net).
Kubernetes is still everywhere, but more companies are dropping the idea that every application needs it. That rethink is colliding with a 2026 release cycle that strips out older defaults and tightens security. (infoworld.com) (kubernetes.io) Kubernetes is software for scheduling containers — packaged applications — across clusters of servers. It became the standard way to run cloud-native systems because it could place workloads, restart failed services, and spread traffic across machines. (kubernetes.io) But running Kubernetes well means operating a platform, not just deploying code. InfoWorld reported on April 21, 2026 that many enterprises now see clusters, upgrades, policy controls, observability, networking, and security as a continuing operational tax that requires scarce specialists. (infoworld.com) That reassessment is landing just as Kubernetes v1.36 is due at the end of April 2026. The project’s March 30 preview said the release includes removals and deprecations, including the deprecation of the `externalIPs` field in Services and other changes aimed at safer defaults. (kubernetes.io) One of the clearest signals is networking. Kubernetes said Ingress NGINX, the long-popular traffic controller for routing web requests into clusters, was retired on March 24, 2026, with no further releases, bug fixes, or security updates after that date. (kubernetes.io) The retirement was announced on November 11, 2025 after maintainers said the project had too few people to keep up with its security burden. The Kubernetes Security Response Committee said features once seen as flexible, including arbitrary NGINX “snippet” annotations, had turned into technical debt and security risk. (kubernetes.io) Kubernetes is steering users toward Gateway API, a newer official project for handling network traffic. The project describes Gateway API as the next generation of Kubernetes Ingress, load balancing, and service mesh APIs, built to separate duties between infrastructure operators and application teams. (gateway-api.sigs.k8s.io) (kubernetes.io) The bigger shift is not that Kubernetes is disappearing. It is that companies are getting more selective: keeping Kubernetes for systems that need portability or deep control, and using managed platform services or simpler runtimes where the extra layer does not pay for itself. (infoworld.com) The wider cloud-native market still leans heavily on Kubernetes. CNCF’s 2024 annual survey, published April 1, 2025, said 80% of respondents were using Kubernetes in production and another 13% were evaluating it, even as respondents also reported concerns about complexity, project longevity, and security vulnerabilities in open-source software. (cncf.io) (blogs.vmware.com) So the 2026 story is less “Kubernetes is over” than “Kubernetes is no longer automatic.” The platform is maturing by removing risky pieces, and its users are maturing by deciding where they actually need it. (kubernetes.io) (infoworld.com)
