fix: [alert] KubeDeploymentRolloutStuck (ai) (#750 )

2026-09-02 10:44:39 +00:00
2 changed files with 12 additions and 0 deletions
@@ -25,6 +25,13 @@ metadata:
    app.kubernetes.io/name: llama-server
 spec:
  replicas: 1
+  # The startupProbe below sanctions a 40 min cold download, but the default
+  # progressDeadlineSeconds is 600. Left implicit the Deployment declares
+  # ProgressDeadlineExceeded at 10 minutes while the probe is still legitimately
+  # waiting, and KubeDeploymentRolloutStuck fires 15 min after that on a rollout
+  # that is fine. Kept above the startup budget, with room for the image pull
+  # and scheduling that happen before the first probe.
+  progressDeadlineSeconds: 3000
  # A rolling update would load a second copy of the weights onto the same
  # iGPU and into the same node's RAM before releasing the first.
  strategy:
@@ -19,6 +19,11 @@ metadata:
    app.kubernetes.io/name: llama-embed
 spec:
  replicas: 1
+  # Same reasoning as llama-server: the startupProbe budget (600s) must stay
+  # below progressDeadlineSeconds, whose default is also 600 — exactly equal, so
+  # any cold download that uses most of its budget trips
+  # KubeDeploymentRolloutStuck on a rollout that is still progressing normally.
+  progressDeadlineSeconds: 900
  strategy:
    type: Recreate
  selector: