Has anyone found a non-chaotic way to do CI/CD with Kubernetes?
Every Kubernetes setup I’ve touched ends up like this: GitHub Actions, custom Docker registry, Helm, ArgoCD, a dashboard, and some bash scripts.
It works… until it doesn’t.
I’d love to hear if anyone has found a more cohesive way to do CI/CD for Kubernetes, or at least a setup that’s less painful to maintain long-term.
2 comments
[ 4.0 ms ] story [ 19.1 ms ] threadAs added benefit, you can then clone your environments or create ephemeral env on PR (great for dev/testing).
It is a commercial product but has a free tier.
Disclosure: I work for Bunnyshell.