Skip to content

fix(longhorn): stop instance-manager OOM by exempting longhorn-system from generated LimitRange #2180

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.

Sign up for GitHub

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

Open
devantler wants to merge 1 commit into
base: main
Choose a base branch
from
+19 −0
Open

fix(longhorn): stop instance-manager OOM by exempting longhorn-system from generated LimitRange #2180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 19 additions & 0 deletions k8s/bases/infrastructure/cluster-policies/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,20 @@ patches:
# platform-owned namespaces; its sizing is VPA-owned, not
# quota-bounded. The LimitRange (rule 1) still applies.
- observability
# Longhorn storage data plane. longhorn-manager creates the
# instance-manager pods WITHOUT a memory limit by design: during
# a volume rebuild they burst well past the generic LimitRange
# default (memory 512Mi), get OOMKilled, and longhorn-manager
# then deletes+recreates the IM pod -- which faults EVERY replica
# engine on that node (DetachedUnexpectedly), cascading into
# CNPG primary failover and Postgres timeline divergence
# cluster-wide (observed 2026-06-20). It is excluded from BOTH
# rules: rule 1 drops the OOM-inducing limit, and this rule
# (ResourceQuota) must drop too -- otherwise pods that no longer
# receive the LimitRange-supplied requests get rejected by the
# requests.memory quota. Longhorn sizing is operator-/VPA-owned
# (manager, csi, ui carry VPAs), not quota-bounded.
- longhorn-system
- op: add
path: /spec/rules/0/generate/generateExisting
value: true
Expand Down Expand Up @@ -79,6 +93,11 @@ patches:
- kube-public
- kube-node-lease
- flux-system
# See rule 0: Longhorn instance-managers must run without the
# default memory limit -- an OOM during a rebuild recreates the
# IM pod and faults every volume on the node, taking the storage
# data plane (and every CNPG database on it) down.
- longhorn-system
- op: add
path: /spec/rules/1/generate/generateExisting
value: true
Expand Down
Loading