You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Helm chart does not support mounting TLS certificates for using MySQL SSL encrypted connections.
The docs suggest adding certificates to the chart root, which is not feasible - we should not repackage the helm chart to enable such simple functionality.
Alternatively, the app could use the CA certificates already available on the pod, eg. /etc/ssl/certs/ca-certificates.crt when ?ssl=true or a similar argument is present in the DB connection URL.
At the moment we had to make SSL encryption optional and sacrifice the security.
Reproduction steps
No response
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@stefannica wdyt? We might consider customizing the Helm chart to mount the existing CA certificates directory from the pod into the application container. This would allow the application to use the pre-existing certificates without needing to repackage the Helm chart.
Contact Details [Optional]
No response
System Information
Helm chart version
0.71.0
What happened?
The Helm chart does not support mounting TLS certificates for using MySQL SSL encrypted connections.
The docs suggest adding certificates to the chart root, which is not feasible - we should not repackage the helm chart to enable such simple functionality.
Alternatively, the app could use the CA certificates already available on the pod, eg.
/etc/ssl/certs/ca-certificates.crt
when?ssl=true
or a similar argument is present in the DB connection URL.At the moment we had to make SSL encryption optional and sacrifice the security.
Reproduction steps
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: