OSS + ELC EU 2026

Building on my Google Summer of Code experience, this tutorial addresses one of the major challenges in open source software systems – at scale, file management results in overly complicated templates and bad composability. People put logic into YAML files resulting in non-debuggable pipelines while local modifications are wiped away by upstream updates.
This tutorial delves into the idea of Configuration as Data with the help of kpt tooling allowing for logic separation from configuration files. The idea is to keep YAML "dumb" and pure data, which makes it fully predictable and WYSIWYG.
You’ll get to use the example of the OpenTelemetry Demo - a complex e-commerce microservices application – by packing it in independent and dependent subpackages.
Using KRM functions and custom Starlark scripts you'll:
• switch from a shop selling astronomical equipment to a website offering flowers
• localize languages, currencies, taxes
• manage different deployments sizes (small/medium/large).
As the last point you will use three way merging to allow applying upstream package updates while keeping all local changes safe.