From 616a759b1bc50f9b1f9505fd3c5ac44bb93dc2ef Mon Sep 17 00:00:00 2001 From: Joe Lanford Date: Thu, 31 Jul 2025 13:43:37 -0400 Subject: [PATCH] webhook tests: remove webhook-operator resource limits The memory limit was causing the pod to be OOMKilled in my local execution of the experimental e2e tests. That limit is irrelevant to the purpose of the test, so it can be safely removed. --- .../manifests/webhook-operator.clusterserviceversion.yaml | 3 --- 1 file changed, 3 deletions(-) diff --git a/testdata/images/bundles/webhook-operator/v0.0.1/manifests/webhook-operator.clusterserviceversion.yaml b/testdata/images/bundles/webhook-operator/v0.0.1/manifests/webhook-operator.clusterserviceversion.yaml index 0b8976f92..26506bd53 100644 --- a/testdata/images/bundles/webhook-operator/v0.0.1/manifests/webhook-operator.clusterserviceversion.yaml +++ b/testdata/images/bundles/webhook-operator/v0.0.1/manifests/webhook-operator.clusterserviceversion.yaml @@ -107,9 +107,6 @@ spec: name: webhook-server protocol: TCP resources: - limits: - cpu: 100m - memory: 30Mi requests: cpu: 100m memory: 20Mi