From 62857c5fcb4af091d199b82e5ebfea53e1ed97d0 Mon Sep 17 00:00:00 2001 From: rock Date: Tue, 27 Oct 2026 23:54:19 -0700 Subject: [PATCH] fix(llm-serving): let the kustomization build again MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The resource list named ornith.yaml and reasoning.yaml, and neither file has ever been committed to this directory. kustomize therefore failed to build, the Application sat in ComparisonError, and nothing in this directory could reconcile — including the clef-flash predictor added a commit earlier. Removing the entries does not remove the models: the Application runs with prune=false, so an object it no longer lists is left untouched. Re-export both from live state the next time either is edited, so the directory describes what actually runs. --- k8s/apps/llm-serving/kustomization.yaml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/k8s/apps/llm-serving/kustomization.yaml b/k8s/apps/llm-serving/kustomization.yaml index d6f4952..4d09759 100644 --- a/k8s/apps/llm-serving/kustomization.yaml +++ b/k8s/apps/llm-serving/kustomization.yaml @@ -11,9 +11,13 @@ kind: Kustomization # in tens of seconds, not a rolling update. resources: - clef-flash.yaml + # ornith and reasoning are live but unmanaged: their manifests were never committed + # to this directory, so listing them made `kustomize build` fail and left the whole + # Application in ComparisonError. Remove the entries rather than the models. The + # Application runs with prune=false, so an object that is no longer in the desired + # state is left alone, not deleted. Re-export both from live state when they are + # next edited. - embeddings.yaml - - ornith.yaml - - reasoning.yaml - reranker.yaml - qwen-cpu.yaml - networkpolicy.yaml