Open-source GitHub Actions that take your applications from a commit to a healthy Kubernetes cluster. Docker Bake builds every image in a repo and pushes to Amazon ECR, Azure ACR or both. The rendered manifests are committed to your CD repo, and Argo CD syncs them and reports when they are healthy.
▶ See how it fits together — 14 slides
| Action | What it does |
|---|---|
| multicloud-build-action | Docker Bake build, pushed to ECR, ACR or both |
| detect-cloud | Tells a job which cloud its runner is in |
| k8s-load-env | Picks the target cluster from your environment map |
| k8s-deploy | Renders Kustomize manifests into your CD repo and syncs Argo CD |
| k8s-helm-deploy | The same, rendering Helm charts — nothing is helm-installed |
| Auto-Commit-Squash-Merge | Writes to a repo by pull request and squash merge |
| ArgoCD-Manage-Applications | Creates, syncs and health-checks Argo CD applications |
| k8s-restore-cluster | Rebuilds every application on a cluster from the CD repo |
Each does one job, so you can adopt one piece without taking the rest. A typical app repo needs two steps: the build, and one deploy workflow. All are MIT-licensed.
GitOps Manager runs the rest for you, inside your own cloud: self-hosted build runners with Docker Bake on BuildKit, lighter deploy runners, Argo CD, and the environment map of your clusters, DNS zones and registries.
- AWS: EKS Manager · AWS Marketplace
- Azure: AKS Manager
- About us: gitopsmanager.io · contact@gitopsmanager.io