Property Reference for tanzumysql.yml

Warning: VMware Tanzu™ SQL with MySQL for Kubernetes is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a production environment. If you discover any bugs, contact Support.

Page last updated:

This topic is a property reference table for the tanzumysql.yml. Refer to this table when you are creating the YAML file for a TanzuMySQL instance. For more information, see Create a TanzuMysql Instance in Creating and Deleting a TanzuMySQL Instance.

The table below explains the properties that you can set in the tanzumysql.yml file.

Property Type Default Description Example Required?
metadata.name String N/A The name of your TanzuMySQL instance:

  • Must be unique within a namespace
  • Cannot be updated
  • Required when creating resources, although some resources might allow a client to request the generation of an appropriate name automatically
Name is primarily intended for creation idempotence and configuration definition. For more information about Name, see the Kubernetes documentation.
my‑instance Yes
spec.storageSize N/A StorageSize specifies the size of the persistent volume claims (PVCs) for the Tanzu MySQL for Kubernetes Pods. For information about the units allowed for these PVC sizes, see about resource quantities in kubernetes / community in GitHub. 50Gi Yes
spec.imagePullSecret String N/A Refers to an existing Kubernetes docker-registry secret that can access the registry that contains the TanzuMySQL image. tanzu-mysql-image-registry Yes
spec.storageClassName String Standard Specifies the StorageClass for the PVCs for the Tanzu MySQL for Kubernetes Pods. For the types of StorageClasses available, contact your Kubernetes admin. For more information about the Kubernetes StorageClass concept, see the Kubernetes documentation. standard No
spec.resources.mysql
  • limits.cpu
  • limits.memory
Best effort Describes the maximum CPU and memory allowed for the MySQL container. If left blank, Kubernetes does its best effort to allocate necessary compute resources for the MySQL container. For more information about managing resources for containers, see the Kubernetes documentation. limits.cpu: 3 , limits.memory: 800Mi No
spec.resources.mysql
  • requests.cpu
  • requests.memory
Best effort Describes the minimum CPU and memory allowed for the MySQL container. If left blank, it defaults to limits if limits have been explicitly specified. For more information about limits, see the Kubernetes documentation. requests.cpu: 2 , requests.memory: 500Mi No
spec.resources.backups
  • limits.cpu
  • limits.memory
Best effort Describes the maximum CPU and memory allowed for the backups container. If left blank, Kubernetes does its best effort to allocate the necessary compute resources for the backups container. For more information about CPU and memory resources, see the Kubernetes documentation. limits.cpu: 2 , limits.memory: 500Mi No
spec.resources.backups
  • requests.cpu
  • requests.memory
Best effort Describes the minimum CPU and memory allowed for the backups container. If left blank, it defaults to limits if limits have been explicitly specified. For more information about limits, see the Kubernetes documentation. requests.cpu: 1 , requests.memory: 200Mi No