Why Is It Taking so Long?! Shining the Light on Application..
summary
Argo CD sync slowdowns are diagnosed by installing Keptn (operator) and annotating the namespace to emit automated OpenTelemetry traces for every workload, with a span per pod and stitched traces across CI and promotion stages. The demo shows a full end‑to‑end trace (one run recorded 2041 seconds) and exposes Prometheus metrics and DORA-style rates in Grafana/Jaeger. Setup is: install Keptn, annotate namespaces, follow labeling/version best practices, and use pre/post deployment evaluations to gate or validate rollouts.
AI-written summary · about
chapters (6)
- 0:00Introductions and welcome
- 2:51Argo CD and its limitations
- 8:10Introducing Keptn
- 13:14Live demo and technical setup
- 21:31Advanced capabilities and resources
- 25:01Q&A session
related talks
15mA Quantitative Study on Argo Scalability
30mExtending Observability to the Application Lifecycle with ArgoCD, Flux and Keptn
29mUnleash ArgoCD Observability Superpowers
27mUntangling the Threads: Understanding Argo Workflows with Workflow Tracing
22mAnalysis in Action: Real-World Metrics Driven Argo Roll...
25mBeyond Production: End-to-End CI/CD Observability With OpenTelemetry
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
28mImprove Monitoring and Observability for Kubernetes with OSS Tools