Grafana Cloud AI Observability and the OpenLIT Operator point to a practical operational pattern for LLM workloads on Kubernetes: instrument by policy, collect with OpenTelemetry, and make cost, latency, and quality visible without asking every application team to wire tracing by hand.
Kyverno’s policy-as-code approach keeps gaining traction because it meets Kubernetes teams where they already work: YAML, CRDs, admission control, and cluster-native workflows. The real value is not novelty but operational fit.
Morgan Stanley’s multi-year Flux journey shows that GitOps at enterprise scale is not just about choosing a reconciler. It is about onboarding, tenancy boundaries, source-of-truth design, and relentless tuning once the cluster count and resource count get large.
ARC 0.14.0 introduces multilabel support for runner scale sets, a new scaleset library client, and experimental Helm charts.
Kyverno provides Kubernetes-native Policy-as-Code using YAML instead of Rego, with validation, mutation, and generation policies for cluster governance.
containerd 2.3.0-beta.0 is the first LTS release under the new Kubernetes-aligned schedule, with CRI improvements, EROFS support, and two-year support commitment.
Five critical vulnerabilities dubbed IngressNightmare affect Kubernetes NGINX Ingress Controller versions prior to 1.12.1, with CVE-2025-1974 enabling unauthenticated RCE. Patch immediately.
containerd 2.3.0 introduces the project's first annual LTS release with a new 4-month cadence aligned with Kubernetes. Learn how to upgrade safely.
The Kubernetes image promoter (kpromo) underwent an invisible rewrite that deleted 20% of the codebase while dramatically improving speed and reliability.
Kubernetes 1.34 brings Dynamic Resource Allocation to GA, enabling proper GPU sharing, topology-aware scheduling, and gang scheduling for AI/ML workloads.
Cilium celebrates 10 years at KubeCon Europe with CiliumCon 2026, featuring Cilium v1.19, Tetragon security advances, and sessions on multi-cluster networking at scale.
The Kubernetes community announces a new working group focused on developing standards and best practices for AI Gateway infrastructure, including payload processing, egress gateways, and Gateway API extensions for machine learning workloads.
Helm’s new patch releases do not scream for attention, but the fixes around OCI references, nil-value preservation, generateName handling, YAML post-render corruption, and upgrade wait behavior are exactly the kind that break chart pipelines in annoying, non-obvious ways. Treat this as a validation run, not a casual patch bump.
A new CNCF-highlighted write-up on etcd-diagnosis and etcd-recovery is really a reminder that most Kubernetes control-plane incidents are slowed down by evidence collection, not by lack of heroics. The smart move is to standardize fast checks, deeper diagnostics, and a hard rule that recovery comes last.
A new CNCF deep-dive shows how CRI-O’s credential provider bridges a long-standing Kubernetes gap: mirror authentication that stays namespace-scoped, auditable, and multi-tenant friendly — without smearing credentials across every node.
AWS says Copilot CLI will reach end of support June 12, 2026. If you’ve standardized on Copilot’s manifests and workflows, now is the moment to choose a migration path that preserves your deployment ergonomics while improving infra visibility.
CNCF argues the AI stack is converging on Kubernetes—data pipelines, training, inference, and long-running agents. Here’s what’s actually driving the migration, the hidden operational tax it removes, and the platform-level standards teams should lock in before the next wave hits.
Ingress-NGINX’s March 2026 retirement is forcing real migrations. Here’s a field guide to the weird edge behaviors you must inventory before moving to Gateway API (or another controller) — and how to avoid silent traffic breaks.
EKS Hybrid Nodes lets you pair an AWS-managed control plane with on‑prem or edge worker nodes. Here’s what changes operationally, what doesn’t, and how to evaluate it against EKS Anywhere and plain upstream Kubernetes.
Kubernetes 1.35 introduces an alpha ‘Restart All Containers’ capability that makes a whole‑Pod refresh a first‑class operation. Here’s where it helps, where it can hurt, and how to roll it out safely.