Operations | Monitoring | ITSM | DevOps | Cloud

December 2021

Integrating GitOps with DevOps: implementing the best of both

GitOps has become a buzzword. Developers love it, because it folds DevOps into Git, a frequently used and familiar tool. Using one tool to manage multiple DevOps activities sounds fantastic, and it can be helpful for many. The truth is GitOps has limits. In this article, we explore DevOps and GitOps, compare their similarities and differences, and examine how their principles can work together to support your software development goals.

Stop Using Branches for Deploying to Different GitOps Environments

In our big guide for GitOps problems, we briefly explained (see points 3 and 4) how the current crop of GitOps tools don’t really cover the case of promotion between different environments or how even to model multi-cluster setups. The question of “How do I promote a release to the next environment?” is becoming increasingly popular among organizations that want to adopt GitOps.

Using GitOps for Infrastructure and Applications With Crossplane and Argo CD

If you have been following the Codefresh blog for a while, you might have noticed a common pattern in all the articles that talk about Kubernetes deployments. Almost all of them start with a Kubernetes cluster that is already there, and then the article explains how to deploy an application on top. The reason for this simplification comes mainly from brevity and simplicity. We want to focus on the deployment part of the application and not its infrastructure just to make the article easier to follow.

Using Codefresh with GKE Autopilot for native Kubernetes pipelines and GitOps deployment

Several companies nowadays offer a cloud-native solution that manages Kubernetes applications and services. While these solutions seem easy at first glance, in reality, they still require manual maintenance. As an example, an important decision for any Kubernetes cluster is the number of nodes and the autoscaling rules you define.

Top Three Benefits of Using GitOps Driven Multi-Cluster Workload Management via Flux CD

With Kubernetes becoming more and more popular every day, so is managing clusters at scale. Managing Kubernetes clusters the GitOps way via Flux CD operator you can manage thousands of clusters, each with dozens or even hundreds of nodes. GitOps works by using Git as a single source of truth for declarative infrastructure and applications. For a Kubernetes cluster the Git repository hosts all resource manifests making up an application. Flux leverages this principle with a set of controllers watching one or more Git repositories for such manifests and automatically applies them.

Applied GitOps with Kustomize

Have you always wanted to have different settings between production and staging but never knew how? You can do this with Kustomize! Kustomize is a CLI configuration manager for Kubernetes objects that leverage layering to preserve the base settings of the application. This is done by overlaying the declarative YAML artifacts to override default settings without actually making any changes to the original manifest.