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 stateless server
To install Spire Server as a deployment(stateless), you need to use an external database. This runs spire-server as stateless microservice enabling HA.
WARNING
The following configurations are not supported for running spire-server as deployment.
- spire-server.persistence.type
- spire-server.dataStore.sql.databaseType: "sqlite3"
- spire-server.keyManager.disk
- spire-server.tornjak
If manually deploying for testing, you can create an incluster or use an external database and put the database password into an environment variable.
Next, edit your-values.yaml with your settings as described in the production install instructions. Check it into your git repo if using one.
Then, deploy the chart pointing at your mysql instance like so:
helm upgrade --install --namespace spire-mgmt spire spire --repo https://spiffe.github.io/helm-charts-hardened/ -f examples/stateless-server/values.yaml --set "spire-server.dataStore.sql.password=${DBPW}" -f your-values.yaml
See the production install instructions for production recommendations. See values.yaml for more details on the chart configurations to achieve this setup.