prop/k8s/kustomization.yaml
Graham McIntire 070e6d8099
Drop secret.yaml from kustomization to unblock Flux reconciliation
After the BFG scrub, k8s/secret.yaml is git-ignored (contains plaintext
credentials) but kustomization.yaml still listed it as a resource. Flux
has been failing to kustomize-build the prop-app for six days, so no
deployment since main-1776019122-8d1d7e4 has actually reached prod —
the beacons crash fix, UTC clock fix, ASOS nudging, MRMS, contact
detail async hydration, and email config change were all stuck.

The `prop-secrets` Secret is applied out-of-band with kubectl and lives
independently in the cluster; Flux no longer needs to track it.
2026-04-12 15:05:48 -05:00

10 lines
370 B
YAML

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
# secret.yaml is applied out-of-band and is git-ignored (contains plaintext
# credentials). Flux reconciles deployment.yaml etc. but does NOT manage the
# secret. Rotate secrets by applying secret.yaml with kubectl directly.
resources:
- namespace.yaml
- rbac.yaml
- deployment.yaml
- service.yaml