Autoscaler Max Limits and Governance
Runaway HPA scaled to 500 pods—invoice shock and DB meltdown.
What broke first on dashboards
Runaway HPA scaled to 500 pods—invoice shock and DB meltdown.
On-call sees green infrastructure metrics while business KPIs diverge — classic sign the gate is not on the critical path.
Root cause — not the obvious answer
Root cause tied to no max replicas—misconfig scales cost unbounded.
autoscaler governance was treated as a one-time setup task instead of an operational contract with owners and SLOs.
Fix path we kept
Move autoscaler governance into the promote path with explicit failure semantics. Add partition-level coverage, not sample-only checks.
Add CI enforcement so misconfigurations cannot merge.
Reference configuration
# Operational hook for autoscaler governance
@task(retries=3, retry_delay=timedelta(minutes=5))
def run_autoscaler_limits_governance():
validate_preconditions()
execute()
emit_lineage(run_id=ctx.run_id)
Day-two ownership
Assign a named owner team, review thresholds quarterly, and rehearse rollback.
New hires should execute a safe canary using only the runbook within their first week.
What to do this week
If you only do one thing this week: put autoscaler governance on the critical path for one tier-1 workflow and measure what it catches.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Handoff to adjacent teams
Capacity Planning pipelines touch ingestion, serving, and finance. Document interfaces where autoscaler governance gates hand off to downstream owners so failures are not bounced without context.
Operating autoscaler governance at scale
After the first successful deploy of autoscaler max limits and governance, most incidents trace to assumptions that stopped being true: traffic doubled, schemas drifted, or credentials rotated without updating consumers. Schedule a quarterly review of autoscaler governance settings with the on-call rotation — not only the primary author.
Further reading
Frequently asked questions
When should teams prioritize Autoscaler Max Limits and Governance?
Before enabling autoscale on new services.
What is the most common mistake with autoscaler governance?
No max replicas—misconfig scales cost unbounded.
How do we know Autoscaler Max Limits and Governance is working?
Define a leading metric tied to autoscaler governance health and a lagging metric tied to incidents or audit findings. If only lagging metrics exist, you discover problems after customers do.
Hiring a senior Android / Flutter engineer?
I architect and ship production mobile software — Kotlin, Jetpack Compose, Flutter — for robotics, EV infrastructure, fintech, and real-time systems. Open to remote roles in Europe and the US.
Get in touch →