Operations | Monitoring | ITSM | DevOps | Cloud

On August 11th, 2021, we conducted a workshop to discuss implementing a GitOps workflow using ArgoCD, Crossplane, and Shipa. We were overwhelmed by the hundreds of people who registered for the session. We believe it shows a few important challenges have to be solved for GitOps to become mainstream across different enterprises. While GitOps brings many benefits, we often see teams facing challenges.

Is GitOps changing observability as we know it? GitOps has been the buzz word in the DevOps space for several years. GitOps, to those that are not familiar, is an operational methodology for DevOps that leverages a continuous deployment approach with Git as the single source of ‘truth’ for declarative control over both infrastructure and applications.

GitHub Actions are a powerful way to add automation to any source code repository. When you take that power and connect it with InfluxDB, you get an amazing combination that allows you to automate data generation, manage GitOps workflows, and a whole lot more. This post will highlight some of the interesting ways to use InfluxDB and GitHub Actions.

Kubernetes allowed us to manage application deployments and infrastructure components using declarative configuration files (yes, those YAMLs that you may not be a fan of ). While dealing with a myriad of YAML files may be loved by some and hated by others, it enables us to host all these files into a Git repository, hook it up to a pipeline (Jenkins, GitLab, etc.), and have a tool apply those changes to a cluster—and voilà, you have GitOps.

GitOps has been getting traction as a cloud-native approach to continuous deployment, leveraging Git for version control. If executed well, GitOps can bring benefits such as automation of your continuous deployment pipeline, lower downtimes, consistency of workflows, and more.

Software development is changing rapidly. On one hand, you must quickly adapt to evolving requirements, while on the other, your applications need to operate continuously without downtime. DevOps helps you quickly adapt to changes. Among other initiatives, continuous integration (CI) and continuous delivery (CD) are intgegral to any DevOps practice.

GitOps is growing in popularity. You’ve probably seen it mentioned on Reddit or dev.to. But what the heck is GitOps? Broadly speaking, GitOps takes the principles of Git and CI-powered workflows favored by software developers — commonly used to automate the process of building, testing and deploying software — and applies them to other business processes.