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’re going to talk about how teams could adopt GitOps, and what tools can help them do that.
1. Should you adopt GitOps? The answer to that question is, as usual, a resounding it depends. Teams should consider GitOps only if their current culture and practices align well with it, not just for the hype!
2. GitLab is a GitOps platform of choice for lots of companies. And OpenShift is the Kubernetes platform of choice of many of those same companies. So it’s great news to learn that the GitLab operator for Kubernetes and OpenShift is generally available now! By the way, Red Hat is also using GitLab for their own Linux kernel workflow, check the video below for more information.
3. Here’s a tutorial to learn how to use Argo CD deployments in Red Hat OpenShift, using GitHub tokens and the OpenShift GitOps Operator. A very common scenario, and a very handy resource.
4. If you do GitOps with GitHub Actions (and who doesn’t, really?), you’re going to love act: a tool to run GitHub Actions locally. No more waiting for workflows to run: get feedback immediately!
5. There is no shortage of great Git clients out there, but lazygit has won a few users at VSHN lately; snappy, fast, and very, very useful. Check out this video with a 15 minute introduction to lazygit by its author!
Is your team doing GitOps? Which tools are you using? Would you like to share GitOps 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 GitOps: #10, #48, #68, #83, and #98.