#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.

Argo CD: Applying GitOps Principles To Manage Production Environment In Kubernetes: https://youtu.be/vpWQeoaiRM4

Applying Gitops and Continuous Delivery (CD) on Infrastructure Using Terraform, Codefresh, and ...

• Google Kubernetes Engine (GKE): https://codefresh.io/continuous-deployment/applying-gitops-continuous-delivery-cd-infrastructure-using-terraform-codefresh-google-kubernetes-engine-gke/
• AWS Elastic Kubernetes Service (EKS): https://codefresh.io/continuous-deployment/applying-gitops-continuous-delivery-cd-infrastructure-using-terraform-codefresh-aws-elastic-kubernetes-service-eks/
• Azure Kubernetes Service (AKS): https://codefresh.io/kubernetes-tutorial/applying-gitops-continuous-delivery-cd-infrastructure-using-terraform-codefresh-azure-kubernetes-service-aks/

Installing and Managing Argo CD through Continuous Delivery Pipelines Using Codefresh with Google Kubernetes Engine (GKE), AWS Elastic Kubernetes Service (EKS), and Azure Kubernetes Service (AKS): https://codefresh.io/continuous-deployment/installing-managing-argo-cd-continuous-delivery-pipelines-using-codefresh-google-kubernetes-engine-gke-aws-elastic-kubernetes-service-eks-azure-kubernetes-service-aks/