CNCF-hosted Co-located Events Europe 2025

Previously, the biggest constraint in our engineering department was the time it took to make infrastructure changes. In this talk I'll describe the changes we made to both our codebase, and our ways of working to remove that constraint entirely, enabling us to optimise flow across our entire engineering department, and increasing the number of active contributors to our codebase five-fold.

We'll cover how to break apart large codebases to reduce plan and apply time, how to design patterns that are easy to repeat and share, and what we did to handle shared concerns across service boundaries. We'll talk about providers in the hundreds, and workspaces in the thousands.

We'll also briefly touch on how we used this pattern to enable more engineers to work on infra code quickly, and how we enable them to do so safely, and finish up with a few points about what we'd have done differently, and sharing some metrics to illustrate the impact this had.

The core developers in attendance will introduce themselves and briefly talk about their experience working on OpenTofu. We will then open the floor for questions related to all aspects of OpenTofu development.

OpenTofu is just over a year old, and registry requests have already reached more than 6 million per day. That kind of phenomenal growth would be impossible without the foundation of community governance and impartiality that underpins OpenTofu.

In this keynote, OpenTofu Technical Lead Christian Mesh celebrates the role these principles have played in fueling OpenTofu’s innovation and rapid adoption. He’ll set the stage for a day of technical discussions led by community users and experts and share insights into OpenTofu’s future.  

It can be easy to hit the right notes when migrating a Terraform project to OpenTofu. The vast majority of Terraform projects require little to no code changes whatsoever to switch to using the Tofu CLI. But how does an enterprise achieve perfect harmony with Tofu at scale?

Fidelity already had tens of thousands of existing Terraform projects when we made the decision to migrate to OpenTofu. This migration needed to be done at a high tempo, without disrupting the rhythm of engineering teams.

Find out how at Fidelity we have orchestrated a fast, seamless path to OpenTofu at scale. Take away some lessons learned that you can watch out for as you conduct your own migrations - all without missing a beat.

In the complex world of modern cloud infrastructure, how does a small platform team enable 60+ developers to manage infrastructure safely and autonomously?

This talk describes the comprehensive approach to platform engineering used at Sweden's largest commercial video streaming service (TV4 Play) that uses OpenTofu through CDKTF, policy-as-code, strategic tooling, and an obsession over the developer experience to implement self-service infrastructure while maintaining rigorous security and compliance standards.

Code hygiene is important. One or two "code smells" that appear in the course of solving a problem is expected, but if they are not addressed as part of a followup step, the smells can build up and invite all sorts of unexpected activity.
One major code smell is the overuse or misuse of local variables in OpenTofu projects. Oftentimes, these are both difficult to interpret on their own and used in composition with other local variables, compounding obscurity.
In this lightning talk, we will present a series of common scenarios describing the use of local variables. We will review examples both that are appropriate and those that are dizzyingly dense to disentangle, including alternative approaches or ways to mitigate obfuscation, as well as how these phenomena arise.

Infrastructure-as-Code (IAC) has become best practice for managing infrastructure. However, it commonly stops at cloud infrastructure despite supporting so much more.

We will dive into examples of going beyond just the cloud with OpenTofu. A reusable module can create two GitHub repos for app and infra code, two GCP projects for dev/prod with corresponding GitHub environments and the IAM pools and permissions to allow deployment from a main branch's CI to dev and release branch to prod, with approval. All permissions are kept to a minimum to allow security without losing developer velocity. We know the infra needs of the frameworks used by apps and set it up by default, so developers can focus on logic and have tools to debug when they need to. A startup can have all of this with a single "apply".

By the end of the talk, you will know how to take advantage of IAC flexibility to speed up development, and with all the examples being OSS, will also have ready-made tools to start with.

The OpenTofu community continues to roll out features that elevate the IaC experience beyond expectations. This talk dives into the unique and much-awaited capabilities exclusive to OpenTofu, designed to address real-world challenges and enhance flexibility, security, and efficiency in IaC workflows.

Discover how State Encryption ensures sensitive data is protected natively, without the need for external solutions. Explore the game-changing Static Evaluation, enabling unparalleled flexibility by decoupling backend configurations from runtime execution. Learn how the Exclude directive simplifies resource management by letting you ignore specific resources during deployment. Dive into Per-Provider Configuration, a feature that allows you to customize behaviors for each provider in your stack, ensuring optimal performance.
Join us to get these features in action, and to get a sneak peek at an upcoming addition designed to further cement OpenTofu’s position as a leader in the IaC space.