Hey everyone! I'm searching for a new approach to manage Kubernetes deployments and would love your insights. We manage AWS infrastructure for several clients, and while our CI/CD runs through GitLab with Kubernetes agents for deployments upon configuration changes, we've encountered a unique situation. One of our major clients has requested a project that will last around 10 months. At the end of that period, we need to hand over the code and the deployment method, so we don't want it tied to our GitLab setup.
I was considering using ArgoCD for deploying from within the cluster, but I'm not sure if that's too much for what we need. We don't have tons of microservices, and I'd like to steer clear of creating manual scripts, like using Jenkins for example. Any suggestions for lightweight deployment solutions?
5 Answers
Honestly, one straightforward solution could be to just install GitLab on their infrastructure and hand it over as-is. It means less work for you! If you’re looking to innovate, then using this project as a way to experiment with new procedures might be the way to go, but there are plenty of options depending on what skills your team has.
I suggest checking out Kluctl as a lightweight option. It offers flexibility and can keep your deployments less tied to your current GitLab setup, giving you the freedom needed for client handover.
Have you thought about adopting GitOps? I personally prefer Flux over ArgoCD. It's really about the choice between an imperative and a declarative approach—keeping your configs as code can help with auditing and easy rollbacks. Plus, since your stack will be less dependent on GitLab, using GitOps could make things cleaner. Just figure out which GitOps tool suits you best!
I think you're on the right track with GitOps. You've already got some practices in place that align with it. The beauty of GitOps is in decoupling your deployment from your build system—changes in your Git repository reflect in your cluster state automatically. That way, you can choose the right GitOps agent like ArgoCD or FluxCD without being tied to your GitLab infrastructure.
If you're using kubectl right now for your deployments, that's already pretty portable. ArgoCD is a step up in terms of continuous delivery but might not heavily solve your CI issues. Perhaps looking into Tekton for CI could complement your deployment needs.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures