mirror of
https://github.com/edgelesssys/constellation.git
synced 2024-09-23 09:46:05 +00:00
90b88e1cf9
In the light of extending our eKMS support it will be helpful to have a tighter use of the word "KMS". KMS should refer to the actual component that manages keys. The keyservice, also called KMS in the constellation code, does not manage keys itself. It talks to a KMS backend, which in turn does the actual key management.
25 lines
676 B
YAML
25 lines
676 B
YAML
global:
|
|
# Port on which the KeyService will listen. Global since join-service also uses the value.
|
|
keyservicePort: 9000
|
|
# Path to which secrets/CMs are mounted.
|
|
serviceBasePath: /var/config
|
|
# Name of the ConfigMap that holds measurements and other info.
|
|
joinConfigCMName: join-config
|
|
# Name of the ConfigMap that holds configs that should not be modified by the user.
|
|
internalCMName: internal-config
|
|
|
|
# GCP specific configuration
|
|
gcp:
|
|
deployCSIDriver: false
|
|
|
|
# Azure specific configuration
|
|
azure:
|
|
deployCSIDriver: false
|
|
|
|
# Set one of the tags to true to indicate which CSP you are deploying to.
|
|
tags:
|
|
Azure: false
|
|
GCP: false
|
|
AWS: false
|
|
QEMU: false
|