GitOps CD for k8s

Transcript

1. GitOps CD for k8s Spiros Economakis
2. What is GitOps?
3. What is GitOps? Versioned CI/CD on top of declarative infrastructure & applications. Stop scripting and start shipping. Kesley Hightower
4. Git as the Source of Truth • A git repo is the single source of truth for the desired state of the whole system • All changes to the desired state are Git commits • All specified are observable, so that we can detect if the desired and observed states are the same (converged) or different (diverged)
5. Is GitOps new?
7. DevOps
8. DevOps • Puppet (kind of) • Chef (kind of) • Salt (kind of) • Terraform cloud etc. etc.
9. GitOps VS existing CI/CD
10. Existing CI/CD • Orchestrating CI pipelines (build, test, merge to trunk) • Automating management of complex multi-step pipelines • CD pipeline step to “push” deployments (applications, infrastructure etc.)
11. Existing CI/CD - Push It is based on “pull” deployments which means an operator observes changes for deployment.
12. GitOps It is based on “pull” deployments which means an operator observes changes for deployment.
13. GitOps - Pull It is based on “pull” deployments which means an operator observes changes for deployment.
14. Example - k8s
15. Pull vs Push • Separation of Concerns • Use any CI and Git server • Events as an integration tool
16. ArgoCD k8s applications
17. What is ArgoCD? Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
19. Declarative setup
20. Hands-on Time
21. Multiple applications Declaratively manage a group of app that can be deployed and configured in concert
22. Hands-on Time
23. Automatic synchronization Automatic synchronisation policy for the applications with: • Auto-prune • Self-heal
24. Hands-on Time
25. Argo Rollouts A canary rollout is a deployment strategy where the operator releases a new version of their application to a small percentage of the production traffic. • Blue green • Canary
26. ArgoCD Benefits • Application health analysis • Automatic drift detection • Version tracking • Easy rollback • Alarming
27. ArgoCD vs Flux Flux allows to connect only one repository per instance of Flux operator ArgoCD can connect multiple git repositories to one cluster
28. ArgoFlux - GitOps Engine Argo + Flux join forces https://www.weave.works/blog/argo-flux-join-forces Share common components as well as backwards-compatibility support for both Argo CD and Flux CD. https://github.com/argoproj/gitops-engine
29. ArgoFlux - GitOps Engine
30. GitOps Benefits • Increased Productivity • Enhanced Developer Experience • Improved Stability • Consistency and Standardization • Stronger Security Guarantees
31. Thanks!!!