[docs] vDB Redis Cluster + PostgreSQL Cluster — release 10/2026: Redis region HAN, Resize Instance Type, pg_cron — VI + EN

English/vdb/README.md

@@ -58,4 +58,4 @@ vDB includes many types of services for each type of database, currently we are
 
 #### Cluster Mode:
 
-<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>yes</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>
+<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>yes</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>yes (HAN)</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>

English/vdb/announcements/release-notes.md

@@ -4,6 +4,28 @@ Summary of updates and new features across all engines in the vDB service.
 
 ***
 
+## October 2026 - vDB Redis Cluster (MDS) — HAN region and Resize Instance Type
+
+GreenNode extends Redis Cluster (MDS) to the **HAN** region and adds **Resize Instance Type**, letting you increase or decrease a cluster's CPU/RAM directly on the portal.
+
+* **New region HAN:** deploy Redis Clusters in Hanoi with availability zones **HAN01-1A** and **HAN01-1B**, alongside the existing HCM region.
+* **Resize Instance Type:** change the instance type of the whole cluster up or down, without creating a new cluster, moving data, or changing the endpoint.
+* If a resize fails, the system automatically reverts the cluster to its previous configuration; data is not affected.
+* Resize Instance Type is currently available in the HAN region only.
+* Learn more at [Manage a Redis Cluster](../memorystore-database-service-mds/redis-cluster/manage-redis-cluster.md).
+
+---
+
+## October 2026 - vDB PostgreSQL Cluster (RDS) — pg_cron extension
+
+GreenNode adds the **pg_cron** extension to PostgreSQL Cluster (RDS), letting you schedule recurring SQL statements with cron syntax directly in the database.
+
+* **pg_cron 1.6** is now in the list of supported extensions for PostgreSQL Cluster.
+* pg_cron runs jobs in the database set by the `cron.database_name` parameter, which defaults to the first database you create when creating the Cluster. The extension can only be created and used in this database.
+* Learn more at [PostgreSQL Cluster Extensions](../relational-database-service-rds/postgresql/postgresql-cluster/vdb-postgresql-cluster-extensions.md) and [PostgreSQL Parameters for Cluster](../relational-database-service-rds/postgresql/postgresql-cluster/postgresql-cluster-parameters.md).
+
+---
+
 ## September 2026 - vDB PostgreSQL Cluster (RDS) — Multi-AZ mode
 
 GreenNode adds the **Multi-AZ** mode to PostgreSQL Cluster (RDS) in the HCM region, letting you spread a cluster's Nodes across two or more availability zones so the cluster keeps serving traffic when one zone fails.

English/vdb/memorystore-database-service-mds/redis-cluster/manage-redis-cluster.md

@@ -1,6 +1,6 @@
 # Manage a Redis Cluster
 
-After creating a Redis Cluster, you can manage its topology, change the number of replicas, trigger manual backups, and delete the cluster directly from the cluster detail page.
+After creating a Redis Cluster, you can manage its topology, change the number of replicas, change the instance type, trigger manual backups, and delete the cluster directly from the cluster detail page.
 
 ***
 
@@ -67,6 +67,59 @@ Each edit allows only **±1 node** at a time. To reach a target node count, save
 
 ***
 
+## Change Instance Type (Resize Instance Type)
+
+You can increase or decrease the instance type (CPU/RAM) of a cluster directly on the portal, without creating a new cluster, moving data, or changing the endpoint in your application.
+
+{% hint style="info" %}
+Resize Instance Type for Redis Cluster is currently available in the **HAN** region only.
+{% endhint %}
+
+* Resizing applies to the **whole cluster**: all nodes switch to the same instance type. You cannot resize individual nodes.
+* Works in both directions: up to a larger package or down to a smaller one.
+* A cluster can be resized only while it is in **ACTIVE** status.
+
+**To change the Instance Type:**
+
+1. Open the **Resize instance type** dialog in one of two ways:
+   * On the Database list page, click the **Action (⋮)** icon of the cluster, then select **Resize Instance Type**.
+
+     ![Action menu with Resize Instance Type](../../../.gitbook/assets/vdb-redis-cluster-resize-action-menu.png)
+   * On the cluster detail page, click the **Resize Instance Type** button in the header.
+
+     ![Resize Instance Type button in the detail page header](../../../.gitbook/assets/vdb-redis-cluster-resize-header-button.png)
+2. In the dialog, select an **Instance family** and a **CPU Platform**, then select a new package in the table. The **Description** column shows how much memory each package provides for your data.
+3. Review the cost on the right side of the dialog:
+   * **CURRENT INSTANCE TYPE:** package and price of the instance type in use.
+   * **NEW INSTANCE TYPE:** package and price of the selected package.
+   * **Total:** equal to the price of the new package.
+
+   Prices shown are the monthly price of one node multiplied by the number of nodes in the cluster.
+4. Click **RESIZE** to apply, or **CANCEL** to close the dialog without changes.
+
+![Resize instance type dialog](../../../.gitbook/assets/vdb-redis-cluster-resize-dialog.png)
+
+Some packages in the table are greyed out and cannot be selected:
+
+* The package currently in use.
+* Smaller packages that cannot hold the amount of data the cluster currently stores.
+
+When increasing the instance type, the system checks your quota for the additional CPU/RAM multiplied by the number of nodes. If the quota is insufficient, the request is rejected with a message and the cluster keeps its current configuration. No quota check is performed when decreasing the instance type.
+
+### During and after resizing
+
+* The cluster switches to **BUILDING** status. During this time, all actions in the Action menu and the header (including Resize Instance Type and Delete) are greyed out and unavailable.
+* While nodes restart one after another, writes to Redis may fail for a short moment each time the master switches. The connection endpoint stays the same.
+* When the resize completes, the cluster returns to **ACTIVE** and the Instance type field shows the new package. All data is preserved.
+* The new package's price applies from the moment the resize succeeds. The Free Backup size also changes with the new package.
+* The **History** tab records the operation with Action **Resize** and Description "Change package from" followed by the old and new package names. Status changes from **IN-PROGRESS** to **FINISHED**.
+
+![Resize row in the History tab](../../../.gitbook/assets/vdb-redis-cluster-resize-history.png)
+
+If the resize fails, the system automatically reverts the cluster to the previous instance type and **ACTIVE** status; data is not affected and the price does not change. The Resize row in the History tab changes to **FAILED**, with the error shown in the **Message** column.
+
+***
+
 ## Manual Backup (Back up now)
 
 The **Back up now** button is located directly in the cluster detail page header, allowing you to create a Full Snapshot immediately without navigating into submenus.
