Update appVersion to 1.0.1 and document resource estimates.

vantage-sh · Oct 23, 2023 · b811e94 · b811e94
1 parent 37792f5
commit b811e94
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 8 deletions.
diff --git a/charts/vantage-kubernetes-agent/Chart.yaml b/charts/vantage-kubernetes-agent/Chart.yaml
@@ -2,6 +2,6 @@ apiVersion: v2
 name: vantage-kubernetes-agent
 description: Provisions the Vantage Kubernetes agent.
 type: application
-version: 1.0.3
-appVersion: "1.0.0"
+version: 1.0.4
+appVersion: "1.0.1"
 icon: "https://www.vantage.sh/nav-logo.svg"
diff --git a/charts/vantage-kubernetes-agent/templates/statefulset.yaml b/charts/vantage-kubernetes-agent/templates/statefulset.yaml
@@ -55,10 +55,6 @@ spec:
             - name: {{ .Values.service.name }}
               containerPort: {{ .Values.service.port }}
               protocol: TCP
-          livenessProbe:
-            httpGet:
-              path: /healthz
-              port: {{ .Values.service.name }}
           readinessProbe:
             httpGet:
               path: /healthz

diff --git a/charts/vantage-kubernetes-agent/values.yaml b/charts/vantage-kubernetes-agent/values.yaml
@@ -29,12 +29,20 @@ service:
   type: ClusterIP
   port: 9010
 
+# These limits are set low to support small clusters (~10nodes) and should be considered minimum values for deploying an agent.
+# Estimates for later clusters are roughly:
+# ~2CPU/1000node
+# ~1MB/node
+# ~16KB/container
+# ie: 100 node cluster with 3000 containers (10 pods per node, 3 containers per pod) would be approximately 150MB and 200mCPU
+# These are estimates and will vary based on node density, label usage, cluster activity, etc.
+# Agent should reach an approximate steady state after about 1hour of uptime and can be tuned accordingly after the fact.
 resources:
   limits:
-    cpu: 10m
+    cpu: 100m
     memory: 50Mi
   requests:
-    cpu: 10m
+    cpu: 100m
     memory: 50Mi