Confidence with Chaos for Your Kubernetes Observability
summary
Demo injects DNS failures with Chaos Mesh (NXDOMAIN) against a Kubernetes app, produces a steady memory leak, and trips a Prometheus alert and an SLO violation — proof that chaos can validate alerts and SLOs. Coverage includes using Prometheus/Alertmanager, Grafana dashboards, PrometheusOperator serviceMonitors, OpenTelemetry traces sent to Jaeger, and ideas for scheduled chaos, CI/CD integration, cautious staging, and eBPF/Tetragon for deeper observability.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:24Kubernetes up and running
- 1:44We need monitoring
- 2:21Monitoring, first iteration: Metrics
- 2:47Prometheus: Architecture
- 9:11Chaos Mesh
related talks
37mConfidence with Chaos for your Kubernetes Observability
30mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
39mMake Cloud Native Chaos Engineering Easier - Deep Dive into Chaos Mesh
30mBring Your Chaos to Work Day
32mTesting Kubernetes apps' observability end-to-end
35mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
42mDistributed Monitoring: How to understand the Chaos
01h 22mKeynotes Día 2
