GitOps Is a Placebo (2021)

Is it a hidden ad for Weaveworks? Because counter-arguments are intentionally weak and this piece seems to really promote idea that the "real" gitops require Wavefront (R)(TM) Weave Flux (R)(TM).

I don't really care who popularized term, but we needed a word for "a infra-as-a-code system where changes happen automatically on git push, and therefore git head always matches the real world", and "gitops" is great word to describe this.

Here is my first result on google search for "gitops": https://about.gitlab.com/topics/gitops/ . No mention of Weave products, and Kubernetes is mentioned as "typically used" example, no a requirement by any means.

RedHat says the same: https://www.redhat.com/en/topics/devops/what-is-gitops

For example, right now one of the projects I am working on does _NOT_ use gitops: instead, the files are stored in the repo, and it's up to developer to "terraform apply" after code review is done and code is merged. Sometimes this does not happen, causing the problems. I would like to switch to gitops setup there -- our Jenkins should auto-apply changes on merge. Note that we do not use K8s anywhere, but that'd still be called "gitops".

To me, GitOps means reconciler that can actively move the system (kubernetes or whatever it is) back into the desired state if the actual state changes. Flux is a reconciler.

Everything else is CIOps[1]

[1] https://www.weave.works/blog/kubernetes-anti-patterns-let-s-...