Issue
-
We need to make some modifications to the database, and therefore we have opened port 3306 of the database to be able to access it from outside, just as we have done many other times.
-
However, this time we were unable to connect to the database with the correct credentials (copied from the console Secrets).
-
We believe that it could be a network issue at the public endpoint.
Environment
- PaaS
Resolution
- It so happens that a change has been introduced, for security and performance reasons (to prepare a database engine migration to
PostgreSQL), in the'database'service image from version '5.4.0'onwards that prevents access to open ports from the outside. - The available alternatives for making changes to the database are as follows:
-
- Implementing Upgrade Steps. You have the following documentation available on how to implement it: Upgrading your database tables.
- Using the database client in write mode: You have the following documentation available on how to use it: Using the database client
- Using Groovy scripting (or even your own development that allows you to send DDL statements to the database).
Additional Information
- 03/26/2024 - Service Release Updates
- This feature request has been created: LPD-40136 Need read permissions of the cloud database or public access to it