alauda · SuJinpei · Mar 25, 2026 · Mar 25, 2026
diff --git a/docs/en/appservice/mysql/pxc.mdx b/docs/en/appservice/mysql/pxc.mdx
@@ -6,6 +6,10 @@ i18n:
 title: About Alauda Database Service for MySQL-PXC
 ---
 
+:::warning Deprecation Notice
+MySQL-PXC is deprecated and no longer managed by the MySQL operator. Existing PXC clusters will continue to run but will not receive operator updates. Please migrate to [MySQL-MGR](./mgr.mdx) for continued support and new deployments. See <ExternalSiteLink name="mysql-mgr" href="/how_to/35-migrate-from-pxc" children="Migrate MySQL-PXC to MySQL-MGR" /> for detailed migration instructions.
+:::
+
 Alauda Database Service for MySQL-PXC is a high availability database solution using synchronous replication based on Percona XtraDB Cluster, running on Kubernetes. It provides the capability for automated deployment and management of objects within the Percona XtraDB Cluster, and can also be used to start new Percona XtraDB Cluster instances or scale existing instance.
 
 <ExternalSite name="mysql-pxc" href="/intro" />
diff --git a/docs/en/appservice/overview/architecture.mdx b/docs/en/appservice/overview/architecture.mdx
@@ -23,7 +23,6 @@ The Alauda Application Services platform supports various types of services, inc
 
   | Alauda Application Services | Version                    | Data Persistence Compatible Storage Class | Backup Compatible Storage Class | Default Scheduling Rule (Single Instance)                                                                                    |
   | ------------------- | ------------------------- | --------------------------------------- | ------------------------------ | ----------------------------------------------------------------------------------------------- |
-  | MySQL-PXC           | 5.7                       | TopoLVM (recommended)                  | S3 (recommended), TopoLVM     | At most (required) only one MySQL node can be scheduled on each node.                                                               |
   | MySQL-MGR           | 8.0                       | TopoLVM (recommended)                  | S3 (recommended)               | At most (required) only one MySQL node can be scheduled on each node.                                                              |
   | Redis               | 5.0, 6.0, 7.2 (recommended) | TopoLVM (recommended)                  | S3 (recommended), CephFS, NFS  | Cluster mode: At most (required) only one Redis node can be scheduled on each node.  Sentinel mode: At most (required) only one Redis data node or one Redis sentinel node can be scheduled on each node. |
   | Kafka               | 3.8 (recommended)         | TopoLVM (recommended)                  | -                              | At most (required) only one Broker node can be scheduled on each node.                                                             |

diff --git a/docs/en/appservice/unified-om/para-template-mgt/functions/param-templates.mdx b/docs/en/appservice/unified-om/para-template-mgt/functions/param-templates.mdx
@@ -5,7 +5,7 @@ sourceSHA: f629c4a27b114868ccf8dea89c926cdc1d8507d07e379c719c9c543b1d47c86d
 
 # Parameter Template Management
 
-The parameter template feature is designed for the unified management and maintenance of parameter sets for various components. This includes viewing which parameters are included in the parameter templates, along with their default values and descriptions. Currently, the components that support parameter templates are MySQL (including PXC and MGR), Redis, and Kafka. The platform comes with pre-configured parameter templates for different scenarios and component specifications, representing industry best practices for use in those scenarios, thus allowing users to utilize them directly. Additionally, users can create custom parameter templates based on their specific business needs, facilitating internal standards implementation. All parameter templates can be selected for use when creating instances.
+The parameter template feature is designed for the unified management and maintenance of parameter sets for various components. This includes viewing which parameters are included in the parameter templates, along with their default values and descriptions. Currently, the components that support parameter templates are MySQL (MGR), Redis, and Kafka. The platform comes with pre-configured parameter templates for different scenarios and component specifications, representing industry best practices for use in those scenarios, thus allowing users to utilize them directly. Additionally, users can create custom parameter templates based on their specific business needs, facilitating internal standards implementation. All parameter templates can be selected for use when creating instances.
 
 ## Main Features
 
@@ -18,7 +18,7 @@ Users can click on the parameter template to access the list page, as shown in t
 On this page, users can view the parameter templates for specific projects according to component type and template type. The supported component types currently include MySQL, Redis, and Kafka. The template types available are the platform's pre-configured templates and user-defined templates. The platform's pre-configured templates are universally applicable across the entire cluster, while users can create custom templates specifically for the current project.
 
 ::: info
-The parameter templates for MySQL can be applicable to both PXC architecture and MGR architecture.
+The parameter templates for MySQL are applicable to MGR architecture.
 :::
 
 ### View Details of a Specified Parameter Template

diff --git a/docs/en/appservice/upgrade.mdx b/docs/en/appservice/upgrade.mdx
@@ -5,14 +5,22 @@ en: Upgrade
 
 # Upgrade
 
