Introduction to GitOps

Transcript

1. Introduction to GitOps Yosuke Asai
2. My Background
3. My career history and future A University student majoring in backpacking (~ 2018) 
 Studied in Bangkok for a year (2016) Backend & Customer Support engineer for b2b accounting software (~ 2021) DevOps/SRE Engineer for cryptocurrency exchange (~ Present) Work abroad as a software engineer ( Future -)
4. GitOps Overview
5. GitOps is for who… wants to use / uses Kubernetes as application infra operates software with large scale organizations appreciate higher security for the system
6. Basic Introduction Proposed by Weaveworks in 2017 An operating model for building 
 applications on k8s Git as the source of truth Opposite consept: CIOps What is GitOps really ? (source: Weaveworks)
7. –Weaveworks “GitOps is Continuous Delivery meets Cloud Native.”
9. CIOps vs GitOps
10. CIOps Example as an Anti-pattern Ref: https://www.weave.works/blog/kubernetes-anti-patterns-let-s-do-gitops-not-ciops
11. CIOps Example as an Anti-pattern -> Push Credentials for both app and k8s clusters Ref: https://www.weave.works/blog/kubernetes-anti-patterns-let-s-do-gitops-not-ciops Too strong authorization
12. GitOps Pipeline Example Ref: https://www.weave.works/blog/kubernetes-anti-patterns-let-s-do-gitops-not-ciops
13. GitOps Pipeline Example Pull -> Credentials only for Con fi g Repo Ref: https://www.weave.works/blog/kubernetes-anti-patterns-let-s-do-gitops-not-ciops
14. Tools to Achieve GitOps
15. Git Repo GitOps Operators 
 (CD tools for k8s) Cloud Native Infra (K8s)
16. How we are achieving GitOps
18. Bene fi ts vs Drawbacks
19. Bene fi ts Increased productivity with automated delivery Enhanced Developer Experience Improve the security of Kubernetes Cluster CD become independent from CI Stable and Reproducible
20. Bene fi ts Increased productivity with automated delivery Enhanced Developer Experience Improve the security of Kubernetes Cluster CD become independent from CI Stable and Reproducible
21. No Manual work for Delivery
22. Bene fi ts Increased productivity with automated delivery Enhanced Developer Experience Improve the security of Kubernetes Cluster CD become independent from CI Stable and Reproducible
23. Developers are responsible til pushing images DevOps/SRE are responsible for Delivery Responsibility Boundary
24. Bene fi ts Increased productivity with automated delivery Enhanced Developer Experience Improve the security of Kubernetes Cluster CD become independent from CI Stable and Reproducible
25. We can easiliy fi nd 
 when 
 who Changed what
26. Easy & Quick Rollback Git as the source of Truth
27. Drawbacks Increase of the complexity of CI/CD architecture Tools are relatively young Not many documents or functions for settings customizations
28. Thank you for listening. Tell us about your CI/CD at the party!
29. Reference Guide to GitOps 
 https://www.weave.works/technologies/gitops/ Kubernetes anti-patterns: Let's do GitOps, not CIOps! 
 https://www.weave.works/blog/kubernetes-anti-patterns-let-s-do-gitops-not-ciops GitOpsͱCIOpsͷ࿩ 
 https://blog.inductor.me/entry/2021/09/24/015402 GitOps-style continuous delivery with Cloud Build 
 https://cloud.google.com/kubernetes-engine/docs/tutorials/gitops-cloud-build