diff --git a/bundle/manifests/amd-gpu-operator.clusterserviceversion.yaml b/bundle/manifests/amd-gpu-operator.clusterserviceversion.yaml
index 15b56dbce..3267e3158 100644
--- a/bundle/manifests/amd-gpu-operator.clusterserviceversion.yaml
+++ b/bundle/manifests/amd-gpu-operator.clusterserviceversion.yaml
@@ -1660,11 +1660,11 @@ spec:
                   periodSeconds: 10
                 resources:
                   limits:
-                    cpu: 500m
-                    memory: 384Mi
+                    cpu: "1"
+                    memory: 1Gi
                   requests:
-                    cpu: 10m
-                    memory: 64Mi
+                    cpu: 100m
+                    memory: 256Mi
                 securityContext:
                   allowPrivilegeEscalation: false
                 volumeMounts:
diff --git a/config/manager-base/manager.yaml b/config/manager-base/manager.yaml
index 4095a85c6..93a1dfea4 100644
--- a/config/manager-base/manager.yaml
+++ b/config/manager-base/manager.yaml
@@ -64,15 +64,17 @@ spec:
             port: 8081
           initialDelaySeconds: 5
           periodSeconds: 10
-        # TODO(user): Configure the resources accordingly based on the project requirements.
-        # More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
+        # Keep in sync with the Helm chart controller-manager resources
+        # (helm-charts-k8s/values.yaml). The previous 384Mi limit was the
+        # kubebuilder scaffold default and caused intermittent OOMKilled
+        # events on OpenShift under load.
         resources:
           limits:
-            cpu: 500m
-            memory: 384Mi
+            cpu: 1000m
+            memory: 1Gi
           requests:
-            cpu: 10m
-            memory: 64Mi
+            cpu: 100m
+            memory: 256Mi
       serviceAccountName: controller-manager
       terminationGracePeriodSeconds: 10
       tolerations: