I've experimented with several CI/CD tools like Jenkins, Tekton, and ArgoCD, and while they each serve a purpose, they often lead to complexity with too many components or issues with their Kubernetes maintenance. A prime example is the Jenkins Operator, where managing dependencies can be a real nightmare and hasn't improved much over the years. I still use Jenkins and GitHub Actions, but after years of managing my own Kubernetes setups, I'm looking for a way to streamline my workflow. Specifically, I'm on the lookout for a simple, single-binary, Kubernetes-native CI/CD solution that minimizes moving parts and operational headaches. If anyone has insights or experiences around this, or you're interested in discussing designs for a new solution, I'd love to connect!
6 Answers
I just manage things using Fleet. It connects to a GitLab repo for deploying deployments, ingress, services, and helm charts. For building containers, I set an env variable with the commit SHA to let Fleet track changes. We’re using RKE2 and Rancher, so Fleet is integrated, meaning no extra binaries needed on the GitLab CI/CD side.
You should definitely consider GitOps practices! Tools like ArgoCD are excellent for Kubernetes deployment, while FluxCD is simpler and avoids the excess. CI should really focus on building artifacts outside of Kubernetes itself. I personally use GitHub Actions, and their operator works great for self-hosted runners too!
Argo Workflows can be a solid choice for CI. It’s quite powerful and flexible, especially when paired with Argo Events to manage Git triggers. It does need some initial setup, but for container orchestration, it really shines!
You might want to check out Woodpecker. It’s a bit simpler since it operates on a plug-and-play basis, though it does require a server and an agent. But from what I’ve seen, it’s lightweight and could suit your needs!
Thanks for the tip! I’ll definitely explore Woodpecker more closely. If it’s manageable entirely as code, that would be a huge plus!
Are you using RKE2, K3s, or K0s for your setup?
Can you clarify why having a single-binary setup is so important for you?
It’s really about making things simpler overall. I’m aiming for a design that packages all necessary dependencies together so it can run smoothly in a lightweight setup without additional software. I’d like to avoid multiple Pods and separate upgrades for control planes and agents; a more streamlined operation means less headache for me.
I appreciate the recommendation! I know Argo is powerful, but I'm hoping to keep things as lean and code-centric as possible without all the extra resources that come with it.