Meetup 23 - 03 - Application Delivery on K8S with GitOps
Download as PPTX, PDF0 likes601 views
This document summarizes a presentation about deploying applications on Kubernetes with GitOps. The presentation covers GitOps workflows and tools like FluxCD and ArgoCD for managing Helm charts from Git repositories. It also discusses integrating continuous integration pipelines with ArgoCD and provides best practices for areas like secret management, scaling, and microservices. The presenter concludes by taking questions and inviting interested parties to join their company.
Meetup 23 - 03 - Application Delivery on K8S with GitOps
- 1. Application Delivery on K8S with GitOps Pham Quang Minh Viet OpenInfra Meetup #23 January 11, 2020
- 2. About me • Pham Quang Minh • DevOps Leader at GAPO • Interested in: • Architecture • Micro-services and Distributed system • Data driven culture
- 3. Agenda GitOps: What / Why? Helm manager: FluxCD vs ArgoCD Intergrate CI and ArgoCD Experience Best practices Scaling ArgoCD Micro-ing the monolith FAQ
- 4. GitOps CI/CD for K8S What / Why?
- 6. Old-fashioned pipeline - CIOps Deployment script, chart,… in project repo Pipeline triggered by any change Hard to manage Security
- 7. Entering GitOps Use Git as the Source of Truth Manifest Configuration State Declarative specification Reliable Observable
- 9. Helm manager: Weave Flux vs ArgoCD
- 10. Continuous Delivery Battle GitOps Flow Helm manager K8S native Fast intergration Flexible Production ready Simple “enough”
- 11. Weave Flux
- 12. ArgoCD
- 13. Weave Flux vs ArgoCD Weave Flux Interval Repo – based Docker registry monitor Auto commit state Cloud / Third party UI One repo, one cluster ArgoCD Interval + webhook Application – based Git manifest monitor Manual commit state Built-in UI Multiple repo, multiple cluster SSO, RBAC,...
- 14. Cool, heh?
- 15. And we choose...
- 16. CI + ArgoCD
- 17. Who is missing?
- 20. Simple updater
- 21. GitlabCI example
- 22. Source Base webhook https://github.com/ncarlier/webhookd Full example with script, chart,… https://github.com/minhpq331/webh ookd-argocd
- 23. Experience
- 24. Best practices Health check is VERY important Separated code & deployment config 1 branch - 1 environment Secret management: Vault, Bitnami Sealed secret,… Tag docker image with commit SHA. Eg: dev-v1-abcdxyz
- 26. Scaling ArgoCD Many applications may cause “Unknown state” ~10 applications per argocd-repo- server
- 27. Micro-ing the monolith Use same chart, same values file Clone “Application” manifest with different name Config routing to 2 “Service” Happy micro-servicing
- 28. What next? Meet their children: GitOps Engine https://github.com/argoproj/gitops-engine
- 29. Questions
- 30. Interested? Join us! Email: [email protected] Telegram: minhpq