Autoscaling Configuration
Quick Reference
What & Why
Definition
>= 70% of stateless services have horizontal autoscaling based on CPU/memory or custom metrics.
Business Value
Prevents infrastructure drift entirely and reduces environment provisioning time from 2 weeks to 2 hours through versioned infrastructure code Achieving >= 70% services have autoscaling is a key milestone toward this goal.
Context
This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting DF, MTTR improvements.
Success Criteria
>= 70% services have autoscaling
Measurement
Service inventory vs HPA/autoscaling config count
Evidence
- HPA YAML configs
- Autoscaling event logs
- Resource utilization during scale events
In Practice
Real-World Implementation
Teams configure Kubernetes HPA or cloud autoscaling: min 2 replicas, max 10 replicas, scale at 70% CPU, cooldown 2min.
Concrete Example
Implementation Guide
Prerequisites
Implementation Steps
Follow the measurement approach: Service inventory vs HPA/autoscaling config count
For detailed step-by-step guidance, refer to the Infrastructure & Operations Baseline Implementation Kit.
Resources
Implementation Kit
Infrastructure & Operations Baseline KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Prerequisites
Implement these first
Enables
What this unlocks
Complementary
Often adopted together, from the Infrastructure & Operations Baseline epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.