rock
62857c5fcb
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.
26 lines
1.3 KiB
YAML
26 lines
1.3 KiB
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
# Explicit allowlist, matching k8s/apps/api. Anything added to this directory
|
|
# and not listed here is silently dropped — no error, no drift shown.
|
|
#
|
|
# These five were adopted from live state on 2026-08-15; they had been applied
|
|
# by hand and carried no ArgoCD ownership. Each was exported and verified with
|
|
# `kubectl diff -f <file>` returning empty before the Application below was
|
|
# created, so the first sync was a no-op rather than a redeploy. Re-verify that
|
|
# way after any edit here: a GPU predictor restart is a weights reload measured
|
|
# 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
|
|
- reranker.yaml
|
|
- qwen-cpu.yaml
|
|
- networkpolicy.yaml
|
|
# No namespace transformer: every file sets its own, and the transformer would
|
|
# rewrite metadata.namespace on anything cross-namespace added later.
|