# Autoscaler Pinned at One Size | ZopNight

> The autoscaler cannot change the replica count at all, so the workload neither absorbs a spike nor gives capacity back.

Source: https://zop.dev/zopnight/rules/autoscaler-pinned-at-one-size

---

_Reliability · Low severity_

## Autoscaler Pinned at One Size

The autoscaler cannot change the replica count at all, so the workload neither absorbs a spike nor gives capacity back.

- 3 — clouds covered
- Low — severity
- Risk — where it shows up
- Manual — fix, change spelled out

Free to start. No card. The playground just needs your work email.

## Found, explained, handed over.

Exposure and fragility, security posture and single points of failure.

- 01. Detect — ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
- 02. Explain — Every finding says exactly what to change: Widen the autoscaler's replica range.
- 03. Fix — The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.

- applies_to_fallback: Any resource in the account
- where_it_appears: The Risk tab of Recommendations, with every affected resource listed.

## Related

- [Autoscaler at Max Capacity](https://zop.dev/zopnight/rules/autoscaler-at-max-capacity)
- [Autoscaler Allows Scale to Zero](https://zop.dev/zopnight/rules/autoscaler-allows-scale-to-zero)
- [Autoscaler Cannot Scale Past One Replica](https://zop.dev/zopnight/rules/autoscaler-cannot-scale-past-one-replica)
- [Autoscaler Has No Metrics](https://zop.dev/zopnight/rules/autoscaler-has-no-metrics)
- [DaemonSet Not Fully Scheduled](https://zop.dev/zopnight/rules/daemonset-not-fully-scheduled)
- [Deployment Not Fully Ready](https://zop.dev/zopnight/rules/deployment-not-fully-ready)

## See the reliability findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

[object Object]