flux

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.