@@ -193,6 +246,7 @@ From the Database list page, click the **Action (⋮)** icon next to a Redis Clu
 
 | Action                       | Description                                                  |
 | ---------------------------- | ------------------------------------------------------------ |
+| **Resize Instance Type**     | Increase or decrease the cluster's instance type (CPU/RAM). Currently available in the HAN region only. |
 | **Edit configuration group** | Edit Redis configuration parameters.                         |
 | **Edit DB settings**         | Edit the cluster name, backup policy, and database settings. |
 | **Delete**                   | Delete the cluster (with confirmation dialog).               |

Vietnamese/vdb/README.md

@@ -64,4 +64,4 @@ vDB gồm nhiều loại dịch vụ cho từng loại cơ sở dữ liệu , hi
 
 #### Cluster Mode:
 
-<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>yes</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>
+<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>yes</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>yes (HAN)</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>

Vietnamese/vdb/announcements/release-notes.md

@@ -4,6 +4,28 @@ Tổng hợp các bản cập nhật và tính năng mới của tất cả các
 
 ***
 
+## Tháng 10, 2026 - vDB Redis Cluster (MDS) — region HAN và Resize Instance Type
+
+GreenNode mở rộng Redis Cluster (MDS) sang region **HAN**, đồng thời bổ sung tính năng **Resize Instance Type** để tăng hoặc giảm CPU/RAM của cluster ngay trên portal.
+
+* **Region mới HAN:** triển khai Redis Cluster tại Hà Nội với các availability zone **HAN01-1A** và **HAN01-1B**, song song với region HCM hiện có.
+* **Resize Instance Type:** đổi instance type cho cả cluster theo cả hai chiều tăng và giảm, không phải tạo cluster mới, không phải chuyển dữ liệu và giữ nguyên endpoint.
+* Hệ thống tự đưa cluster về cấu hình cũ nếu resize gặp lỗi, dữ liệu không bị ảnh hưởng.
+* Resize Instance Type hiện chỉ khả dụng tại region HAN.
+* Tìm hiểu thêm tại [Quản lý Redis Cluster](../memorystore-database-service-mds/redis-cluster/quan-ly-redis-cluster.md).
+
+---
+
+## Tháng 10, 2026 - vDB PostgreSQL Cluster (RDS) — extension pg_cron
+
+GreenNode bổ sung extension **pg_cron** cho PostgreSQL Cluster (RDS), cho phép lên lịch chạy câu lệnh SQL định kỳ theo cú pháp cron ngay trong database.
+
+* **pg_cron 1.6** có trong danh sách extension được hỗ trợ của PostgreSQL Cluster.
+* pg_cron chạy job trên database được chỉ định ở tham số `cron.database_name`, mặc định là database đầu tiên bạn tạo khi khởi tạo Cluster. Extension chỉ tạo và dùng được trong database này.
+* Tìm hiểu thêm tại [PostgreSQL Cluster Extensions](../relational-database-service-rds/postgresql/postgresql-cluster/cac-extension-duoc-ho-tro-cho-cluster.md) và [PostgreSQL Parameters cho Cluster](../relational-database-service-rds/postgresql/postgresql-cluster/cau-hinh-tham-so-cho-cluster.md).
+
+---
+
 ## Tháng 9, 2026 - vDB PostgreSQL Cluster (RDS) — chế độ Multi-AZ
 
 GreenNode bổ sung chế độ **Multi-AZ** cho PostgreSQL Cluster (RDS) tại region HCM, cho phép trải các Node của cluster trên từ hai availability zone trở lên để cluster vẫn phục vụ được khi một zone gặp sự cố.