Testing Service Mesh configs & k8s manifests
summary
Shows concrete checks and tools to catch config errors early: schema validation with kubeval or kubectl --dry-run (flags show spec.replicas must be integer), and opinionated policy checks with conftest backed by OPA/Rego to deny image:latest or privileged containers (demo fails on image:latest). Covers common pitfalls—replica/resource/healthcheck misconfigurations, canary-weight mistakes (90+90 -> >100), and Istio architecture (control plane + Envoy sidecars) plus a note that HashiCorp Consul supports multi-platform/VM meshes.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:36Kubernetes Manifest
- 8:09Failure Stories
- 8:23Configuration Errors
- 9:00Health Checks
- 9:24Graceful Shutdown
- 10:08Fault Tolerance
- 10:47Resource Utilization
- 11:27Best Practices
- 17:10Deployment Manifest
- 19:58Built-in Checkers
- 21:36Custom Validators
- 24:14Deployment Yaml
- 35:24What Are Canary Deployments
- 37:00Early Feedback
related talks
30mA Developer’s Introduction to Service Mesh
01h 01mIstio Service Mesh & pragmatic microservices architecture
53mDo you need a Service Mesh?
19mService Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
50mMulti-Cluster Kubernetes and Service Mesh Patterns
26mAn Introduction to Service Mesh in Action