Extending Observability to the Application Lifecycle with ArgoCD, Flux and Keptn
summary
Keptn lifecycle toolkit installs as a Helm chart and attaches to Argo/Flux by namespace annotations, caching metrics from Prometheus, Dynatrace and DataDog into a captain metric server that drives HPA and SLO evaluations. It emits OpenTelemetry traces of each sync and deployment and publishes Prometheus-format DORA metrics, and it runs custom pre/post checks as Deno tasks (JavaScript) that gate deploys by exit code so failing prechecks keep a version in pending state.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:27Observability challenges
- 3:57Captain metric server
- 6:03Deployment success metrics
- 7:06Integration complexity solutions
- 9:36Grafana dashboard demo
- 11:45Lifecycle toolkit setup
- 13:31Captain tasks definition
- 15:42Metric server integration
- 17:10Community feedback
- 18:48Q&A: Recovery time
- 20:19Captain application health
- 22:27Ingress and dependencies
- 23:52Multi-cluster models
- 24:36Deployment upgrade triggers
- 25:43Project viability
- 26:45Task automation
- 27:49Trace test integration
- 29:15Closing remarks
related talks
38mAutomated & Observable Deployments with Flux + Keptn
24mOrchestrating and Observing GitOps Deployments with Keptn
36mKeptn Beyond 1.0: Sailing into the Future
29mObservability Driven Automation: Beyond GitOps with Keptn
19mWorking Your Way Through GitOps with Keptn
27mWhy Is It Taking so Long?! Shining the Light on Application..
29mThanks Keptn Obvious! Observable SLOs with Prometheus and Keptn
22mThe Ortelius Journey with GitOps and Event Driven CI/CD