+:::warning
+PXC Removal in Alauda Database Service for MySQL v4.3.0
+
+**MySQL-PXC is deprecated** and **removed** starting from Alauda Database Service for MySQL v4.3.0. Existing PXC instances will continue running but are no longer managed by the MySQL operator. If you have PXC instances, you **must migrate them to MySQL-MGR before upgrading** to MySQL Operator v4.3.0 or later.
+
+- **Migration Guide**: See <ExternalSiteLink name="mysql-mgr" href="/how_to/35-migrate-from-pxc" children="Migrate MySQL-PXC to MySQL-MGR" /> for comprehensive step-by-step instructions covering schema compatibility, character sets, users, and privileges.
+- **MySQL Operator Upgrade Guide**: See <ExternalSiteLink name="mysql-mgr" href="/upgrade" children="Upgrade Guide" /> for pre-upgrade checklists, upgrade scenarios, and emergency response procedures.
+:::
+
 Alauda Container Platform Data Services Essentials are designed to upgrade automatically during platform upgrades, requiring no manual intervention. The system handles all necessary migrations and updates seamlessly in the background.
 
 Alauda Container Platform Data Services RDS Framework will execute upgrades based on the configured upgrade strategy:
 * **Automatic**: Auto-upgrades are triggered immediately upon detecting new component versions.
 * **Manual**: Requires manual approval before initiating the upgrade process.
 
 :::warning
-When upgrading ACP from v3 to v4, it is recommended to promptly upgrade both the global cluster and workload clusters to the new version to ensure proper display of Data Services view.  
+When upgrading ACP from v3 to v4, it is recommended to promptly upgrade both the global cluster and workload clusters to the new version to ensure proper display of Data Services view.
 If only the global cluster is upgraded to v4 while workload clusters remain on v3, please contact the technical team during this period to obtain mitigation steps for view display issues in unupgraded workload clusters.
 :::
