Starting My Journey to Become a Maintainer of Terraform-Provider-Flux

Steve Wade
4 min readMar 28, 2024


Embarking on a journey to contribute to a project as influential as terraform-provider-flux feels like coming full circle. My relationship with Flux began with its inception, a tool that has since become a cornerstone of my professional repertoire. From implementing both v1 and v2 across diverse sectors like financial services and security startups, Flux has been a constant companion. This journey hasn’t just deepened my understanding of its capabilities in automating and managing Kubernetes configurations; it’s also shown me the transformative effect it can have on operational workflows, making them more efficient and streamlined.

The Early Days: Discovering Flux

My initial encounter with Flux was nothing short of revelatory. It offered a glimpse into a future where deployment workflows were not just automated but also intricately linked to the very fabric of infrastructure management. Implementing Flux v1 across various organisations allowed me to see its potential in real-time, solving complex deployment challenges and enhancing productivity.

Evolution and Adaptation: Moving to Flux v2

The evolution from Flux v1 to v2 was a pivotal moment, not just for the project but for me. This transition mirrored the broader shifts within the tech industry towards more sophisticated and scalable solutions. Migrating to Flux v2 wasn’t just an upgrade of tools; it was an upgrade in thinking, approaching deployment and configuration with a new perspective emphasising scalability, reliability, and security. Throughout this transition, the support and guidance from key figures in the Flux community, like Stefan Prodan and others, were invaluable. Their expertise and willingness to share knowledge helped overcome technical challenges but also helped understand the broader impact of these tools on the industry. Sorry Stefan Prodan, for how long it took for me to migrate!

Giving Back: A New Chapter

Now, as I stand on the precipice of a new chapter, aiming to become a maintainer of terraform-provider-flux, it’s a moment of reflection and ambition. This isn’t just about contributing to a project; it’s about giving back to a community that has been instrumental in my growth and the growth of many others. My journey with Flux, from v1 to v2 and everything in between, has equipped me with a unique blend of experiences and insights that I wish to bring to terraform-provider-flux.

I aim to contribute actively to its growth and sustainability, ensuring it continues to serve its users with the innovation and reliability they’ve come to expect. Joining the Flux community organisation on GitHub, I’m excited to leverage my background to foster enhancements, drive adoption, and support the community in navigating the complexities of modern infrastructure management with Flux.

Looking Ahead

My commitment to the terraform-provider-flux project is a professional endeavour and a personal mission to support and nurture the community that has given so much to me. As I embark on this journey, I’m reminded of the countless individuals who’ve made this path possible — from Stefan Prodan, Kingdon and many others who guided me through the early days of Flux to the many users whose feedback and insights have continuously shaped its evolution.

As I take this significant step towards becoming a maintainer of terraform-provider-flux, I’m filled with anticipation for the challenges and opportunities that lie ahead. This journey promises personal growth and the chance to contribute to a project reshaping how we think about GitOps bootstrapping. Here’s to the next chapter in a journey that’s been years in the making.

A Look Back: My Flux v1 Chronicles

As I step forward into this new chapter of contributing as a maintainer for the terraform-provider-flux repository, I find it enlightening and humbling to glance back at the early days of my journey with Flux. The writings from those days chronicled my explorations and challenges and captured the essence of a community coming together to push the boundaries of what’s possible. Below, I’ve linked a collection of my Flux v1 blog posts. These milestones mark significant learning, struggle, and, ultimately, achievement. They’re a testament to where we’ve come from and a reminder of the foundational experiences that shape our perspectives and skills.

Whether you’re new to Flux or have been in the trenches since the beginning, I hope these posts offer you insights, provoke thoughts, or at the very least, provide a bit of nostalgia for the early days of Kubernetes and infrastructure as code.

  1. Increasing Kubeval lint speeds
  2. Upgrading to Helm3 with Flux
  3. Creating a helm repo on GCP
  4. Validating HelmReleases in CI using hrval
  5. Restricting Flux v1 permissions
  6. How to secure the Helm Operator (Flux v1) a little more