CNL: Kyverno 1.16 — Advancing Policy as Code with CEL and SDK @cncf

Updated September 2026, 2 weeks ago

CNL: Kyverno 1.16 — Advancing Policy as Code with CEL and SDK

KubeEdge DeepDive: Extending Kubernetes To the Edge With Real-World Industry Use Case - Ronak Raj

From Statsd To OpenTelemetry: Atlassians Metrics Platform Migration… I. Grace Endozo & F. Vazirnia

Building an Observability Agent for Rapid Root Cause Analysis using Prometheus metrics - P. Yekbote

From Squire To Network Knight: Defending the Kubernetes Castle the Cloud Native... Donia Chaiehloudj

CNCF Ambassador Arsh Sharma on What Makes the CNCF Community Different

One Binary, Two Ecosystems: Embedding Prometheus Exporters With OCB - Kyle Eckhart & Arthur Sens

Closing Remarks - Yuichi Nakamura, Hitachi, Ltd.

From Model Serving To Distributed Inference: How Llm-d Evolves AI Platforms on… K. Yan & L. He

$Keycloak + Sigstore: Binding Human Identity To Artifact Signatures - Oshi Gupta & Sagar Utekar 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 Keycloak + Sigstore: Binding Human Identity To Artifact Signatures - Oshi Gupta, Improving Pune (Infracloud Technologies) & Sagar Utekar, Crowdstrike Most teams treat signing and identity as two separate problems. Sigstore handles your artifact signatures. Keycloak handles your users. Nobody asks whether the person who triggered that signed build is actually who the signature claims they are. That gap matters more than people realize. In this talk we will walk through how we wired Keycloak directly into Sigstores keyless signing flow as the OIDC provider — so every artifact signature is cryptographically bound to a verified human or service identity that lives in your own identity infrastructure, not GitHubs, not Googles. Your keys, your trust root, your audit trail. Well cover the exact Fulcio configuration that makes this work, how Keycloak realm and client setup maps to Sigstores identity claims, and the operational realities nobody documents — token expiry during long builds, claim mapping mismatches that silently break verification, and how to handle service identities for automated pipelines alongside human developer identities in the same trust domain. If you care about knowing not just what was signed but who actually signed it and whether that person had the right to — this talk is for you.$

A Decade of Cilium Around the World - Liz Rice, Isovalent at Cisco & Hiroki Hanada, Cybozu, Inc.