Continuous Reliability. How?
summary
Claims that Keptn automates delivery and operations by enforcing service level objectives as quality gates inside CI/CD, integrating with Dynatrace and Prometheus, running chaos experiments and performance tests in-pipeline, and even executing auto-remediation (example: toggle a feature flag). Demo shows a release blocked when the 95th-percentile latency hits 1052 ms against a 500 ms SLO, then fixed in a subsequent version and promoted. Tutorials include local k3s setup.
AI-written summary · about
chapters (13)
- 0:00Continuous reliability intro
- 1:04Modern systems complexity
- 3:35Limits of manual SRE
- 4:39Three pillars of reliability
- 5:44Keptn project intro
- 7:30Service level objectives
- 11:03SLOs as quality gates
- 13:09Internal delivery platforms
- 15:14Keptn live demo
- 19:28SLOs with Keptn YAML
- 20:33Chaos engineering pipeline
- 23:23Learning via experiments
- 24:46Building reliability closing
related talks
22mReliability as Code (RaC), A Startup Case Study
37mUsing SLOs for Continuous Performance Optimizations of Your K8s Workloads
36mA Guide to Event-driven SRE-inspired DevOps
27mApplying SRE Principles to CI/CD
49mDeveloping a Culture of Reliability & Resilience through Chaos
27mPutting Chaos Into Continuous Delivery to Increase App...
29mObservability Driven Automation: Beyond GitOps with Keptn
13mBeyond observability: Using reliability scores to drive results