MySQL Chart Values Reference
This reference lists the MySQL values the Axual Governance Helm chart exposes: the deployment name overrides, the image and pull secrets, and the database and credential settings for each of the two database aliases.
Type |
Reference |
Goal |
Look up a MySQL chart value while writing the Axual Governance values file. |
Audience |
Platform Operator deploying the databases that back Platform Manager and Keycloak. |
When to use |
While configuring MySQL, alongside the procedure that installs Axual Governance. |
About MySQL
MySQL is an open-source relational database management system. Platform Manager and Keycloak both store their data in it, so Axual Governance defines two aliases, one per database:
-
platform-manager-mysql -
keycloak-mysql
MySQL Configuration
Axual Governance wraps the Bitnami MySQL Helm chart, so the MySQL public documentation holds the full list of parameters. Set each value below under one of the two aliases. Replace every <VALUE> placeholder with your own value before installing.
MySQL Deployment name
The deployment name decides the names MySQL gives to the resources it creates, such as pods and Secrets. This example combines the release name with nameOverride to build the service names.
platform-manager-mysql:
## @param nameOverride String to partially override common.names.fullname template (will maintain the release name)
##
nameOverride: "platform-manager-mysql"
## @param fullnameOverride String to fully override common.names.fullname template
##
fullnameOverride: ""
This example uses fullnameOverride instead, so the service names come from that value alone.
keycloak-mysql:
## @param nameOverride String to partially override common.names.fullname template (will maintain the release name)
##
nameOverride: ""
## @param fullnameOverride String to fully override common.names.fullname template
##
fullnameOverride: "keycloak-mysql"
MySQL Repository Configuration
You can override registry, tag, and pullPolicy for the MySQL pod. By default these values come from the Axual Governance chart. You can also override imagePullSecrets; if you leave it unset, the MySQL pod uses global.imagePullSecrets.
platform-manager-mysql:
## @param global.imageRegistry Global Docker image registry
## @param global.imagePullSecrets Global Docker registry secret names as an array
##
global:
imageRegistry: ""
imagePullSecrets:
- name: axualdockercred
keycloak-mysql:
## @param global.imageRegistry Global Docker image registry
## @param global.imagePullSecrets Global Docker registry secret names as an array
##
global:
imageRegistry: ""
imagePullSecrets:
- name: axualdockercred
MySQL Database Configuration
You can have MySQL create a database and its user at startup, once per alias.
platform-manager-mysql:
## MySQL Authentication parameters
##
auth:
## @param auth.rootPassword Password for the `root` user. Ignored if existing secret is provided
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-the-root-password-on-first-run
##
rootPassword: "<MYSQL_ROOT_PASSWORD>"
## @param auth.createDatabase Whether to create the .Values.auth.database or not
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run
##
createDatabase: true
## @param auth.database Name for a custom database to create
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run
##
database: "selfservice-db"
## @param auth.username Name for a custom user to create
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-user-on-first-run
##
username: "fluxmaster"
## @param auth.password Password for the new user. Ignored if existing secret is provided
##
password: "<PLATFORM_MANAGER_DB_PASSWORD>"
keycloak-mysql:
## MySQL Authentication parameters
##
auth:
## @param auth.rootPassword Password for the `root` user. Ignored if existing secret is provided
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-the-root-password-on-first-run
##
rootPassword: "<MYSQL_ROOT_PASSWORD>"
## @param auth.createDatabase Whether to create the .Values.auth.database or not
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run
##
createDatabase: true
## @param auth.database Name for a custom database to create
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run
##
database: "keycloak-db"
## @param auth.username Name for a custom user to create
## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-user-on-first-run
##
username: "keycloak"
## @param auth.password Password for the new user. Ignored if existing secret is provided
##
password: "<KEYCLOAK_DB_PASSWORD>"