graham/prop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Drop secret.yaml from kustomization to unblock Flux reconciliation

Browse source 
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.
This commit is contained in:
Graham McIntire 2026-04-12 15:05:47 -05:00
parent ca8299a3f1
commit 070e6d8099
No known key found for this signature in database
GPG key ID: F4ABF488E6029E59
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
k8s/kustomization.yaml
View file

@ -1,8 +1,10 @@
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
- secret.yaml
- rbac.yaml
- deployment.yaml
- service.yaml