-
diff --git a/docs/en/configure/backup/application/backup-app.mdx b/docs/en/configure/backup/application/backup-app.mdx
@@ -16,7 +16,7 @@ Create an application backup schedule to define the scope of data to back up (by
 
 :::warning
 * To back up application data, include PersistentVolumeClaims (PVCs). PVCs bound to `hostPath` PersistentVolumes are not supported.
-* To ensure reliability and data integrity, do not back up database data (for example, MySQL-PXC, Redis). Use Data Services for database backups.
+* To ensure reliability and data integrity, do not back up database data (for example, MySQL, Redis). Use Data Services for database backups.
 * Avoid reads, writes, updates, and deletes in the namespaces being backed up to prevent drift and inconsistencies after migration.
 :::
 <Steps>

diff --git a/docs/en/upgrade/pre-upgrade.mdx b/docs/en/upgrade/pre-upgrade.mdx
@@ -10,6 +10,10 @@ weight: 20
 
 Before starting, ensure your current platform version is within the supported upgrade range.
 
+:::warning MySQL-PXC Removed in Alauda Database Service for MySQL v4.3.0
+If you have **MySQL-PXC** instances, they will become **unmanaged** after upgrading to ACP v4.3.0 or later (when the MySQL operator is also upgraded). See <ExternalSiteLink name="mysql-mgr" href="/upgrade" children="MySQL Operator Upgrade Guide" /> for migration instructions.
+:::
+
 ## Important Notes
 
 - Ensure the directory `/cpaas/minio` on the control plane nodes of global cluster has at least **120 GB** of free disk space.

diff --git a/docs/en/upgrade/upgrade_global_cluster.mdx b/docs/en/upgrade/upgrade_global_cluster.mdx
@@ -4,6 +4,10 @@ weight: 30
 
 # Upgrade the global cluster
 
+:::warning MySQL-PXC Removed in Alauda Database Service for MySQL v4.3.0
+Upgrading the global cluster will also upgrade the MySQL operator. If you have PXC instances, they will become unmanaged after the operator upgrade. See <ExternalSiteLink name="mysql-mgr" href="/upgrade" children="MySQL Operator Upgrade Guide" /> for migration instructions before upgrading.
+:::
+
 <Term name="productShort" /> consists of a **global cluster** and one or more **workload clusters**. The global cluster **must** be upgraded before any workload clusters.
 
 This document walks you through the upgrade procedure for the global cluster.

diff --git a/docs/en/upgrade/upgrade_workload_cluster.mdx b/docs/en/upgrade/upgrade_workload_cluster.mdx
@@ -4,12 +4,16 @@ weight: 30
 
 # Upgrade Workload Clusters
 
+:::warning MySQL-PXC Removed in Alauda Database Service for MySQL v4.3.0
+**MySQL-PXC is removed** starting from Alauda Database Service for MySQL v4.3.0. Existing PXC instances will no longer be managed by the MySQL operator after upgrading to ACP v4.3.0 or later. See <ExternalSiteLink name="mysql-mgr" href="/upgrade" children="MySQL Operator Upgrade Guide" /> for migration instructions before upgrading.
+:::
+
 After completing the upgrade of the global cluster, you can proceed to upgrade the workload clusters.
 The workload cluster upgrade process is similar to that of the global cluster but requires attention to the following considerations:
 
 - If your platform uses the **global disaster recovery (DR)** solution, you **must complete the upgrade of both the primary and standby global clusters** before upgrading any workload clusters.
 - All **PostgreSQL** instances will be **automatically restarted** during the upgrade.
-- For **MySQL-PXC**, **MySQL-MGR**, **Redis**, **Kafka**, and **RabbitMQ** instances configured with an **automatic update strategy**, the upgrade process includes a restart, which may lead to **temporary service disruption**.
+- For **MySQL-MGR**, **Redis**, **Kafka**, and **RabbitMQ** instances configured with an **automatic update strategy**, the upgrade process includes a restart, which may lead to **temporary service disruption**.
 - A maximum of **20 workload clusters** can be upgraded concurrently.
 
 ## Upgrade a workload cluster

diff --git a/docs/shared/functionresources/functionresources.yaml b/docs/shared/functionresources/functionresources.yaml
@@ -1421,8 +1421,8 @@ items:
     annotations:
       auth.cpaas.io/functionresource.function.id: "1"
       auth.cpaas.io/functionresource.module.id: "8"
-      cpaas.io/functionresource.function.display-name: MySQL (PXC) 实例管理
-      cpaas.io/functionresource.function.display-name.en: MySQL (PXC) Instance
+      cpaas.io/functionresource.function.display-name: MySQL 实例管理
+      cpaas.io/functionresource.function.display-name.en: MySQL Instance
       cpaas.io/functionresource.module.display-name: Data Service
       cpaas.io/functionresource.module.display-name.en: Data Service
       helm.sh/chart-version: v3.19.0-beta.88.gb325a12b
@@ -1441,12 +1441,6 @@ items:
     uid: 6c37f95e-863a-4600-8f50-5b8bcd64e131
   spec:
     rules:
-    - apiGroup: pxc.percona.com
-      bindCluster: unlimit
-      bindNamespacePart: common
-      bindScope: namespace
-      resources:
-      - perconaxtradbclusters
     - apiGroup: middleware.alauda.io
       bindCluster: unlimit
       bindNamespacePart: common
@@ -1560,47 +1554,14 @@ items:
       bindScope: namespace
       resources:
       - mysqlrestores
-- apiVersion: auth.alauda.io/v1beta1
-  kind: FunctionResource
-  metadata:
-    annotations:
-      auth.cpaas.io/functionresource.function.id: "3"
-      auth.cpaas.io/functionresource.module.id: "8"
-      cpaas.io/functionresource.function.display-name: MySQL (PXC) 备份恢复
-      cpaas.io/functionresource.function.display-name.en: MySQL (PXC) Backup/Restore
-      cpaas.io/functionresource.module.display-name: Data Service
-      cpaas.io/functionresource.module.display-name.en: Data Service
-      helm.sh/chart-version: v3.19.0-beta.88.gb325a12b
-      helm.sh/original-name: acp-middleware-mysqlrestore
-    creationTimestamp: "2025-02-13T01:53:15Z"
-    generation: 1
-    labels:
-      auth.cpaas.io/functionresource.function: mysqlrestore
-      auth.cpaas.io/functionresource.module: middleware
-      auth.cpaas.io/product: console-acp
-      helm.sh/chart-name: auth-manager
-      helm.sh/release-name: auth-manager
-      helm.sh/release-namespace: cpaas-system
-    name: acp-middleware-mysqlrestore
-    resourceVersion: "6753"
-    uid: ba29feb9-7a5c-4ef6-988a-3bc1171f0c8f
-  spec:
-    rules:
-    - apiGroup: pxc.percona.com
-      bindCluster: unlimit
-      bindNamespacePart: common
-      bindScope: namespace
-      resources:
-      - perconaxtradbclusterbackups
-      - perconaxtradbclusterrestores
 - apiVersion: auth.alauda.io/v1beta1
   kind: FunctionResource
   metadata:
     annotations:
       auth.cpaas.io/functionresource.function.id: "2"
       auth.cpaas.io/functionresource.module.id: "8"
-      cpaas.io/functionresource.function.display-name: MySQL (PXC) 用户管理
-      cpaas.io/functionresource.function.display-name.en: MySQL (PXC) User
+      cpaas.io/functionresource.function.display-name: MySQL 用户管理
+      cpaas.io/functionresource.function.display-name.en: MySQL User
       cpaas.io/functionresource.module.display-name: Data Service
       cpaas.io/functionresource.module.display-name.en: Data Service
       helm.sh/chart-version: v3.19.0-beta.88.gb325a12b