From 6ed00d6d8498c7794599b29d1600f2e0c054eda5 Mon Sep 17 00:00:00 2001
From: Jonny Ervine <jonny@ervine.org>
Date: Thu, 16 Apr 2026 17:53:09 +0800
Subject: [PATCH] Remove ingress, drop memory requests

---
 goldilocks/charts/vpa/values.yaml | 2 +-
 goldilocks/values-home.yaml       | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/goldilocks/charts/vpa/values.yaml b/goldilocks/charts/vpa/values.yaml
index a1293a5..62bd33b 100644
--- a/goldilocks/charts/vpa/values.yaml
+++ b/goldilocks/charts/vpa/values.yaml
@@ -101,7 +101,7 @@ recommender:
       memory: 1000Mi
     requests:
       cpu: 50m
-      memory: 500Mi
+      memory: 70Mi
   nodeSelector: {}
   tolerations: []
   affinity: {}
diff --git a/goldilocks/values-home.yaml b/goldilocks/values-home.yaml
index 548ab12..29f74d4 100644
--- a/goldilocks/values-home.yaml
+++ b/goldilocks/values-home.yaml
@@ -140,7 +140,7 @@ dashboard:
 
   ingress:
     # dashboard.ingress.enabled -- Enables an ingress object for the dashboard.
-    enabled: true
+    enabled: false
 
     # dashboard.ingress.ingressClassName -- From Kubernetes 1.18+ this field is supported in case your ingress controller supports it. When set, you do not need to add the ingress class as annotation.
     ingressClassName: