Best Practices
Use these guides to configure production behavior and verify it under load.
Guides
Section titled “Guides”| Guide | Use it to |
|---|---|
| Kubernetes Autoscaling Best Practices | Set requests, probes, placement and shutdown behavior |
| KEDA Best Practices | Tune activation, fallback, polling and stabilization |
| Scale-to-zero & cold starts | Balance idle capacity against startup latency |
Production checklist
Section titled “Production checklist”- Set an acceptance target: peak throughput, latency, error rate and recovery time.
- Check ownership: one controller per replica/resource field; configure generated HPA/KPA resources through the ScaledObject.
- Test ramp, spike and idle traffic: compare source metrics, desired replicas and ready capacity, including node provisioning and startup.
- Test failure and scale-down: unavailable metrics, controller failover, request draining and queue acknowledgements.
- Retain a rollback: record the original configuration and apply changes through the same Helm/GitOps owner.
Validate Autoscaling Health
Section titled “Validate Autoscaling Health”Autoscaling Checks exercise the signal-to-replica path and expose check latency for alerting. They complement application load tests. Use Monitor scaling to locate delays.
For component operations, see high availability and performance tuning in Operate. See also resource sizing, HTTP proxy tuning and rightsizing validation.