Configuring external databases for components

You can configure external databases for the components in DevOps Loop and provide the database URL in the helm chart to connect the components to external database.

Overview

You can configure external databases using Helm charts for the components in DevOps Loop. Each product may require different settings or secrets, which are defined in Helm chart values and configuration files. This topic summarizes how to configure databases for Deploy, Plan, Build, Velocity, and Test components.

Deploy

To configure an external database for Deploy, refer to the Prerequisites and Parameters sections of the README file in Helm chart. Helm values related to database configuration begin with database.

Plan

To configure an external database for Plan. Refer to Helm chart external database configuration.

Build

Build uses the same MySQL database as Deploy. The Deploy Helm chart must be configured with MySQL. Configure the Build Helm chart using the following values:

  • ibm-devops-build.mysql.database – the database name
  • ibm-devops-build.mysql.user – the database user
  • ibm-devops-build.mysql.password – the database password

Measure and Release

To configure an external database for Measure and Release, create a secret named mongodb-url-secret with a property named password after installing the MongoDB instance. The value should follow this format:

mongodb://<user>:<password>@<host>:<port>/<auth_database>

Example command:

kubectl create secret generic mongodb-url-secret --namespace devops-automation --from-literal=password="${MONGO_URL}"

Set the Helm chart value to reference the secret:

--set ibm-ucv-prod.secrets.database=mongodb-url-secret

For more information, refer to Velocity installation prerequisites.

DevOps Test

Support for configuring external databases in DevOps Test will be provided in an upcoming release.