Source: medium.com
GitOps — A fully declarative way to deploy to KubernetesCategory: Software, Kubernetes, Infrastructure, automation, yaml, ansible, puppet
A lot has changed since the rise of containers & Kubernetes, especially for larger organizations. Deployment automation becomes a lot easier as containers provide a way to package, test and deploy any application to any Cloud platform, behaving in the exact same way.
After the trigger — a point in time — the CD System needs to: The ‘truth’ for your Kubernetes resources is coming from multiple sources, and is not reliable because of the possible “configuration drift”.
The GitOps Operator (like ArgoCD or Flux) lives inside the Kubernetes cluster and will continuously monitor the Git repositories that you configure.
ArgoCD is a GitOps Operator that works with Custom Resource Definitions in Kubernetes, giving the opportunity to set up an organization-wide GitOps architecture using projects and application groups.
After the trigger — a point in time — the CD System needs to: The ‘truth’ for your Kubernetes resources is coming from multiple sources, and is not reliable because of the possible “configuration drift”.
The GitOps Operator (like ArgoCD or Flux) lives inside the Kubernetes cluster and will continuously monitor the Git repositories that you configure.
ArgoCD is a GitOps Operator that works with Custom Resource Definitions in Kubernetes, giving the opportunity to set up an organization-wide GitOps architecture using projects and application groups.
Related Articles
Community Partners
DevOps Careers