From 6d02f59a9b7d60c8a94f176336efa223261bc897 Mon Sep 17 00:00:00 2001 From: rock Date: Wed, 4 Nov 2026 06:07:20 +0800 Subject: [PATCH] k8s(llm-serving): stop managing the coder InferenceService coder.yaml requests 2 V100s and never reaches Ready, so it permanently occupies half the GPU pool. candle-vllm serves the coder model on the other two cards; the unmanaged predictor starves clef-serve and blocks its own rollout on every sync. ArgoCD has prune:false, so this removes management only. The live object is deleted manually after the sync, otherwise selfHeal recreates it. --- k8s/apps/llm-serving/kustomization.yaml | 5 ----- 1 file changed, 5 deletions(-) diff --git a/k8s/apps/llm-serving/kustomization.yaml b/k8s/apps/llm-serving/kustomization.yaml index 801ae29..925774a 100644 --- a/k8s/apps/llm-serving/kustomization.yaml +++ b/k8s/apps/llm-serving/kustomization.yaml @@ -14,11 +14,6 @@ resources: # v0.5.22+, published only on CUDA 13, and CUDA 13 dropped Volta kernels. The model # instead runs the implementation it ships (joint_schema_model.py) in fp16 on one V100. - clef-serve.yaml - # coder = Qwen3-Coder-30B-A3B-Instruct, 4-bit GPTQ, TP=2 at 262,144 tokens. It serves - # both `coder` and `reasoning`, so poimen-memory needs a host change only, never a - # model-name change. reasoning.yaml below can be dropped once that host change lands. - - coder.yaml - - reasoning.yaml # Stable client-facing name for the chat model. poimen-memory points at this Service, # so the vLLM -> candle-vllm handoff is a selector edit here and no client change. - reasoning-long-service.yaml -- 2.54.0