Download to read offline
Uploaded byVMware Tanzu
SpringOne Tour: Doing Progressive Delivery with your Team
The document discusses progressive delivery techniques for safer deployments including traffic shifting, A/B testing, blue/green techniques, and user segmentation. It emphasizes instrumenting applications to monitor rates, errors, and durations (RED metrics) and using these with tools like Flagger to gradually shift traffic to new versions. Continuous delivery, zero-downtime deployments, and a focus on people and decision making are presented as prerequisites.
More Related Content
Similar to SpringOne Tour: Doing Progressive Delivery with your Team
SpringOne Tour: Doing Progressive Delivery with your Team
- 1.
- 2. Doing Progressive Deliverywith Your Team @capileigh stealthybox
- 3. Traffic Shifting Safer Deployments Experimentation -A/B Testing - Blue/Green techniques - User Segmentation - Traffic Mirroring @capileigh stealthybox Progressive Delivery
- 4. Instrument Your Applications -R.E.D. Method ( Rates / Errors / Duration ) - Many service-meshes and ingress-controllers auto-expose RED via Prometheus Flagger can integrate directly /w these metrics @capileigh stealthybox Pre-req:
- 5. Continuous Delivery Zero-Downtime Deployments @capileighstealthybox Pre-req:
- 6. @capileigh Tech doesn’t solveproblems without People Engineering + Product reviewing metrics Optional communication to Stakeholder for promoting a Canary Team Review of key release risks and struggles stealthybox Decision Making
- 7. Traffic Shifting Good forinfrequently hit, read-workloads Header Matching / User Indication Client can flag if a User has “joined the beta program” User Segmentation ( ex: device-type or browser User Agent ) A/B Testing Traffic Sampling, Replay, and Mirroring @capileigh stealthybox Feature Gate Strategy
- 8. General migration strategyfor breaking changes to load-bearing interfaces. ( Classes, Database Schema, API’s, etc. ) Expand Migrate Contract @capileigh stealthybox Parallel Change
- 9. Basic Site Reliability Engineering(SRE) @capileigh stealthybox
- 10. How do Ieven do SRE @capileigh stealthybox
- 11. How do Ieven do SRE Why? @capileigh stealthybox
- 12. Progressive Delivery allowsyou to sample real traffic and measure your mutations ( you need metrics retention ) @capileigh stealthybox
- 13. SLI INDICATOR This is ametric -- typically quantifiable in an automated manner SLO OBJECTIVE SLA AGREEMENT This is an enforceable contract Between the Service Provider and the Consumer Consumer could be internal or external Often Formal + Culturally or Legally binding @capileigh stealthybox SRE Jargon -- Service Levels
- 14.
- 15. “How to FeatureGate” - Describe Policies for Canaries - Durations - Metrics Thresholds - Weighted Routing - Good for infrequently hit routes - Feature persistence can combine with upstream sticky sessions - Header matching - Pre-rollout / Rollout hooks @capileigh stealthybox Flagger capabilities
- 16. RED Metrics Flagger Feature-Gate Strategy DecisionMaking Approach @capileigh stealthybox Progressive Delivery:
- 17. RED /w metricsretention enables: Monitoring SLI's Setting SLO's Keeping SLA's This supports solving problems with Progressive Delivery @capileigh stealthybox SRE:
- 18.