From 4a49a84fb0a46e8c639af3317c976ea038e256c4 Mon Sep 17 00:00:00 2001 From: rock Date: Thu, 5 Nov 2026 10:28:22 +0800 Subject: [PATCH] fix(llm-serving): retire the reference clef-serve, free the GPU clef-serve (pytorch reference) and clef-candle both claim replicas 1, but only one GPU is free: coder takes 2 of the 4 V100s. They starved each other, so clef-candle sat Pending and the clef-serve Service had no endpoints. The Service now selects app: clef-candle, so the reference receives no traffic even when it runs. Keeping it at 1 only burns a GPU. --- k8s/apps/llm-serving/clef-serve.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/k8s/apps/llm-serving/clef-serve.yaml b/k8s/apps/llm-serving/clef-serve.yaml index a8b820f..bd37506 100644 --- a/k8s/apps/llm-serving/clef-serve.yaml +++ b/k8s/apps/llm-serving/clef-serve.yaml @@ -43,7 +43,7 @@ spec: # Cold start is about four minutes: the pod pip-installs on every boot because the # torch base image cannot be pushed to the registry (Cloudflare answers 413 above # 100 MB per layer). startupProbe allows for that. - replicas: 1 + replicas: 0 # Recreate, not RollingUpdate. Every GPU card is allocated, so a rolling update leaves # the new pod Pending forever waiting for a card the old pod still holds. strategy: