Sync the self-hosting stack

2026-10-21 10:11:48 +02:00
parent 6db65866d2
commit e210b4db11
7 changed files with 82 additions and 25 deletions
@@ -147,9 +147,16 @@ spec:
 apiVersion: autoscaling/v2
 kind: HorizontalPodAutoscaler
 metadata:
-  # With the Deployment it belongs to.
+  # A WAVE AFTER the Deployment it scales, in the last one, and that is the whole point of the line.
+  #
+  # Argo waits for every resource of a wave to report healthy before it starts the next, and reads
+  # an HPA as Degraded while the HPA reads no metric for its pods. On a FIRST install those pods are
+  # seconds old and metrics-server has not scraped them yet ("the HPA was unable to compute the
+  # replica count … no metrics returned"), so in wave 1 the first sync failed on it every time, and
+  # only an automated policy's retry got past it. The last wave is applied and not waited on: the
+  # sync succeeds, and the HPA turns healthy by itself within a minute. Nothing reads it before.
  annotations:
-    argocd.argoproj.io/sync-wave: "1"
+    argocd.argoproj.io/sync-wave: "2"
  name: jarvis-web
  namespace: jarvis
 spec: