What
backend-secret.yaml is committed to git with stringData containing CHANGE_ME placeholders for DATABASE_URL, JWT_SECRET, STELLAR_SECRET_KEY. Anyone who deploys without overriding runs with known credentials.
Why
Known credentials in a payroll system is a critical security issue. The secret should use an external secret manager.
Scope
In scope: Use Sealed Secrets or External Secrets Operator, remove plaintext from git, document safe-apply workflow
Out of scope: Vault setup
Acceptance Criteria
Technical Context
k8s/base/backend-secret.yaml — plaintext placeholders
infrastructure/terraform/modules/secrets/ — AWS Secrets Manager
What
backend-secret.yamlis committed to git withstringDatacontaining CHANGE_ME placeholders for DATABASE_URL, JWT_SECRET, STELLAR_SECRET_KEY. Anyone who deploys without overriding runs with known credentials.Why
Known credentials in a payroll system is a critical security issue. The secret should use an external secret manager.
Scope
In scope: Use Sealed Secrets or External Secrets Operator, remove plaintext from git, document safe-apply workflow
Out of scope: Vault setup
Acceptance Criteria
Technical Context
k8s/base/backend-secret.yaml— plaintext placeholdersinfrastructure/terraform/modules/secrets/— AWS Secrets Manager