add a rdbms folder at https://github.com/wso2/kubernetes-apim/tree/2.1.0/base for the mysql docker image: docker.wso2.com/apim-rdbms-kubernetes:2.1.0 used in pattern-X/artifacts/rdbms/rdbms-deployment.yaml

[yhilem]

Hi,

Can you please add a rdbms folder at https://github.com/wso2/kubernetes-apim/tree/2.1.0/base for the mysql docker image: docker.wso2.com/apim-rdbms-kubernetes:2.1.0 used in pattern-X/artifacts/rdbms/rdbms-deployment.yaml ?

Thanks, Youcef HILEM

[imesh]

Hi Youcef,

Thanks for raising this! In general it would be better to use vanilla Docker images whenever possible unless there is no other way to inject configurations or add extensions/customizations to an existing Docker image. This is to reduce the maintenance overhead.

When using MySQL Docker images we can use environment variables for changing root password, creating a new user, and creating a database [1]. Therefore I do not see any other reason to maintain a separate Dockerfile for MySQL. Do you see any other requirements?

[1] https://hub.docker.com/_/mysql/

Thanks Imesh

[pubudu538]

Hi,

Actually, we have added the mysql for APIM [1]. We have added all the database scripts here.

[1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0/base/mysql

Thank you! Pubudu.

[yhilem]

Thanks. For our production environment, the database is not deployed on OpenShift. The mysql docker image without persistent volume is used to quickly mount and test configurations on OpenShift.

[imesh]

Maintaining a WSO2 specific MySQL Dockerfile might be unnecessary. The centos/mysql-57-centos7 image can be used with a config map for executing SQL scripts at the startup. Please refer below MySQL K8S resources as an example:

https://github.com/imesh/wso2-microservices-poc/blob/master/kubernetes-mysql/resources/mysql-deployment.yaml