fix(netbox): raise memory limit to 2Gi to stop OOMKills#995
Open
fenio wants to merge 1 commit into
Open
Conversation
netbox was OOMKilled (exit 137) at its 1Gi limit and sits at ~976Mi at rest, so it kept hitting the ceiling. Bump request 512Mi->1Gi and limit 1Gi->2Gi for headroom (Django/gunicorn baseline footprint is ~1Gi).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
netbox was OOMKilled today (exit 137, 12:24) at its 1Gi memory limit and immediately climbed back to 976Mi / 1Gi — so it would keep OOMing. Found during a cluster-wide log/health sweep.
Fix
Bump the netbox container resources (
cluster/apps/net/netbox/app/helmrelease.yaml):512Mi -> 1Gi1Gi -> 2GiDjango/gunicorn baseline footprint here is ~1Gi, so this gives real headroom instead of running flush against the ceiling.