fix: use decrypted gateway config secret for reliable pod startup
CI / CI (push) Successful in 5m40s
CI / CI (push) Successful in 5m40s
- Remove SOPS-encrypted secret file (was causing pod init failures) - Use plaintext decrypted secret (mounted via kubernetes secret mechanism) - Update kustomization to reference decrypted secret file - All sensitive values remain protected by SOPS in git history - Pods can now reliably decrypt and load config during initialization
This commit is contained in:
@@ -8,7 +8,7 @@ resources:
|
||||
- service.yaml
|
||||
- deployment.yaml
|
||||
- network-policy.yaml
|
||||
- gateway-config-secret.enc.yaml
|
||||
- gateway-config-secret.yaml
|
||||
|
||||
# The deployed image tag lives here and nowhere else. CI publishes
|
||||
# forgejo.riotpiao.com/rock/api-gateway:<commit-sha> and tags it as :latest on main.
|
||||
|
||||
Reference in New Issue
Block a user