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.
SpinKube runs Spin WebAssembly apps on Kubernetes without containers, using a containerd shim and Kubernetes primitives. Pairing it with the Gateway API gives teams a cleaner, role-oriented way to expose WASM services without annotation sprawl.
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.
Logs are expensive because repetition is free to emit and costly to store. The OTel Collector’s log deduplication processor offers a new middle path: compress noise at ingest while preserving incident context.
OpenTelemetry is now mainstream, and the project’s own ‘2025 year in review’ highlights a less-discussed scaling story: documentation localization, contributor growth, and the operational maturity required when observability becomes an industry baseline.
Cloudflare’s February 20, 2026 incident withdrew customer BYOIP routes via BGP. The postmortem is a masterclass in failure domains for ‘network-as-code.’ Here are the actionable cloud-native lessons for change management, blast radius, and rollback.
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.
A quiet but important trend: vendors are shifting OpenTelemetry collector distribution to CDNs. That changes reliability, patch velocity, and how platform teams should govern observability agents.
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.
The Collector is easy to deploy but surprisingly easy to misconfigure at scale. This guide focuses on the practical knobs—pipelines, batching, tail sampling, memory limits, and auth—to turn ‘telemetry works’ into ‘telemetry is reliable.’
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.
Cilium 1.18.7 adds pragmatic improvements—safer default label handling and better Hubble Relay logging options—plus bugfixes that matter in real clusters. Here’s what to pay attention to and how to roll it out without surprises.
Gateway API keeps moving from “promising” to “practical.” Here’s how to evaluate popular implementations in 2026, focusing on operational fit, multi-tenancy, and day-2 upgrades.
Envoy Gateway v1.7 lands with a dense set of Gateway API-adjacent upgrades: richer policy controls, better OTLP export options, safer extension defaults, and breaking changes that signal maturity.
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.
Gateway API is the direction of travel, but teams still need an implementation that can survive production traffic. Envoy Gateway is quietly becoming that default. Here’s what’s maturing, what’s still sharp, and how to adopt it without breaking every app team.
Grafana is positioning its Assistant as an agent grounded in your telemetry and transparent about queries. Here’s how to evaluate that claim—and operationalize it safely.
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.
Internal developer platforms are maturing from catalogs to paved roads with guardrails. The difference is product thinking—and metrics.
