From 92fff129fdae4cf21ab367650f2b4c84634e7b2e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Thu, 14 Sep 2023 22:01:11 +0200 Subject: [PATCH] ci: k8s: Don't set cpu limit request for k8s-inotofy test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Without setting the cpu limit / request to 1, we can make this test run in a smaller VM instance without any issue. Signed-off-by: Fabiano Fidêncio --- .../runtimeclass_workloads/inotify-configmap-pod.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/tests/integration/kubernetes/runtimeclass_workloads/inotify-configmap-pod.yaml b/tests/integration/kubernetes/runtimeclass_workloads/inotify-configmap-pod.yaml index c85240c94e..2e23864bf0 100644 --- a/tests/integration/kubernetes/runtimeclass_workloads/inotify-configmap-pod.yaml +++ b/tests/integration/kubernetes/runtimeclass_workloads/inotify-configmap-pod.yaml @@ -16,10 +16,8 @@ spec: args: ["-c", "inotifywait --timeout 120 -r /config/ && [[ -L /config/config.toml ]] && echo success" ] resources: requests: - cpu: 1 memory: 50Mi limits: - cpu: 1 memory: 1024Mi volumeMounts: - name: config