Metadata
Details how to customize Kubernetes metadata, such as labels and annotations, for the resources generated and managed by the Operator.
This documentation shows how to configure metadata in the MariaDB Enterprise Kubernetes Operator CRs.
Children object metadata
MariaDB and MaxScale resources allow you to propagate metadata to all the children objects by specifying the inheritMetadata field:
This means that all the reconciled objects will inherit these labels and annotations. For instance, see the Services and Pods:
You have the ability to provide dedicated metadata for Pods by specifying the podMetadata field in any CR that reconciles a Pod, for instance: MariaDB, MaxScale, Backup, Restore and SqlJobs:
It is important to note that the podMetadata field supersedes the inheritMetadata field, therefore the labels and annotations provided in the former will override the ones in the latter.
Service metadata
Provision dedicated metadata for Services in the MariaDB resources can be done via the service, primaryService and secondaryService fields:
In the case of MaxScale, you can also do this via the kubernetesService field.
Refer to the to know more about the Service fields and MaxScale.
Both MariaDB and MaxScale allow you to define a volumeClaimTemplate to be used by the underlying StatefulSet. You may also define metadata for it:
Being able to provide metadata allows you to integrate with other CNCF landscape projects:
If you run on bare metal and you use for managing the LoadBalancer objects, you can declare its IPs via annotations:
injects the data-plane container to all Pods, but you might want to opt-out of this feature in some cases:
For instance, you probably don't want to inject the Istio sidecar to Backup Pods, as it will prevent the Jobs from finishing and therefore your backup process will hang.
This page is: Copyright © 2025 MariaDB. All rights reserved.