From 5595b13ce0a4e6aa592a01b8d274a3d208ffe8d9 Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Thu, 4 Jan 2024 07:22:04 -0800 Subject: [PATCH] Use milliCPU as units for clarity --- helm-charts/support/values.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/helm-charts/support/values.yaml b/helm-charts/support/values.yaml index f463dbb6c8..39996dc6ad 100644 --- a/helm-charts/support/values.yaml +++ b/helm-charts/support/values.yaml @@ -428,13 +428,14 @@ cryptnono: # Measured with the following prometheus queries: # Memory: sum(container_memory_usage_bytes{container="monero", namespace="support"}) by (instance) # CPU: sum(rate(container_cpu_usage_seconds_total{container="trace", namespace="support"}[5m])) by (instance) - # Seems to hover mostly around the 60Mi mark for memory, and generally less than 0.0002 in CPU + # Seems to hover mostly around the 60Mi mark for memory, and generally less than 0.0002 in CPU. But + # 1m (or 0.001) is the lowest that can be specified in kubernetes, so we use that. limits: memory: 128Mi - cpu: 0.005 + cpu: 5m requests: memory: 64Mi - cpu: 0.0001 + cpu: 1m # Configuration of templates provided directly by this chart # -------------------------------------------------------------------------------