From cf7dde5f317ddc4c1b2e19e90c124633c32f06ab Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:00:09 +0200 Subject: [PATCH 1/4] fix(rdb): dns entries and ram upgrade --- .../how-to/connect-database-instance.mdx | 5 +++++ .../how-to/manage-nodes.mdx | 1 + 2 files changed, 6 insertions(+) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx index 70bc344c34..65ef19cddb 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx @@ -81,6 +81,11 @@ You can create new Database Instances to attach to your Private Network, or atta Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu. + + There are also internal DNS entries that point to the allocated IP address, which can be used to connect to the database. You can use the following formats: + - `..internal` + - `..internal` + - `..internal` 7. Click **Attach to Private Network** to conclude. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx index 10a159a050..3eea6916c7 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx @@ -67,6 +67,7 @@ If you are in standalone mode, you can change the node configuration to High Ava Keep in mind that: - Changing the node type performs a rolling upgrade of your Database Instance. + - Switching to a node type with less RAM than the current one incurs in an automatic reset of your configured parameters to ensure they fit the new available resources. - During this process, the Database Instance will be unavailable for several seconds. - The Instance stays in `Initializing` mode throughout the process and all console actions are unavailable. - If you use local storage the process can take longer than expected, but the unavailability period of the Instance will be short. This means that the Database Instance remains mostly available during the entire process, except for a few seconds. From 799f796c7c726083bdc683753e5a6df0ff333047 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:11:07 +0200 Subject: [PATCH 2/4] fix(rdb): review axel --- .../how-to/manage-nodes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx index 3eea6916c7..1bc8379f45 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx @@ -31,6 +31,7 @@ You can change your Database Instance node type and enable High Availability aft Keep in mind that: - Changing the node type performs a rolling upgrade of your Database Instance. + - Switching to a node type with less RAM than the current one incurs in an automatic reset of your configured parameters to ensure they fit the new available resources. - During this process, the Database Instance will be unavailable for several seconds. - The Instance stays in `Initializing` mode throughout the process. - If you use local storage: @@ -67,7 +68,6 @@ If you are in standalone mode, you can change the node configuration to High Ava Keep in mind that: - Changing the node type performs a rolling upgrade of your Database Instance. - - Switching to a node type with less RAM than the current one incurs in an automatic reset of your configured parameters to ensure they fit the new available resources. - During this process, the Database Instance will be unavailable for several seconds. - The Instance stays in `Initializing` mode throughout the process and all console actions are unavailable. - If you use local storage the process can take longer than expected, but the unavailability period of the Instance will be short. This means that the Database Instance remains mostly available during the entire process, except for a few seconds. From 5c5e6e092d84bee6c065431b60367744e623eb56 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:12:51 +0200 Subject: [PATCH 3/4] fix(rdb): review axel2 --- .../how-to/manage-nodes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx index 1bc8379f45..ec0f5024be 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-nodes.mdx @@ -31,7 +31,7 @@ You can change your Database Instance node type and enable High Availability aft Keep in mind that: - Changing the node type performs a rolling upgrade of your Database Instance. - - Switching to a node type with less RAM than the current one incurs in an automatic reset of your configured parameters to ensure they fit the new available resources. + - Switching to a node type with less RAM than the current one incurs an automatic reset of your configured parameters to ensure they fit the new available resources. - During this process, the Database Instance will be unavailable for several seconds. - The Instance stays in `Initializing` mode throughout the process. - If you use local storage: From d280b1d868fb1aaee32477cb7ec8c2956a6e6506 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:18:08 +0200 Subject: [PATCH 4/4] fix(rdb): review bastien --- .../how-to/connect-database-instance.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx index 65ef19cddb..c7311aefe0 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx @@ -80,12 +80,8 @@ You can create new Database Instances to attach to your Private Network, or atta - Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu. - - There are also internal DNS entries that point to the allocated IP address, which can be used to connect to the database. You can use the following formats: - - `..internal` - - `..internal` - - `..internal` + - Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform/OpenTofu. + - You can also use internal DNS entries that point to the allocated IP address, which can be used to connect to the database. Refer to the [DNS resolution details](/vpc/reference-content/dns/#dns-resolution-details) section of the **Understanding Scaleway DNS for VPC and Private Networks** documentation page for a list of the formats resolved by the DNS service. 7. Click **Attach to Private Network** to conclude.