Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update KubeHpaMaxedOut.md to fix typo & improve clarity #64

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions content/runbooks/kubernetes/KubeHpaMaxedOut.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,14 @@ weight: 20

## Meaning

Horizontal Pod Autoscaler has been running at max replicas for longer
The Horizontal Pod Autoscaler (HPA) has been running at maximum replicas for longer
than 15 minutes.

## Impact

Horizontal Pod Autoscaler won't be able to add new pods and thus scale application.
**Notice** for some services maximizing HPA is in fact desired.
The Horizontal Pod Autoscaler will not be able to add new pods, thus preventing the
application from scaling.
**Notice** For some services, maximizing HPA utilization is actually desired.

## Diagnosis

Expand All @@ -26,7 +27,7 @@ Check why HPA was unable to scale:

If using basic metrics like CPU/Memory then ensure to set proper values for
`requests`.
For memory based scaling ensure there are no memory leaks.
If using custom metrics then tine tune how app scales accordingly to it.
For memory-based scaling, ensure there are no memory leaks.
If using custom metrics, fine-tune how the app scales according to it.

Use performance tests to see how the app scales.