Eight definitions of “observability” vs. “monitoring” – and why none of them work

Updated September 2026, 2 weeks ago

Eight definitions of “observability” vs. “monitoring” – and why none of them work - Björn Rabenstein

Scaling in Kubernetes Safely on On-Prem KaaS Across 1,300+ Clusters and 40,000+ Nodes - S. Yoshimura

Navigating the Identity Abyss in the AI‑Native Era - Yuichi Nakamura, Hitachi

Root Without Risk: A Decade-Long Quest for True Container Isolation - Sumir Broota

CNCF Ambassador Prithvi Raj on 14 Years of KubeCon + CloudNativeCon

Longhorn: Intro, Deep Dive and Q&A - Derek Su, SUSE

The Day is Made: Seema Saharan, CNCF Ambassador

$Configuring Argo CD Is Messy: Heres How We Can Fix It - Michael Crenshaw, Intuit Dont miss out! Join us at our next KubeCon + CloudNativeCon events in Shanghai, China (8-9 September, 2026) and Salt Lake City, United States (Nov 9–12, 2026). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at https://kubecon.io Configuring Argo CD Is Messy: Heres How We Can Fix It - Michael Crenshaw, Intuit Argo CD is a powerful system with a lot of configuration options. You can tune performance settings, configure security restrictions, customize the UI, and much more. The configuration options are exposed via many different interfaces such as ConfigMaps, CLI flags, and environment variables. Its often difficult to discover settings, understand the available options, and determine the defaults. This fractured configuration landscape also makes Argo CD difficult to maintain. Its difficult to understand which settings should be exposed where, how to document them, how they affect multi-tenancy, etc. Improving Argo CDs configuration experience is a huge challenge. But with careful planning, we can do it! Argo CD lead maintainer Michael Crenshaw will walk the audience through a proposal to allow configuring Argo CD via a new Custom Resource Definition. Hell walk through the various requirements: backwards compatibility, per-component configuration, migration path, etc.; and hell describe the design decisions that come from each requirement. The audience will learn a lot about how Argo CD works and will get a glimpse into a bright future where configuring Argo is fun and easy!$

ChatLoopBackOff Episode 79: Capsule with Thomas and Oliver

Sandbox for Agentic Application With Cloud Native Stack - Xu Wang, Ant Group & Yu Hu, JAPAN AI

The Next Evolution of Kubernetes: GPU-Centric Infrastructure for AI Workloads - Takao Indoh, Fujitsu

Container Forensics for Kubernetes: Building an Evidence Pipeline With Open Source… J. Wu & P. Garg