Resolve issue in prod example on volume mount (#143)

2023-03-21 04:39:59 -07:00
parent 5b6708bb57
commit 64d010757c
2 changed files with 11 additions and 1 deletions
@@ -1,8 +1,14 @@
-Install with something similar to:
+# Recommended production setup

+Too install Spire with the least privileges possible we deploy spire accross 2 namespaces.
+
+```shell
 kubectl create namespace "spire-system"
 kubectl label namespace "spire-system" pod-security.kubernetes.io/enforce=privileged
 kubectl create namespace "spire-server"
 kubectl label namespace "spire-server" pod-security.kubernetes.io/enforce=restricted

 helm upgrade --install --namespace spire-server spire charts/spire -f values.yaml
+```
+
+See [values.yaml](./values.yaml) for more details on the chart configurations to achieve this setup.