From b1ce5c41a34e89f138b5ae345970f8407be010e4 Mon Sep 17 00:00:00 2001
From: Antoni Ivanov <aivanov@vmware.com>
Date: Fri, 31 Mar 2023 21:44:16 +0300
Subject: [PATCH] vdk-cicd: apply limit ranges for storage

Changing the helm configuraiton did not seem to fix the issue
(PR 1813) so instead I
will try to apply limit ranges for the whole namespace

Testing Done: apply them manually and verified frontend builds passing

Signed-off-by: Antoni Ivanov <aivanov@vmware.com>
---
 support/gitlab-runners/install-runners.sh |  3 +++
 support/gitlab-runners/limitranges.yaml   | 18 ++++++++++++++++++
 2 files changed, 21 insertions(+)
 create mode 100644 support/gitlab-runners/limitranges.yaml

diff --git a/support/gitlab-runners/install-runners.sh b/support/gitlab-runners/install-runners.sh
index da5ecf5f23..92b3017f07 100755
--- a/support/gitlab-runners/install-runners.sh
+++ b/support/gitlab-runners/install-runners.sh
@@ -49,6 +49,9 @@ if [ -n "$IMAGE_PULL_DOCKER_USERNAME" ]; then
     --docker-server="https://index.docker.io/v1/" --namespace="$NAMESPACE"
 fi
 
+echo "Apply limit ranges"
+kubectl apply -f limitranges.yaml --namespace="$NAMESPACE"
+
 helm repo add gitlab https://charts.gitlab.io
 
 # Before updating version, review changelog at https://docs.gitlab.com/runner/install/kubernetes.html .
diff --git a/support/gitlab-runners/limitranges.yaml b/support/gitlab-runners/limitranges.yaml
new file mode 100644
index 0000000000..baf0ecbb32
--- /dev/null
+++ b/support/gitlab-runners/limitranges.yaml
@@ -0,0 +1,18 @@
+# Copyright 2023-2023 VMware, Inc.
+# SPDX-License-Identifier: Apache-2.0
+
+apiVersion: v1
+kind: LimitRange
+metadata:
+  name: ephemeral-storage-limit
+spec:
+  limits:
+    - type: Container
+      max:
+        ephemeral-storage: "3Gi"
+      min:
+        ephemeral-storage: "100Mi"
+      default:
+        ephemeral-storage: "3Gi"
+      defaultRequest:
+        ephemeral-storage: "1Gi"