// the find
fluxcd/flux
Successor: https://github.com/fluxcd/flux2
Flux v1 is the original GitOps continuous delivery tool for Kubernetes — it watches a Git repo and syncs your cluster to match. It's EOL as of late 2022 and has been fully superseded by Flux v2 (fluxcd/flux2). Nobody should be starting a new project on this.
The codebase is a decent historical reference for how a GitOps operator was built before the controller-runtime pattern became standard. The versioned RPC API (v6 through v11) in pkg/remote/rpc shows a pragmatic approach to evolving a daemon protocol without breaking existing clients. The registry caching layer with memcached is solid and shows real production thinking around container image polling at scale.
End of life — no security patches, no bug fixes, nothing. The monolithic daemon architecture is exactly what the team admitted was the reason they rewrote it from scratch. No CRD-based API means you can't use kubectl to inspect or manage state in any standard way. Multi-tenancy is flat-out missing; one Flux instance, one Git repo, one cluster — that limitation alone made v2 necessary.