flux

Right. Flux was a handy little tool[1] that sync'd yaml manifests in git repos to live clusters. The concept was fascinating, and the tool was well done--small and efficient. Easy to learn. In 2019, they announced they'd be "merging" with argocd[2]. It seems the merge never really took place, and after that they deprecated flux and announced flux2[3]. The sudden changes of course were a little confusing and perhaps not too well communicated. 1: https://github.com/fluxcd/flux 2: https://discuss.kubernetes.io/t/flux-cd-joins-forces-with-ar... 3: https://github.com/fluxcd/flux2

Looks really neat. We have a not-super-trivial rails app that I want to move to docker one day, but kinda scared to make the jump. We're already using docker for development, plus even have a home-grown docker-compose setup for ephemeral labs, but it's clunky at best. This seems like something that might provide a simple jumping board hopefully... Also bumped into fluxCD[0] recently which also looks interesting. [0] https://github.com/fluxcd/flux

Just use https://github.com/fluxcd/flux — „The GitOps Kubernetes operator”

> It doesn't make all the other yaml files happen. It doesn't make the yaml files you no longer want happening, stop happening. It doesn't even tell you "these things were created by 'old' yaml files" and should be garbage collected (since it doesn't seem to have a sense of old yaml files). This is definitely one piece of Kubernetes that is getting a lot of attention recently. The three tools I've been paying attention to are Argo CD[0], Flux[1], and Config Sync[2]. All of these allow you to point your repository to a cluster and sync resources from the repo to the cluster, including deletes. [0] https://argoproj.github.io/argo-cd/ [1] https://github.com/fluxcd/flux [2] https://cloud.google.com/kubernetes-engine/docs/add-on/confi... Disclaimer: I work at GCP, but not on the GKE team. Opinions are my own.

Flux or Argo can help with this. The operator lives on your cluster, and ensures your cluster state matches a Git repo with all your configuration in it. Flux - https://github.com/fluxcd/flux ArgoCD - https://argoproj.github.io/argo-cd/

My default tends to be Ansible because it is really versatile and lightweight on the systems being managed. That versatility can bite you though because it's easy to use it as a good solution and miss a great one. Also, heaven help you if you need to make a change on 1000s of hosts quickly. I also use (In order of frequency): Terraform, Invoke (Sometimes there is no substitute for a full programming language like python), Saltstack (1000's of machines in a heterogenous environment) If I were going to deploy a new app on k8s today, I would probably use something like https://github.com/fluxcd/flux. I haven't really had a pleasant time with the tooling around serverless ecosystem yet once you get beyond hello worlds and canned code examples.

Looks a lot like http://github.com/weaveworks/flux which we're happy users of at dotmesh.com. Glad to see gitops getting some traction! https://www.weave.works/blog/gitops-operations-by-pull-reque...

Keel looks nice, thanks for making it! Does Keel include any ability to rollback to a previously deployed version? How to you recommend handling that use case? Keel looks similar to Weave Flux (https://github.com/weaveworks/flux). Have you looked at Flux, are you able to compare them? At first glance it looks like Keel is probably easier to setup, but Flux is more feature rich (edits k8s .yaml files in git with updated image tags, has CLI that supports listing deployments and images, can release an old image).

At Weaveworks, we have a built a tool called Flux [1]. It is able to relate manifests in a git repo to images in container registry. It has a CLI client (for use in CI scripts or from developer's workstation), it also has an API server and an in-cluster component, as well as GUI (part of Weave Cloud [2]). Flux is OSS [3], and we use it to deploy our commercial product, Weave Cloud, itself which runs on Kubernetes. 1: https://www.weave.works/continuous-delivery-weave-flux 2: https://cloud.weave.works 3: https://github.com/weaveworks/flux