explaingit

fluxcd/flux

★ 6,865GoAudience · ops devopsComplexity · 4/5Setup · hard

TLDR

Flux v1 is a retired GitOps tool for Kubernetes that automatically syncs your cluster to whatever is committed in a Git repository, now end-of-life and fully replaced by Flux v2.

Mindmap

mindmap
  root((flux v1))
    What it does
      GitOps for Kubernetes
      Auto-sync cluster
      Git-driven deploys
    Status
      End of life
      Use Flux v2
      Migration guide
    History
      Weaveworks origin
      CNCF donation
      Rebuilt as v2
    Audience
      DevOps engineers
      Kubernetes teams
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Migrate an existing Flux v1 setup to Flux v2 using the official migration guide.

USE CASE 2

Understand the history of GitOps tooling from the original Flux project through to the modern GitOps Toolkit.

USE CASE 3

Reference archived v1 code while completing a migration to Flux v2.

Tech stack

GoKubernetes

Getting it running

Difficulty · hard Time to first run · 1day+

This is the archived v1, no longer maintained, new users should go to fluxcd/flux2 instead.

In plain English

This repository holds the source code for Flux v1, the original version of the Flux project, which is now officially retired. Flux is a tool for managing software deployments on Kubernetes clusters using a practice called GitOps, where the desired state of your infrastructure is stored in a Git repository and automatically applied whenever the repository changes. Instead of manually pushing updates to a cluster, Flux watches a Git repo and keeps the running system in sync with whatever is committed there. Flux v1 reached end of life and has been replaced entirely by Flux v2, found at the fluxcd/flux2 repository. Anyone looking to adopt Flux for the first time is directed to v2. Existing users of v1 are pointed to a migration guide, with options for professional help if needed. The project was originally built by Weaveworks and open-sourced in 2016. In 2019 it was donated to the Cloud Native Computing Foundation (CNCF), an organization that oversees many widely used infrastructure projects. As adoption grew, the team decided the original codebase needed a full redesign. In 2020 they began rebuilding Flux from scratch using modern Kubernetes tooling, breaking it into separate specialized components now called the GitOps Toolkit. Flux v2 launched in 2021 with significant improvements: support for multiple Git repositories, multi-tenancy, stronger security, and a free open-source web interface called Weave GitOps. By 2022, v2 had passed security audits and its APIs were considered stable for production use. Major cloud providers including Amazon AWS and Microsoft Azure now offer Flux as part of their managed Kubernetes services. This v1 repository is preserved for historical reference and for teams still working through the migration process.

Copy-paste prompts

Prompt 1
Walk me through the Flux v1 to v2 migration guide step by step for a cluster that uses Helm releases and image automation.
Prompt 2
Compare the key differences between Flux v1 and Flux v2 so I can scope my migration project and estimate effort.
Prompt 3
Explain how GitOps with Flux works in plain English: how does committing to a Git repo automatically update my Kubernetes cluster?
Prompt 4
What is the GitOps Toolkit in Flux v2 and how does it replace the single-binary approach used in Flux v1?
Open on GitHub → Explain another repo

← fluxcd on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.