Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.2.0] Avoid Packaging MySQL JDBC Driver in WSO2 Product Docker Images #321

Closed
chirangaalwis opened this issue Jul 10, 2020 · 2 comments · Fixed by #335
Closed

[3.2.0] Avoid Packaging MySQL JDBC Driver in WSO2 Product Docker Images #321

chirangaalwis opened this issue Jul 10, 2020 · 2 comments · Fixed by #335

Comments

@chirangaalwis
Copy link
Member

Description:
It has been suggested to avoid packaging the MySQL JDBC Driver in the WSO2 product Docker images.

The original purpose of packaging this binary in Docker images was to support evaluatory deployments in container platforms such as, Kubernetes with externalized MySQL RDBMS support.

For a user who intends to use a different version of the particular connector (as opposed to what is packaged inside the image) may not be able to use the current, official WSO2 product Docker images as the base since, he/she may experience version conflicts.

Affected Product Version:
Docker resources for WSO2 API Management version v3.1.0.3 and below

@chirangaalwis
Copy link
Member Author

chirangaalwis commented Jul 10, 2020

As per the initial evaluation, we can continue to install this connector for evaluation purposes in each container platform, via the following methods.

  • Docker Compose
    Please see the official documentation for the suggested method.

  • Kubernetes
    Use Kubernetes InitContainers and shared volume mounts.

@chirangaalwis
Copy link
Member Author

Fixed in #335.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant