Flux CD
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
1warn against
Nov 3, 2025first mention
Sep 7, 2026latest mention
Why people recommend it
“Using GitOps (FluxCD) as deployment strategy enables no dependencies on e.g. GitHub Actions.”
“K3s + FluxCD. There's something nice about using git”
Show 2 more
“We use flux for our gitops, and it is easy to bypass if we need to in an emergency.”
Caveats and dissent
“they're messy, they add another layer of complexity, other software to run and troubleshoot, more cognitive load.”
devops/cloud engineer from sysadmin backgroundon “I Am Building a Cloud”
Often compared with
Who recommends it in their own words
Threads where it came up
- Ask HN: Who wants to be hired? (September 2026) 1 mention
- Ask HN: Who is hiring? (July 2026) 1 mention
- I Am Building a Cloud 1 mention
- I tried building my startup entirely on European infrastructure 1 mention
- Docker Swarm vs. Kubernetes in 2026 1 mention
- OpenGitOps 1 mention
Also written as FluxCD. Data: flux-cd.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 9
“GitHub Actions, Python, Typescript, Go, Flux CD”
“Flux”
“they're messy, they add another layer of complexity, other software to run and troubleshoot, more cognitive load.”
“Using GitOps (FluxCD) as deployment strategy enables no dependencies on e.g. GitHub Actions.”
“K3s + FluxCD. There's something nice about using git”
“We use flux for our gitops, and it is easy to bypass if we need to in an emergency.”
“I moved back to using K8S with FluxCD instead”
“fluxCD brings a really nice helm-controller”
“Our stack includes Java, Python, TypeScript, Angular, SQL, AWS, Kubernetes, Postgres, Trino, Flux, Flagger, and Terraform.”