Observability: the Key to Unlocking GitOps
summary
Argues that observability is a prerequisite for GitOps and shows a live Argo CD demo reconciling a declared manifest with the cluster control plane, creating a simple Go web app and changing replica counts to trigger the reconciliation loop. Details: GitOps uses a repo as single source of truth, manifests are declarative, versioned and pulled by agents, and drift is healed automatically. Distinguishes internal observability for controllers from external observability for ops staff and gives four practical takeaways.
AI-written summary · about
chapters (14)
- 0:00intro
- 0:21preface
- 1:03about alex
- 1:26warning! holistic approach: by reference to the whole
- 2:05observability
- 3:49observability vs monitoring
- 5:43gitops
- 8:27gitops plus observability
- 9:18why gitops is so important?
- 9:46what is opengitops?
- 13:24show me the code - demo
- 25:00any conclusion?
- 27:474 key takeaways
- 28:46thanks!
related talks
30mThe Objectives And The Principles Behind GitOps
01h 19mTutorial: Everything You Need To Become a GitOps Ninja
27mImplementing GitOps with ArgoCD: A Practical Guide
35mGitOps - the holy grail of devops
29mDemystifying Gitops with ArgoCD
07mIntroduction to GitOps
09mOpening and Welcome
06mGitOps - At a Glance