More memory for gdscan

GDATASoftwareAG · Jan 16, 2024 · 3859dc4 · 3859dc4
1 parent bd2f85d
commit 3859dc4
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -51,7 +51,7 @@ helm upgrade vaas gdatasoftware/vaas -f values.yaml
 * Start Minikube:
 
 ```
-minikube start --cpus="6" --memory="6g" --addons ingress
+minikube start --cpus="6" --memory="10g" --addons ingress
 ```
 
 * Check your Minikube IP: ```minikube ip```

diff --git a/charts/vaas/Chart.yaml b/charts/vaas/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v2
 name: vaas
-version: 1.0.0
+version: 1.0.1
 description: Deployment of a Verdict-as-a-Service on-premise instance
 maintainers:
   - name: G DATA CyberDefense AG

diff --git a/charts/vaas/values.yaml b/charts/vaas/values.yaml
@@ -146,17 +146,28 @@ gdscan:
     image:
       repository: ghcr.io/gdatasoftwareag/vaas/scanserver
       pullPolicy: Always
-      tag: 1.9.4
+      tag: 1.9.5
     containerSecurityContext:
       enabled: false
+    resources:
+      limits:
+        memory: 2.5Gi
+      requests:
+        cpu: '1'
   client:
     name: client
     image:
       repository: ghcr.io/gdatasoftwareag/vaas/scanner
       pullPolicy: Always
-      tag: 1.9.4
+      tag: 1.9.5
     containerSecurityContext:
       enabled: false
+    resources:
+      limits:
+        memory: 4Gi
+      requests:
+        cpu: '1'
+
   terminationGracePeriodSeconds: 30
 
   nameOverride: ""