...
Adeptia Connect stores such confidential information in encrypted form in Secrets, and offers you the option of using the default Kubernetes Secrets or the one from a third party vendor. The sections below describe how you can use the default Kubernetes Secrets or configure the Secrets provided by a third party vendor, for example, Vault.
| Table of Contents |
|---|
...
- Provide the values for environment variables highlighted in red in the following screenshotsscreenshot.
- Set the value for the properties highlighted in red in the following screenshot.
- For each microservice, provide the values for the two properties highlighted in red in the screenshot below.
The following screenshot depicts the properties for the Webrunner microservice. Similarly, you need to set the same properties for all the microservices.
...
After you've completed the settings in Vault, you need to provide the following information in the values.yaml file.
VAULT_ADDR: vault url
pullSecret:
enabled: false
secret:
enabled: true
vaultMountPoint: valuelabs-dev authntication method
vaultRole: valuelabs-dev-role role defined in auth mthod
# Data path should be like "kv/data/valuelabs-dev/db-secret"
dbDataFrom: db secret path
# Data path should be like "kv/data/valuelabs-dev/image-secret"
imageDataFrom: image secret path
- Provide the values for the properties highlighted in red in the following screenshot.
- Set the enabled property under pullSecret to false as highlighted in the screenshot below.
