Chart version: 0.32.0
Api version: v1
App version: 5.7.14
MySQL w/ Kanister support based on stable/mysql
Chart Type
Set me up:
helm repo add center https://repo.chartcenter.io
Install Chart:
helm install kanister-mysql center/kanister/kanister-mysql
Versions (0)


MySQL is one of the most popular database servers in the world. Notable users include Wikipedia, Facebook and Google.


This chart bootstraps a single node MySQL deployment on a Kubernetes cluster using the Helm package manager.


  • Kubernetes 1.6+ with Beta APIs enabled
  • PV provisioner support in the underlying infrastructure
  • Kanister version 0.7.0 with profiles.cr.kanister.io CRD installed

Installing the Chart

Installing Kanister Enabled MySQL For basic installation, you can install using the provided Helm chart that will install an instance of MySQL (a deployment with a persistent volume) as well as a Kanister blueprint to be used with it.

Prior to install you will need to have the Kanister Helm repository added to your local setup.

$ helm repo add kanister http://charts.kanister.io

Then install the sample MySQL application in its own namespace.

$ helm install kanister/kanister-mysql -n my-release --namespace mysql-test \
    --set profile.create='true' \
    --set profile.profileName='mysql-test-profile' \
    --set profile.location.type='s3Compliant' \
    --set profile.location.bucket='kanister-bucket' \
    --set profile.location.endpoint='https://my-custom-s3-provider:9000' \
    --set profile.aws.accessKey='AKIAIOSFODNN7EXAMPLE' \
    --set profile.aws.secretKey='wJalrXUtnFEMI%K7MDENG%bPxRfiCYEXAMPLEKEY' \
    --set mysqlRootPassword='asd#45@mysqlEXAMPLE' \
    --set persistence.size=10Gi

The settings in the command above represent the minimum recommended set for your installation. The command deploys MySQL on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

The command will also configure a location where artifacts resulting from Kanister data operations such as backup should go. This is stored as a profiles.cr.kanister.io CustomResource (CR) which is then referenced in Kanister ActionSets. Every ActionSet requires a Profile reference whether one created as part of the application install or not. Support for creating an ActionSet as part of install is simply for convenience. This CR can be shared between Kanister-enabled application instances so one option is to only create as part of the first instance.

If not creating a Profile CR, it is possible to use an even simpler command.

$ helm install kanister/kanister-mysql -n my-release --namespace mysql-test \
     --set mysqlRootPassword='asd#45@mysqlEXAMPLE' \
     --set persistence.size=10Gi

By default a random password will be generated for the root user. If you’d like to set your own password change the mysqlRootPassword in the values.yaml.

You can retrieve your root password by running the following command. Make sure to replace [YOUR_RELEASE_NAME]:

printf $(printf '\%o' `kubectl get secret [YOUR_RELEASE_NAME]-mysql -o jsonpath="{.data.mysql-root-password[*]}"`)

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release. To completely remove the release include the --purge flag.


The following table lists the configurable MySQL Kanister blueprint and Profile CR parameters and their default values. The Profile CR parameters are passed to the profile sub-chart.

Parameter Description Default
profile.create (Optional) Specify if a Profile CR should be created as part of install. false
profile.defaultProfile (Optional if not creating a default Profile) Set to true to create a profile with name default-profile false
profile.profileName (Required if not creating a default Profile) Name for the profile that is created nil
profile.aws.accessKey (Required if creating profile) API Key for an s3 compatible object store. nil
profile.aws.secretKey (Required if creating profile) Corresponding secret for accessKey. nil
profile.location.bucket (Required if creating profile) A bucket that will be used to store Kanister artifacts.

The bucket must already exist and the account with the above API key and secret needs to have sufficient permissions to list, get, put, delete.
profile.location.region (Optional if creating profile) Region to be used for the bucket. nil
profile.location.endpoint (Optional if creating profile) The URL for an s3 compatible object store provider. Can be omitted if provider is AWS. Required for any other provider. nil
profile.verifySSL (Optional if creating profile) Set to false to disable SSL verification on the s3 endpoint. true
kanister.controller_namespace (Optional) Specify the namespace where the Kanister controller is running. kanister

The following table lists the configurable parameters of the MySQL chart and their default values.

Parameter Description Default
imageTag mysql image tag. Most recent release
imagePullPolicy Image pull policy IfNotPresent
mysqlRootPassword Password for the root user. nil
mysqlUser Username of new user to create. nil
mysqlPassword Password for the new user. nil
mysqlDatabase Name for new database to create. nil
livenessProbe.initialDelaySeconds Delay before liveness probe is initiated 30
livenessProbe.periodSeconds How often to perform the probe 10
livenessProbe.timeoutSeconds When the probe times out 5
livenessProbe.successThreshold Minimum consecutive successes for the probe to be considered successful after having failed. 1
livenessProbe.failureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded. 3
readinessProbe.initialDelaySeconds Delay before readiness probe is initiated 5
readinessProbe.periodSeconds How often to perform the probe 10
readinessProbe.timeoutSeconds When the probe times out 1
readinessProbe.successThreshold Minimum consecutive successes for the probe to be considered successful after having failed. 1
readinessProbe.failureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded. 3
persistence.enabled Create a volume to store data true
persistence.size Size of persistent volume claim 8Gi RW
persistence.storageClass Type of persistent volume claim nil (uses alpha storage class annotation)
persistence.accessMode ReadWriteOnce or ReadOnly ReadWriteOnce
persistence.existingClaim Name of existing persistent volume nil
persistence.subPath Subdirectory of the volume to mount nil
resources CPU/Memory resource requests/limits Memory: 256Mi
CPU: 100m
configurationFiles List of mysql configuration files nil

Using Configuration Parameters

Some of the parameters above map to the env variables defined in the MySQL DockerHub image.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set mysqlRootPassword=secretpassword,mysqlUser=my-user,mysqlPassword=my-password,mysqlDatabase=my-database \

The above command sets the MySQL root account password to secretpassword. Additionally it creates a standard database user named my-user, with the password my-password, who has access to a database named my-database.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml kanister/kanister-mysql

Tip: You can use the default values.yaml


The MySQL image stores the MySQL data and configurations at the /var/lib/mysql path of the container.

By default a PersistentVolumeClaim is created and mounted into that directory. In order to disable this functionality you can change the values.yaml to disable persistence and use an emptyDir instead.

“An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever.”

Custom MySQL configuration files

The MySQL image accepts custom configuration files at the path /etc/mysql/conf.d. If you want to use a customized MySQL configuration, you can create your alternative configuration files by passing the file contents on the configurationFiles attribute. Note that according to the MySQL documentation only files ending with .cnf are loaded.

  mysql.cnf: |-
  mysql_custom.cnf: |-