[CP 1603] fix(olm): raise controller-manager memory limit to 1Gi (KUBE-49)#604
Merged
spraveenio merged 2 commits intoJul 15, 2026
Conversation
The OpenShift OLM bundle shipped the kubebuilder scaffold defaults (384Mi limit / 64Mi request) for the controller-manager pod, while the Helm chart was tuned to 1Gi / 256Mi. The two install paths drifted out of sync, and the under-provisioned OLM limit intermittently OOMKills the controller-manager under load (KMM builds, ANR remediation, DRA reconciles). Reported by an IBM customer on AMD GPU Operator 1.5.0 / OpenShift 4.20. Align the OLM bundle with the Helm chart at 1Gi limit / 256Mi request by updating the manifest source of truth and regenerating the CSV. Co-authored-by: Claude <noreply@anthropic.com> (cherry picked from commit 00cce5b676c7a2158cba1844a8cef931321c8750)
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
3 participants
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.
cp of pensando/gpu-operator#1603
Source PR Description (pensando/gpu-operator#1603):
Summary
Aligns the OpenShift OLM bundle controller-manager pod resources with the Helm chart. The OLM bundle shipped the kubebuilder scaffold defaults (384Mi limit / 64Mi request) while the Helm chart was tuned to 1Gi / 256Mi. The under-provisioned OLM limit intermittently OOMKills the controller-manager under load (KMM builds, ANR remediation, DRA reconciles).
resourcestolimits: cpu 1000m / memory 1Gi,requests: cpu 100m / memory 256Miin the manifest source of truth (config/manager-base/manager.yaml) and regenerate the bundle CSV.1Gi(over the customer's minimal 600Mi) converges both install paths on a single already-validated value with headroom.Jira: https://amd.atlassian.net/browse/KUBE-49
Plan: docs-internal/knowledge/plans/2026-07-14-olm-bundle-manager-memory-limit.md
Test plan
operator-sdk bundle validate ./bundlepasseslimits.memory: 1Giand no OOMKills under the customer workload🤖 Generated with Claude Code
Cherrypick triggered by: ACP-Automation