# OpenTofu Day Returns to Salt Lake City for KubeCon 2026: Shaping the Future of Infrastructure Provisioning
Most KubeCon and CloudNativeCon gatherings assume that the Kubernetes cluster is already up and running. However, a co-located event taking place on November 9 in Salt Lake City focuses on everything that must be provisioned beforehand: cloud accounts, networking setups, managed services, and the clusters themselves. This gathering, known as OpenTofu Day, is a single-track, community-driven summit designed to bridge the gap between infrastructure creation and cloud-native deployment.
## The Shift in the Infrastructure Landscape
Licensing changes, industry consolidation, and shifting commercial models have prompted many organizations to reevaluate the tooling their infrastructure relies upon. A growing preference for community-governed projects has fueled the rapid ascent of OpenTofu. Once a fork, it has matured into a CNCF Sandbox project, surpassing 10 million downloads as of October 2026. Recent releases have introduced powerful capabilities, including client-side state encryption, enhanced `for_each` support for provider configurations, and OCI registry compatibility.
## Navigating the Migration Path
For most teams, swapping the command-line interface is the straightforward part; OpenTofu is engineered as a drop-in replacement. The complex decision lies in what happens around it—the pipelines, state management, policies, and access controls used to deliver infrastructure changes. Platform engineers generally face two distinct paths. The first is to maintain their existing workflows and simply replace the engine underneath, minimizing immediate disruption. The second is to treat the transition as a catalyst for re-platforming and redesigning how infrastructure changes are delivered entirely. Both paths involve real trade-offs in risk, effort, and long-term flexibility, and the right choice depends entirely on the organization’s specific needs. Hearing directly from teams that have walked both roads is a central value of the upcoming event.
## A Day of Learning and Collaboration
The schedule kicks off with a state-of-the-project update from the core maintainers, covering recent releases, community growth, and future roadmaps. This is followed by an “Ask the Devs” panel, giving attendees the rare opportunity to pose questions directly to the project’s architects. The remainder of the day is filled with practitioner talks covering topics such as migrating legacy workflows, performance optimization and instrumentation at scale, and operating the software within platform engineering teams—including innersource adoption strategies in larger enterprises. Built-in breaks encourage hallway conversations, an environment where many of the day’s most practical insights are naturally exchanged.
## Who Should Attend
The event is specifically tailored for DevOps engineers, platform engineers, and infrastructure leaders. It is especially valuable for teams currently running the predecessor tool in production and evaluating a migration, as they will leave with a clear picture of the trade-offs between keeping existing workflows and re-platforming, guided by teams that have already completed the journey. Existing users will gain insights into how others leverage the latest capabilities and operate at massive scale. Teams building internal developer platforms will find the sessions on provisioning and governance directly applicable, while contributors and prospective contributors will benefit from a full day with the core team, gaining a clear sense of the project’s direction and how they can help shape it. No special preparation is required, though attendees should arrive with a working familiarity with the tool or similar systems and questions about their own infrastructure.
## FAQ
**Q: What is the primary focus of this co-located KubeCon event?**
A: Unlike standard KubeCon sessions that assume a cluster already exists, this event focuses on the provisioning and setup required before and around a cluster, including cloud accounts, networking, and managed services.
**Q: Why are organizations looking to adopt OpenTofu?**
A: Organizations are moving toward this tool due to a desire for community governance in the wake of licensing changes and consolidation in the industry. It has grown rapidly into a CNCF Sandbox project with millions of downloads and new features like client-side state encryption.
**Q: What are the two main approaches to migrating existing infrastructure workflows?**
A: Teams can either keep their existing workflows and swap the underlying engine for minimal disruption, or they can use the migration as an opportunity to completely re-platform and redesign their infrastructure delivery processes.
**Q: Who is the ideal attendee for this gathering?**
A: The day is built for DevOps engineers, platform engineers, and infrastructure leaders, particularly those running the previous tool in production and evaluating a transition, as well as those building internal developer platforms.
**Q: Is prior preparation required to get value out of the day?**
A: No, preparation is not required. The sessions assume familiarity with the tool or similar infrastructure-as-code systems, and attendees who bring questions about their own setups will get the most out of the experience.
## Conclusion
OpenTofu Day represents more than just a technical summit; it is a cornerstone gathering for the infrastructure-as-code community. By uniting core maintainers, production users, and newcomers in one room, the event creates a unique space where real-world problems are solved and the future of provisioning is collaboratively shaped. Whether you are planning a migration, scaling a platform, or simply looking to connect with the engineers building the tools of tomorrow, this summit offers the insights and connections needed to move forward confidently. Thank you for reading
