The Cloud Native Computing Foundation has unveiled the CARE Program (Certification Advancement & Recertification Experience), a significant restructuring of its certification renewal policy that addresses long-standing…
Platform Engineering Day’s growing emphasis on AI, security, and internal platform maturity is a useful signal: cloud-native teams are moving past raw infrastructure enthusiasm and toward the harder work of building governed, product-like platforms for developers and automation.
The KubeCon + CloudNativeCon India 2026 schedule is less interesting as an event announcement than as a demand signal. AI + ML, observability, operations, platform engineering, and security are showing up together because teams no longer get to treat them as separate tracks in production.
Collector-contrib v0.146.0 brings OTTL context inference to the Filter Processor, reducing config footguns and making filtering rules more readable. Here’s what changes for platform teams running OTel at scale.
The OpenTelemetry project says key parts of its declarative configuration spec are now stable, including the data model schema and YAML representation. That’s a quiet milestone with big implications: versionable config, safer rollout patterns, and vendor-neutral ‘observability as code.’
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.
Collector-contrib v0.146.0 adds context inference to the Filter Processor, letting teams write readable, intent-first OTTL conditions instead of juggling internal contexts. Here’s what changes, how evaluation works, and how to adopt it safely.
Flux 2.8 goes GA with Helm v4 support, server-side apply defaults, kstatus health checks, and new features aimed directly at reducing MTTR in GitOps workflows.
OpenTelemetry’s eBPF Instrumentation project shipped its first alpha release. Here’s what you gain (and what you still don’t) when you shift observability left—down into the kernel.
OpenTelemetry’s eBPF instrumentation (OBI) is now shipping an initial release, pushing the ecosystem toward low-friction, kernel-level telemetry—especially for large fleets where manual instrumentation doesn’t scale. Here’s what eBPF-based signals are good for, where they’re risky, and how to roll them out safely in production.
Flux 2.8 lands Helm v4 support (SSA + kstatus health checks), reduces MTTR by canceling health checks when new revisions appear, and expands GitOps feedback loops with PR/MR comment providers and a new Flux Operator Web UI.
OpenTelemetry’s eBPF Instrumentation project (OBI) just hit its first release. That’s a milestone for low-overhead, zero-code observability—but it also raises new questions about privilege, fleet rollout, and data governance.
CNCF is spotlighting Agentics Day at KubeCon EU 2026 with a focus on MCP and production-grade agents. The real story: interoperability layers are becoming infrastructure. Here’s how to think about MCP as platform plumbing—and how to operate it safely.
CNCF’s ‘Agentics Day: MCP + Agents’ points to a new infrastructure layer: standardized model-to-tool connections under neutral governance. Here’s what platform teams should expect—and what to prototype now.
Kyverno 1.17 stabilizes its next-gen CEL policy engine. That’s more than a version bump: it’s a signal that policy-as-code is shifting toward faster, more standardized evaluation across Kubernetes platforms.
KubeCon + CloudNativeCon Europe heads back to Amsterdam on March 23–26, 2026. Here’s a practical preview of the themes to track—platform engineering, security, observability, and AI—and how to get more value out of the week.
Envoy Gateway v1.7 is another sign the Gateway API ecosystem is moving from ‘early adopter’ to ‘default’. We walk through what a v1.7-style platform setup looks like, plus common pitfalls in production.
Dragonfly v2.4.0 adds scheduling and operational improvements that matter when you’re moving images and artifacts at scale—especially across multi-cluster and edge-heavy architectures.
Dragonfly’s v2.4.0 release brings a load-aware scheduler, a new Vortex transfer protocol, and smarter multi-cluster deployment knobs—pushing P2P image and artifact distribution closer to mainstream platform engineering.
