The k8s-workload-registrar needs access to the spire-server socket and therefore has to run in the same pod to be able to mount the socket into the container. Signed-off-by: Marco Franssen <[email protected]> Signed-off-by: Marco Franssen <[email protected]>
29 lines
640 B
YAML
29 lines
640 B
YAML
nameOverride: ""
|
|
fullnameOverride: ""
|
|
|
|
# subcharts
|
|
spire-server:
|
|
nameOverride: server
|
|
bundleConfigMap: &bundleConfigMap spire-bundle
|
|
|
|
clusterName: &clusterName "example-cluster"
|
|
trustDomain: &trustDomain "example.org"
|
|
|
|
socketPath: &serverSocketPath /run/spire/server-sockets/spire-server.sock
|
|
|
|
spire-agent:
|
|
nameOverride: agent
|
|
bundleConfigMap: *bundleConfigMap
|
|
|
|
clusterName: *clusterName
|
|
trustDomain: *trustDomain
|
|
|
|
socketPath: &agentSocketPath /run/spire/agent-sockets/spire-agent.sock
|
|
|
|
spiffe-csi-driver:
|
|
agentSocketPath: *agentSocketPath
|
|
|
|
spiffe-oidc-discovery-provider:
|
|
enabled: false
|
|
trustDomain: *trustDomain
|