zeekay
977c24fbe4
Live do-sfo3-lux-k8s/lux-system carries two `status*` deployments:
- `status` — orphan, 92d old, image ghcr.io/hanzoai/status:latest
(no source-of-truth in this repo, references CMs
status-config/status-frontend/status-brand/status-logo
that also have no source; second pod has been
ContainerCreating for 5+ days). Policy violation —
floating :latest tag.
- `status-lux` — canonical, sha-pinned, declared in k8s/status/.
Add k8s/status/kustomization.yaml so the canonical stack is Kustomize-
applyable (was previously raw YAML).
Add k8s/status/orphan-cleanup.sh — production-impacting cleanup
script with all the kubectl delete commands needed to remove the
orphan deployment + its dangling ConfigMaps + PVC. NOT executed in
this commit; flagged in LLM.md for confirmation before run.
LLM.md additions:
- Decomplection audit section recording the lux-system orphan state
- Decomplection audit section recording the luxd-startup.yaml bash bag
+ the operator-side decomplection plan (see luxfi/operator
decomplect/luxnetwork-declarative-startup@d5b3d26)
13 lines
294 B
YAML
13 lines
294 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
namespace: lux-system
|
|
resources:
|
|
- configmap.yaml
|
|
- deployment.yaml
|
|
- ingressroute.yaml
|
|
labels:
|
|
- pairs:
|
|
app.kubernetes.io/cluster: lux-k8s
|
|
app.kubernetes.io/part-of: hanzo-universe
|
|
includeSelectors: false
|