fluxcd/flux2

Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 7th, 2026
Created on April 24th, 2020
Open Issues & Pull Requests: 258 (+0)
GitHub issues: Enabled
Number of forks: 780
Total Stargazers: 8,387 (+0)
Total Subscribers: 68 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Flux is a continuous delivery solution for Kubernetes that keeps clusters synchronized with configuration sources like Git repositories and OCI artifacts through GitOps principles.

Flux solves the problem of managing Kubernetes cluster state declaratively by continuously reconciling the cluster with desired configuration stored in version control. It works by monitoring Git repositories and other sources, detecting changes, and automatically applying them to the cluster. The tool is built on the GitOps Toolkit, a set of composable Kubernetes APIs and controllers that enable this synchronization. Flux v2 was redesigned from the ground up to leverage Kubernetes' native API extension system, allowing it to integrate seamlessly with the broader Kubernetes ecosystem including Prometheus and other standard components.

Flux suits teams practicing GitOps who want their Kubernetes clusters to be the source of truth for configuration management. It is particularly valuable for organizations needing multi-tenancy support or those managing multiple Git repositories across clusters. The tool handles Helm releases, automated image updates to Git, and secret management through integration with tools like SOPS. Flux v2 represents a significant architectural shift from earlier versions, built natively on Kubernetes custom resources rather than external abstractions, making it more idiomatic for Kubernetes-native deployments.

The project maintains active development with regular updates to its core controllers and APIs. The toolkit components are actively refined to support new use cases and integrations. Documentation is comprehensive and regularly expanded, covering repository structuring, Helm release management, image automation, and secrets handling. The project has established itself as a production-grade solution with adoption across multiple organizations and cloud providers, and it holds graduated status within the Cloud Native Computing Foundation.