New to KubeDB? Please start here.

MariaDBVersion

What is MariaDBVersion

MariaDBVersion is a Kubernetes Custom Resource Definitions (CRD). It provides a declarative configuration to specify the docker images to be used for MariaDB database deployed with KubeDB in a Kubernetes native way.

When you install KubeDB, a MariaDBVersion custom resource will be created automatically for every supported MariaDB versions. You have to specify the name of MariaDBVersion crd in spec.version field of MariaDB crd. Then, KubeDB will use the docker images specified in the MariaDBVersion crd to create your expected database.

Using a separate crd for specifying respective docker images, and pod security policy names allow us to modify the images, and policies independent of KubeDB operator. This will also allow the users to use a custom image for the database.

MariaDBVersion Specification

As with all other Kubernetes objects, a MariaDBVersion needs apiVersion, kind, and metadata fields. It also needs a .spec section.

apiVersion: catalog.kubedb.com/v1alpha1
kind: MariaDBVersion
metadata:
  annotations:
    meta.helm.sh/release-name: kubedb-catalog
    meta.helm.sh/release-namespace: kube-system
  creationTimestamp: "2021-03-09T13:00:51Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: kubedb-catalog
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: kubedb-catalog
    app.kubernetes.io/version: v0.16.2
    helm.sh/chart: kubedb-catalog-v0.16.2
  ...
  name: 10.5.23
spec:
  db:
    image: kubedb/mariadb:10.5.23
  exporter:
    image: kubedb/mysqld-exporter:v0.11.0
  initContainer:
    image: kubedb/busybox
  podSecurityPolicies:
    databasePolicyName: maria-db
  stash:
    addon:
      backupTask:
        name: mariadb-backup-10.5.23
      restoreTask:
        name: mariadb-restore-10.5.23
  version: 10.5.23

metadata.name

metadata.name is a required field that specifies the name of the MariaDBVersion crd. You have to specify this name in spec.version field of MariaDB crd.

We follow this convention for naming MariaDBVersion crd:

• Name format: {Original MariaDB image version}-{modification tag}

We modify original MariaDB docker image to support additional features. An image with higher modification tag will have more features than the images with lower modification tag. Hence, it is recommended to use MariaDBVersion crd with highest modification tag to take advantage of the latest features.

spec.version

spec.version is a required field that specifies the original version of MariaDB database that has been used to build the docker image specified in spec.db.image field.

spec.deprecated

spec.deprecated is an optional field that specifies whether the docker images specified here is supported by the current KubeDB operator.

The default value of this field is false. If spec.deprecated is set true, KubeDB operator will not create the database and other respective resources for this version.

spec.db.image

spec.db.image is a required field that specifies the docker image which will be used to create Petset by KubeDB operator to create expected MariaDB database.

spec.exporter.image

spec.exporter.image is a required field that specifies the image which will be used to export Prometheus metrics.

spec.initContainer.image

spec.initContainer.image is a required field that specifies the image which will be used to remove lost+found directory and mount an EmptyDir data volume.

spec.podSecurityPolicies.databasePolicyName

spec.podSecurityPolicies.databasePolicyName is a required field that specifies the name of the pod security policy required to get the database server pod(s) running.

spec.stash

spec.stash is an optional field that specifies the name of the task for stash backup and restore. Learn more about Stash MariaDB addon