Operations | Monitoring | ITSM | DevOps | Cloud

GitOps

The latest News and Information on GitOps and related technologies.

Kubernetes GitOps with Rancher Continuous Delivery

As the number of Kubernetes clusters under management increases, application owners and cluster operators need a programmatic way to approach cluster management. Rancher CD solves this by creating a git driven engine for applying cluster changes. Declarative code is stored in a git repo. As changes are committed to the repo, linked clusters are automatically updated. Gitops keeps all your clusters consistent, version controlled, and reduces the administrative burden as you scale.

Combining Progressive Delivery With GitOps and Continuous Delivery Through Argo CD, Argo Rollouts, and Codefresh

Progressive delivery is arguably the most reliable and advanced set of deployment practices based on a simple idea. Instead of shutting down the old release and deploying a new one in its place, progressive delivery takes an iterative approach. It gradually increases the reach of a new release. That gives us quite a few benefits like zero-downtime deployments, reduced blast radius, increased security, and so on and so forth. I will not go into depth about what progressive delivery is.

ArgoCD Observability Using the New Codefresh GitOps Dashboard

In this article, we will show you how to connect ArgoCD and Codefresh so that you get the full observability experience for GitOps. ArgoCD provides the underlying deployment mechanism and Codefresh the visual dashboard to provide high-level information for deployments. We assume that the following are in place GitOps is a way to do Kubernetes cluster management and application delivery.

Entering GitOps 2.0 with Codefresh and ArgoCD

In our previous article, we explained the vision behind GitOps 2.0 and the features we expect to be covered by GitOps 2.0 tools. In this article, we will see how the new Codefresh GitOps dashboard is the first step towards this vision and more specifically in the area of observability and traceability.

The pains of GitOps 1.0

GitOps as a practice for releasing software has several advantages, but like all other solutions before it, has also several shortcomings. It seems that the honeymoon period is now over, and we can finally talk about the issues of GitOps (and the current generation of GitOps tools) In the article we will see the following pain points of GitOps.

Managing Your Full Application Lifecycle Using #GitOps

#GitOps is nothing new. Or, to be more precise, the principles of GitOps existed long before the term was invented. But hey, that's the pattern in our industry. It is the fate of all good practices to be misunderstood, so we need to come up with new names to get people back on track. That is not to say that we are in a constant loop. Instead, I tend to think of it as a periodic reset trying to eliminate misinterpretations. GitOps is one of those resets. It fosters the practices and the ideas that existed for a while now and builds on top of them.