Faisal Memon
9273f11f0a
* Add root-level spire-lib chart Signed-off-by: Faisal Memon <[email protected]> * Make spire consume root-level spire-lib Signed-off-by: Faisal Memon <[email protected]> * Prepare chart dependencies in CI Signed-off-by: Faisal Memon <[email protected]> * Document DCO requirement in CODEX Signed-off-by: Faisal Memon <[email protected]> * Centralize local chart dependency prep Signed-off-by: Faisal Memon <[email protected]> * Exclude spire-lib from chart-testing install Signed-off-by: Faisal Memon <[email protected]> * Rename CODEX guide to AGENTS Signed-off-by: Faisal Memon <[email protected]> * Add make target for chart dependencies Signed-off-by: Faisal Memon <[email protected]> --------- Signed-off-by: Faisal Memon <[email protected]>
Example external postgresql
We recommend you put your config into git, but never put a password directly into git. Generally the easiest way to do so is via environment variable. Your CI/CD system of choice usually allows you to set those. Please refer to your systems documentation for guidance.
If manually deploying for testing, you can safely put the password into an environment variable by running:
source ../bin/readpw.sh
Follow the instructions as described at https://artifacthub.io/packages/helm/spiffe/spire, and copy in the settings from examples/external-postgresql/values.yaml into your values file.
You can add the password at install runtime like so:
helm upgrade --install --namespace spire-mgmt spire spire -f your-values.yaml --set "spire-server.dataStore.sql.password=${DBPW}" --repo https://spiffe.github.io/helm-charts-hardened/