soup VS pipecd

I'm building a GitOps operator for Kubernetes focused on simplicity. It is functional and you can check the project on GitHub: https://github.com/caldito/soup

Also, you can see here a demo of it: https://asciinema.org/a/439238

It uses SSA (https://kubernetes.io/docs/reference/using-api/server-side-a...) to perform the deployment and has other cool features.

Let me know what you think, hope you find it interesting/useful :)

Demo of performing GitOps using the Soup operator, which can be found at https://github.com/caldito/soup

I'm building a GitOps operator for Kubernetes focused on simplicity.

Now its functional but with many things on the roadmap which is available in the TODO file of the repository (https://github.com/caldito/soup).

It uses SSA(https://kubernetes.io/docs/reference/using-api/server-side-a...) to perform the deployment and has other cool features.

A newer competitor is Fleet, which is developed by Rancher. Its special ability is that it is able to manage not just one, but a fleet of clusters. PipeCD is similarly young and has an even broader focus. Like Fleet, it promises the ability to manage multiple Kubernetes clusters, and it also offers a UI. In addition, it can handle Terraform and some services from the major cloud providers.