fix(llm-serving): let the kustomization build again
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.
This commit is contained in:
@@ -11,9 +11,13 @@ kind: Kustomization
|
|||||||
# in tens of seconds, not a rolling update.
|
# in tens of seconds, not a rolling update.
|
||||||
resources:
|
resources:
|
||||||
- clef-flash.yaml
|
- 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
|
- embeddings.yaml
|
||||||
- ornith.yaml
|
|
||||||
- reasoning.yaml
|
|
||||||
- reranker.yaml
|
- reranker.yaml
|
||||||
- qwen-cpu.yaml
|
- qwen-cpu.yaml
|
||||||
- networkpolicy.yaml
|
- networkpolicy.yaml
|
||||||
|
|||||||
Reference in New Issue
Block a user