OSS + ELC EU 2026

YAML turned 25 this year.
It is essential to Kubernetes, Docker, Ansible, CI pipelines, and config files for everything in between.
That ubiquity is both a gift and a curse: every change risks breaking something, somewhere, silently.
So how do you grow a data language that a billion files depend on without risk of catastrophe?

Ingy döt Net helped invent YAML and he now maintains the YAML Specification and The YAML Family (libyaml, go-yaml, PyYAML, YAMLStar, YAMLScript etc).
In this talk he'll show how he plans to grow YAML by extension: a plugin system that can deeply affect YAML behavior in completely configurable ways.
Plugin APIs include schema association, tab indent, standard functions, comment support include i18n.
This is being delivered first to go-yaml with the rest of the Family to follow.
The work and its real world feedback will guide future changes to the specification.

One morning, CI across ~1,800 repos ground to a near-total halt. HTTP 401 from github.com, everywhere. Deterministic, not flaky. Valid tokens, healthy rate limits. GitHub support said "anti-abuse." We said "which abuse?"

Twenty days and 17,863,537 log records later, we'd gone deeper into git's open source plumbing than we ever intended: how git negotiates HTTP auth, what it leaks in user-agents, which config knobs actually matter under load, and how its defaults — sensible on a laptop — behave pathologically behind Kubernetes NAT at 50,000 CI runs a day.

This talk is a forensic walkthrough of git's HTTP transport, told through an outage: the red herrings, the tcpdumps, the fixes that didn't work, the fix that did. You'll leave knowing what git clone really does when you're not looking — and how to configure it so it never makes you look guilty.

Bring popcorn.

There is a big difference between getting Kata Containers running in a proof of concept and operating a large multi-tenant Kata environment for years.

This talk is a practical, vendor-neutral look at what becomes hard after the demo works. Once every pod carries a lightweight VM lifecycle behind it, platform teams are no longer operating only Kubernetes. They are also operating guest kernels, guest images, VMMs, hypervisor behavior, virtio devices, runtime and agent version skew, and a second debugging surface under the container platform.

We will walk through production issues that show up at scale: guest kernel CVEs and regressions, host/guest kernel drift, CNI and tap-device networking, virtio-fs and storage durability semantics, fragmented observability, boot storms, vCPU oversubscription, memory accounting drift, NUMA behavior, GPU passthrough, VFIO/IOMMU lifecycle, upgrade matrices, and incident ownership.

This is not a criticism of Kata. Kata solves a real open source isolation problem. The goal is to help operators understand the operational work required to run VM-isolated containers safely and sustainably in production.

Modern infrastructure platforms increasingly combine OpenStack VMs, Kubernetes Pods, managed platforms, and external services, yet connectivity models often remain fragmented across runtime boundaries and tied to infrastructure-specific constructs such as IP-based ACLs.

This session presents how LY Corporation introduced a service-oriented connectivity model across OpenStack and Kubernetes environments. Rather than extending Kubernetes-native service mesh concepts to VM workloads, we introduced a runtime-independent service abstraction where connectivity and policy are defined consistently across VMs, Pods, PaaS instances, and external resources.

Under this model, services become the primary unit for service discovery, authentication and authorization, ACL management, and traffic control, independent of the underlying runtime or network topology. A sidecar proxy enforces service-to-service policy consistently across both OpenStack-managed VMs and Kubernetes workloads.

We cover the architectural design, OpenStack and Kubernetes integration for service registration and identity propagation, and lessons from migrating production workloads at scale.

"Life, uh, finds a way." So do AI agents. Give one a tool, and a prompt-injected README will teach it to spawn a shell. CVE-2025-59528 (CVSS 10.0) and Google's Antigravity sandbox escape proved the same thing twice in 2025: the agent didn't break the sandbox , either the sandbox was missing, or the electric fence was in the wrong place.
This talk is a tour of Jurassic Park, rebuilt on Kubernetes. The paddock walls are containers. The electric fence is kubernetes-sigs/agent-sandbox, swapping gVisor for Kata Containers under the same CRD. The control room is OpenTelemetry where invoke_agent, execute_tool, and tool.policy_check spans turn every isolation verdict into queryable telemetry.
We will deploy OpenClaw ,an open-source AI agent gateway inside a Sandbox resource on Cluster API, watch the agent attempt three different escapes, and ship policy decisions as first-class spans. Help shape OpenTelemetry semconv #3583 before the park opens.

Authoritative DNS is one of the last holdouts against declarative, GitOps-style management. BIND9 still serves a huge share of the world's zone data, but it's driven imperatively: hand-edited zone files, rndc reload, and brittle automation glued on top. bindy is an open-source Kubernetes operator, written in Rust on kube-rs, that closes the gap. It models zones and records as custom resources and continuously reconciles a running BIND9 against them, leaving no orphaned zone file behind.
This talk walks through the architecture of bindy and its sibling projects, bindcar, a sidecar that exposes RNDC operations over a typed API, and hornet, a Rust zone-file parser, then digs into the operator-engineering lessons that transfer to anyone writing controllers in Rust. We'll cover splitting selection from synchronization to avoid reconcile loops, using the reflector and store, modeling ownership and status conditions, and where Rust and kube-rs paid off versus Go's controller-runtime.
Attendees leave with a concrete, reusable pattern for wrapping any stateful, non-cloud-native daemon in a declarative Kubernetes API, and three open-source projects they can adopt, fork, or contribute to.