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
Crossplane is an open-source Infrastructure as Code (IaC) project that enables us to use Kubernetes to provision and manage infrastructure, services, and applications. Combined with Argo CD or Flux, it allows us to apply GitOps principles not only on infrastructure.
Bitnami Sealed Secrets allow us to encrypt secrets safe to store in Git repositories, private or public.
Flux v2 is a tool for converging the actual state (Kubernetes clusters) into the desired state defined in Git. It is a GitOps-based deployment mechanism often used in continuous delivery (CD) processes.
Octant is all the rage. It’s supposed to be the best Kubernetes dashboard on the market. Yet, I failed to see a reason why anyone would use it. Am I wrong? What am I missing?
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.
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.