Application lifecycle typically consists of three parts. First, we develop locally, we deploy to temporary environments, usually due to creating pull requests, and we proceed towards a permanent environment, all the way until production. Can we streamline and simplify the whole application lifecycle process by combining Kubernetes, vCluster, DevSpace, Argo CD, k3d, and GitHub Actions? Even if you prefer a different combination, the principles behind this process can be easily applied to a myriad of other tools.Continue reading
Can we make Kubernetes disappear? Can we make infrastructure and application management so simple that anyone can do it? Can we leverage DevOps, SRE, ops, and sysadmin experience to create a system that would make developers autonomous? TL;DR We can do that by combining ArgoCD (GitOps), Crossplane (control plane), Kubevela (OAM), and a few other tools.Continue reading
How to manage infrastructure, applications, and services? How to apply GitOps principles to everything? How to ensure that all the resources are always in-sync? Can we combine infrastructure, application, and service management using ArgoCD and Crossplane?Continue reading
Couchbase is a distributed NoSQL cloud database. The Couchbase Autonomous Operator enables us to automate the management of common Couchbase tasks like, for example, configuration, scaling, and recovery. It lets us focus on the desired configuration and by automating deployment and life-cycle management.
In this video, we are going a step further and applying GitOps principles through ArgoCD.
What do we get if we combine events, workflows, GitOps, progressive delivery, and secrets management? The short answer is that we get automation of everything in Kubernetes in a way that we should be operating in 2021.
We’ll combine Argo Events, Workflows & Pipelines, CD, and Rollouts and sprinkle all that with SealedSecrets, Kaniko, and a few other tools.
Release frequency keeps increasing and, with it, the need to get away from static environments like staging, integration, and other permanent setups. Dynamic environments based on pull requests are probably the best example of a need for a much higher level of dynamism. Kubernetes allows us to easily create whatever we need, and destroy what is not in use. There is no need for anything, especially not environments to be permanent, except for production. We can get far in that direction by combining GitOps practices and Argo CD in a way that each pull request (PR) creates a new environment that is destroyed when a PR is closed. By doing that, we can improve efficiency while, at the same time, reducing the costs.
Argo CD is a declarative GitOps deployment tool for Kubernetes.
It is one of the best, if not the best tool we have today to deploy applications inside Kubernetes clusters. It is based on GitOps principles, and it is a perfect fit to be a part of continuous delivery pipelines. It provides all the building blocks we might need if we would like to adopt GitOps principles for deployments and inject them inside the process of application lifecycle management.
Argo CD is a tool that helps us forget the existence of
helm install, and similar commands. It is a mechanism that allows us to focus on defining the desired state of our environments and pushing definitions to Git. It is up to Argo CD to figure out how to converge our desires into reality.