Instructions for customers to authenticate and gain access to the private MariaDB Enterprise Docker registry to pull protected container images.
This documentation aims to provide guidance on how to configure access to docker.mariadb.com in your MariaDB Enterprise Kubernetes Operator resources.
Customer credentials
MariaDB Corporation requires customers to authenticate when logging in to the . A Customer Download Token must be provided as the password. Customer Download Tokens are available through the MariaDB Customer Portal. To retrieve the customer download token for your account:
Copy the Customer Download Token to use as the password when logging in to the MariaDB Enterprise Docker Registry.
Then, configure a Kubernetes to authenticate:
If you are running in Openshift, it is recommended to use the to configure . The global pull secret is automatically used by all Pods in the cluster, without having to specify imagePullSecrets explicitly.
To configure the global pull secret, you can use the following commands:
Extract your :
Login in the MariaDB registry providing the customer download token as password:
Update the global pull secret:
Alternatively, you can also create a dedicated Secret for authenticating:
In order to configure access to docker.mariadb.com in your MariaDB resources, you can use the imagePullSecrets field to specify your :
As a result, the Pods created as part of the reconciliation process will have the imagePullSecrets.
Similarly to MariaDB, you are able to configure access to docker.mariadb.com in your MaxScale resources:
The batch Job resources will inherit the imagePullSecrets from the referred MariaDB, as they also make use of its image. However, you are also able to provide dedicated imagePullSecrets for these resources:
When the resources from the previous examples are created, a Job with both mariadb-enterprise and backup-registryimagePullSecrets will be reconciled.