Downloaded 41 times
Uploaded byVietnam Open Infrastructure User Group
Meetup 23 - 03 - Application Delivery on K8S with GitOps
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.
More Related Content
Similar to Meetup 23 - 03 - Application Delivery on K8S with GitOps
More from Vietnam Open Infrastructure User Group
Meetup 23 - 03 - Application Delivery on K8S with GitOps
- 1. Application Delivery on K8S withGitOps Pham Quang Minh Viet OpenInfra Meetup #23 January 11, 2020
- 2. About me • PhamQuang 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 forK8S What / Why?
- 5.
- 6. Old-fashioned pipeline -CIOps Deployment script, chart,… in project repo Pipeline triggered by any change Hard to manage Security
- 7. Entering GitOps UseGit as the Source of Truth Manifest Configuration State Declarative specification Reliable Observable
- 8.
- 9. Helm manager: Weave Fluxvs ArgoCD
- 10. Continuous Delivery Battle GitOps Flow Helm manager K8S native Fast intergration Flexible Production ready Simple “enough”
- 11.
- 12.
- 13. Weave Flux vsArgoCD 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.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. Source Base webhook https://github.com/ncarlier/webhookd Full example with script, chart,… https://github.com/minhpq331/webh ookd-argocd
- 23.
- 24. Best practices Healthcheck 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
- 25.
- 26. Scaling ArgoCD Manyapplications 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? Meettheir children: GitOps Engine https://github.com/argoproj/gitops-engine
- 29.
- 30. Interested? Join us! Email:[email protected] Telegram: minhpq