Computer History Museum, Mountain View, CA
Join us for the second KCD San Francisco Bay Area, the biggest gathering for the cloud native and Kubernetes community in the Bay Area! KCD San Francisco Bay Area is a full-day event with sessions that explores the latest cloud native technologies and topics like Cloud Native AI, Platform Engineering, Security, Observability, trending cloud native open source projects, and more.

Join us for amazing opportunities for community networking with some of our industry's most iconic thought leaders and technologists.

The event will take place at the historic Computer History Museum in Mountain View, and as an added bonus, the museum will be open during the day to all event attendees as part of your registration package.


Cap off the day with our vibrant evening social hour, perfect for connecting with industry friends, colleagues, and new acquaintances, or stroll through the Computer History Museum exhibits during the social hour. Whether you are here to learn, share ideas, or make new connections, this event is designed to foster collaboration and knowledge-sharing within the Bay Area's thriving cloud native community.

Guild.ai
Director of Growth and Community
Distinguished Software Engineer at Google Cloud (Kubernetes & GKE)
Uber
Developer Advocate
Dash0
Principal Developer Relations Engineer
ControlPlane
Principal Cloud Native Consultant
CoreWeave
Principal Software Engineer at CoreWeave | Kubernetes AI Conformance Lead
Senior Staff Software Engineer at Google (GKE)
New Relic
Senior Developer Relations Engineer
OpenAI
Scaling Infrastructure for Frontier Models
Adobe
Principal Product Manager
NVIDIA
Director, Open Source Ecoystem and Developer Platform
Testkube
CTO
Archana Anand Senior Software Engineer, Kubernetes Infra Team
Microsoft
Principal Software Engineer
Uber
Senior Staff Engineer, ML Platform
Intuit
Group Development Manager
PayPal
Software Engineer | Distributed Systems, AI, and Platform Engineering
Intuit
Senior Software Engineer
OpenAI
Engineer
Linux Foundation
Certification Community Architect
AWS
Sr Technical Account Manager
EarnIn
Staff Platform Engineer
Intuit
Senior Staff Software Engineer
WSO2
VP & Distinguished Engineer
RX-M
Principal Consultant
EPAM Systems
Lead DevOps
September 1 – 2, 2026
4:00 PM – 2:00 AM (UTC)
Program Chair | CNCF Ambassador | DevRel Architect
Red Hat
Project Manager | SF Chapter Organizer
Special Programs | SF Chapter Organizer
American Red Cross
Sponsors + Finance | CNCF Ambassador
Man Numeric
Program Committee
Over the past decade, cloud native transformed how we build, deploy, and operate software. Containers, Kubernetes, and the CNCF ecosystem became the foundation of modern applications. Now another shift is underway. AI agents are evolving from chat interfaces into systems that can reason, plan, use tools, collaborate, and take action. As these capabilities mature, an important question emerges: How will agentic computing reshape cloud native over the next decade? This talk briefly looks back at the evolution of cloud native before exploring how agents may influence Kubernetes and the broader CNCF ecosystem. We'll examine trends in agent communication, identity, memory, observability, governance, and orchestration, and discuss which cloud native concepts may endure, evolve, or give way to new abstractions. Rather than predicting specific products, this session focuses on the long-term patterns that could define the next generation of distributed systems.
Building machine learning platforms on Kubernetes shouldn't force data scientists to become infrastructure experts. True platform engineering means masking the complexities of cluster manifests, distributed scaling, and fault tolerance so data teams can focus purely on innovation. In this session, Paul Zimmerman and Eric Wang from Uber's Michelangelo team explore how platform engineers can leverage the newly open-sourced Michelangelo framework to build a seamless "Code to Cluster" experience. We’ll dive into strategies for abstracting infrastructure while retaining native control over Kubernetes primitives, deploying complex stacks via Helm, scaling distributed training with Ray and PyTorch, and using CNCF Cadence Workflow for pipeline resilience. Join us to see how to bridge the gap between abstract code and distributed cloud-native scale.
Cloud-native systems have outgrown the incident response playbook. Static runbooks, manual operator intervention, and reactive on-call rotations weren't designed for the scale and complexity of modern distributed systems — and the result is longer outages, inconsistent recoveries, and burned-out engineers. This session introduces an agentic AI approach to disaster recovery, where LLM-based agents don't just advise — they act. Multiple collaborating agents work in concert to detect anomalies, reason about root causes, evaluate recovery strategies, and execute remediation directly through your existing Kubernetes and cloud interfaces. Human oversight remains intact through safety controls for high-impact operations, so you keep the guardrails without the bottlenecks. We'll show real-world results: dramatic reductions in MTTR and operational toil, with measurable improvements in recovery consistency and reliability. More importantly, we'll walk through the architecture — how agents are orchestrated, how they reason under uncertainty, and how this system evolves from a passive advisory tool into an autonomous SRE co-pilot. If you're an SRE, platform engineer, or architect wondering where AI fits into your reliability story, this session gives you a concrete, battle-tested answer.
With agentic workflows, kubectl commands can have dangerous consequences. Improper RBAC can allow agents to kubectl delete, and that includes deleting your whole CI with no commits to roll back to! That’s why Flux's security-first design is even more relevant for agentic GitOps. We'll cover how to use Flux to confine agents to human-reviewable PRs for all sorts of use cases. We’ll do this with a kernel-sandboxing tool called `nono`. In addition, for your agent management tool of choice, we'll cover how to manage your agents' sandboxes with Flux so that nefarious (or confused) agents can't destabilize the security policies that you have in place. We’ll cover safe practices for agentic use cases like: - using Prometheus metrics to trigger resource tuning - troubleshooting and rolling back after HPA crashes - agents requesting additional network access with PR’s for human reviewers Come join in!
Cloud native certifications are shaped by the people who build the exams and the professionals who pursue them. In this lightning talk, AmyJune Hineline will offer a behind-the-scenes look at how subject matter experts help define, develop, and validate certification exams, while Giorgi will share how the Kubestronaut program can support professional growth, continued learning, and community involvement. Together, they will explore two different ways people contribute to and benefit from the cloud native certification landscape and get involved in the CNCF community. Bring your questions, experiences, and certification goals, then continue the conversation with both speakers at the Birds of a Feather table during lunch.
OpenTelemetry's metrics performance has long been a sore point for high-throughput users. Recording a simple Counter with three attributes/labels cost around 50 nanoseconds per call - enough to show up in CPU profiles and rule OpenTelemetry out of the busiest code paths. Pre-resolved metric handles are an old answer. Prometheus client libraries expose labelled-metric handles you can cache, and Windows Performance Counters have used the same pattern for decades. OpenTelemetry now offers it as a first-class API, called bound instruments, and on that same hot path, recording drops to under 2 nanoseconds - roughly 25× faster (Measured in OTel Rust Sdk) This lightning talk shows where the speedup comes from, when to reach for it (high-frequency counters with a fixed, known attribute set), and - more importantly - when not to. Used the wrong way, the new fast path can be slower than the original. Flexible by default, fast when you need it.
Kubernetes gives platform teams powerful building blocks. But turning those into a real developer experience takes months of work. OpenChoreo is a complete, open-source developer platform for Kubernetes. It's ready to use from day one, for both humans and agents. In this lightning talk, I'll walk through how OpenChoreo provides development and platform abstractions on top of Kubernetes. It comes with a Backstage-powered developer portal, plus built-in CI/CD, GitOps, and observability. Developers can self-serve deployments without needing to be Kubernetes experts. These same abstractions also work well for AI agents. Agents need to build, deploy, and operate workloads too, often alongside humans. I'll share what it means to design a platform that serves both audiences from the start. If you're building a platform for your team, or thinking about how agents fit into your Kubernetes setup, this talk is for you. You'll leave with a clear picture of what a CNCF Sandbox developer platform looks like when built for both humans and agents.
1:15 pm Panel: At the Crossroads of AI and Cloud Native - Arun Gupta, NVIDIA; Janet Kuo, Google; Joseph Sandoval, Adobe; Rita Zhang, CoreWeave
1:15 pm Workshop (75 min): Agent workshop with Guild
Platform teams are in between the company's needs to be competitive through agentic strategies and making sure that the internal developers that they support are supported, productive, and meeting security requirements. This workshop will give participants hands-on experience with spinning up agentic environments quickly and ready for use. We will cover 2 use cases: one for engineering team productivity and one for engineering and platform teams to serve internal business teams. By the end of the workshop, participants will have quickly spun up agents, set up context and skills, and have agentic environments that they can continue to maintain, evolve, and improve as needed.
Most teams running the OTel Collector are using it as a passthrough. Data goes in, data goes out and everything lands in the backend whether it is useful or not. That gets expensive fast and it creates compliance problems when PII ends up in your traces. OTTL, the 12:00emetry Transformation Language, ships with every Collector distribution and lets you filter, redact, and normalize telemetry data before it ever leaves your infrastructure. In this session we'll look at the syntax and architecture, walk through real transformation statements for the transform and filter processors, and cover the cases where OTTL makes more sense than building a custom component.
Everyone is racing to deploy LLMs on Kubernetes. Getting a model running is easy, running them efficiently and cost-effective at scale is the real challenge. This talk covers the journey from a vLLM StatefulSet to a production-grade inference platform using llm-d, KServe, and Gateway API Inference Extension. We address three bottlenecks: storage drag from massive model weights, infrastructure lock-in from node affinity, and GPU waste from load balancing that ignores KV-cache locality. See how prefix-cache aware routing delivered 3x throughput and 2x TTFT reduction on Llama 3.1 70B across 4 MI300X GPUs. We also discuss upstream CNCF contributions this work produced and how running at scale hardened these projects for everyone. Walk away with architecture patterns for intelligent LLM routing, real benchmarks, and steps to adopt llm-d + KServe in your clusters.
Large scale inference workloads on Kubernetes are extremely sensitive to rare packet loss: one missing packet can cause seconds of tail latency or failed requests. These incidents are hardest when they cross the visibility boundary between platform teams and cloud-provider infrastructure: node kernel, vNIC driver, hypervisor, and network. In this session, we share an incident response story from OpenAI's scale inference. Starting from latency symptoms and TCP retransmissions, we used targeted eBPF tracing to follow packets through the node stack and vNIC driver. Correlating sequence numbers, skb state, DMA mappings, and completions showed affected packets leaving the guest driver path, narrowing the issue toward cloud infrastructure. That evidence enabled a shadow traffic workaround, validated latency improvement, and built rollout confidence while the provider fix was underway.
For most teams, draining a node isn't something they built. It's a byproduct of the autoscaler, or a kubectl drain script that works until it doesn't. This session showcases a dedicated, multi-cluster node lifecycle controller built to cordon, drain, retire, and replace nodes across a fleet of hundreds of thousands of nodes, hitting every production edge case along the way. It pairs high-scale architecture with the war stories that shaped it: a two-plane design (workload clusters reconciled against a central management hub) and the multi-handler approval protocol built after racing controllers disrupted live workloads. Attendees will learn how to solve stale cache "lies" (dead nodes reporting Ready), bypass pod eviction loops, and design reversible kill switches so unattended fleet automation is crash-safe, leaving with a production-tested blueprint for resilient node automation.
EarnIn operates a high-availability fintech platform on 15+ CNCF projects, including Flux, Karpenter, Kyverno, cert-manager, Linkerd, external-secrets-operator, Argo CD, Velero, and more. When infrastructure components fail silently — cert-manager chains breaking post-upgrade, Velero jobs reporting success without executing — the impact is immediate and customer-facing. To address this, we built a Kubernetes-native testing framework using Testkube that validates our full infrastructure stack on every GitOps-triggered change. Tests are defined as Kubernetes CRDs, integrated into our Flux delivery pipeline, and cover TLS validation, policy enforcement, secret sync, backup integrity, and add-on health across the stack. This session walks through our test architecture, the specific failure classes we catch, and how we operationalized infrastructure testing as a first-class part of our platform engineering workflow — not an afterthought.
PagerDuty goes off. Before a human fully opens the laptop, an AI SRE agent can already be pulling telemetry, checking dashboards, correlating logs, and drafting an incident summary. This talk shows how to design an AI incident-response workflow that integrates with tools like PagerDuty, Datadog, and New Relic to accelerate triage without bypassing safety. What would be covered: • event trigger from alert to investigation • gathering evidence from observability systems • forming a first-pass RCA hypothesis • drafting timelines and incident summaries • keeping humans in the approval loop
CONTACT US