Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we aren’t going to talk about Greek mythology, but about Argo CD, the mythical ship faithfully delivering code to the blue waters of κυβερνήτης.
1. Continuous Integration and Deployment (CI/CD) and GitOps are such important pieces of The DevOps And Cloud Native Experience™®© that the CNCF has at least 6 projects related to CI/CD; Argo CD (recently promoted to version 2.3.0) and Flux being the two most popular of the bunch.
2. How to choose between Argo CD and Flux? What are their similarities and differences? Christian Hernandez from The New Stack tells us everything we need to know.
3. Argo CD is highly addictive; once a team starts using it, the whole organization wants it too. Which raises questions of multi-tenancy, RBAC, scopes, and secret management. The Argo CD team recently published some guidelines for such scenarios.
4. We’ve already mentioned vcluster in a previous issue of VSHN.timer; and here’s the official Argo CD step-by-step guide explaining in detail how to use Argo CD on vcluster.
5. As good as Argo CD is, it’s just software, and it can suffer from some nasty vulnerabilities. In this case, CVE-2022-24348; but the Argo CD team has already published a patch. Are you protected? Learn more about it and secure your clusters.
Are you a Flux or Argo CD person? Do you prefer classic CI/CD pipelines instead? Would you like to share κυβερνήτης tips and tricks with the community? Get in touch with us, and see you next week for another edition of VSHN.timer.
PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.
PS2: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.
PS3: check out our previous VSHN.timer editions about DevOps: #5, #13, #29, #31, #42, and #110.