Kubernetes 1.27 released in April 2023. The headline features are incremental, which is appropriate for a platform that now runs an estimated 65% of container workloads in production. The interesting story is the ecosystem around it.
What 1.27 brought
Kubernetes 1.27 promoted several features from beta to stable: improvements to garbage collection for unused images, memory manager enhancements for NUMA-aware resource allocation, and a redesigned approach to handling pod scheduling for nodes with heterogeneous hardware. None of these are user-visible in most workloads. Kubernetes 1.x releases are now largely about engineering excellence in a mature platform rather than fundamental feature addition.
The operator ecosystem
Kubernetes operators, controllers that extend Kubernetes to manage stateful applications, have matured significantly. The operator pattern from CoreOS (2016) is now a standard part of how databases, message queues, and monitoring systems are run on Kubernetes. OperatorHub lists over 250 certified operators. The result is that running Postgres, Kafka, Elasticsearch, and Prometheus on Kubernetes with production-quality lifecycle management is a solved problem.
Cilium as the networking standard
Cilium, the eBPF-based Kubernetes networking plugin, has become the default choice for new clusters at most major cloud providers. EKS, AKS, and GKE all offer Cilium as an option. Its advantages over older CNI plugins are: network policy enforcement at the kernel level (faster than iptables), L7 visibility into HTTP traffic, and the ability to replace kube-proxy entirely. The migration from Flannel or Calico to Cilium requires planning but is worth the operational investment for large clusters.
GitOps as the deployment standard
Argo CD and Flux are now the standard GitOps deployment tools. Both have reached CNCF graduation. The question is no longer whether to do GitOps but which flavour: Argo CD with its UI and application set abstractions, or Flux with its composability and closer alignment to Kubernetes' native API patterns. For new platforms, the choice is often made by team familiarity. For existing platforms, both tools support migration from each other.