...
When you're going to use the default Secrets, you need to pass the confidential information on to the Kubernetes for the creation of Secrets through some properties and environment variables in values.yaml file at the time of deployment. Given below is the list of properties or environment variables that you may need to set.
In env variables enter the followings:
BACKEND_DB_USERNAME:
BACKEND_DB_PASSWORD:
LOG_DB_PASSWORD:
LOG_DB_USERNAME:
LOG_ARCHIVE_DB_PASSWORD:
LOG_ARCHIVE_DB_USERNAME:
In pullSecret.
enabled: true
registry: repository provided by Adeptia
username: provided by Adeptia
password: provided by Adeptia
For each microservice, provide.
image.repository: to reach to the image, provided by adeptia
image.tag: provided by adeptia
Rest of the settings will remain sameIn the values.yaml file, you need to complete the following settings.
- Provide the values for environment variables highlighted in red in the following screenshots.
- 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.
Info |
---|
Rest of the settings in values.yaml file will remain as they are. |
Using third party tool for secrets
...