docs: remove MySQL-PXC references from ACP 4.4 and add the migration warning - #1004
Open
SuJinpei wants to merge 3 commits into
Open
docs: remove MySQL-PXC references from ACP 4.4 and add the migration warning#1004SuJinpei wants to merge 3 commits into
SuJinpei wants to merge 3 commits into
Conversation
MySQL-PXC was removed in Alauda Database Service for MySQL v4.3.0 and is no longer shipped, so ACP 4.4 docs should not advertise it. - delete docs/en/appservice/mysql/pxc.mdx (embedded the pxc-docs site) - drop the mysql-pxc sub-site entry from sites.yaml - drop the MySQL-PXC 5.7 row from the appservice architecture matrix - drop PXC wording from the parameter-template page - backup-app.mdx: MySQL-PXC -> MySQL in the do-not-back-up example - functionresources.yaml: rename the two MySQL (PXC) functions to plain MySQL, drop the pxc.percona.com rules, and remove the PXC-only backup/restore FunctionResource (matches release-4.3) - regenerate the llms.txt / llmstxt-state.json entries for the above
Now that the PXC pages are gone from ACP 4.4, customers upgrading from 4.2 with PXC instances have no pointer to the migration path. Port the release-4.3 warning admonition verbatim so the Data Services upgrade page tells them to migrate to MySQL-MGR first. Both ExternalSiteLink targets were verified to exist on mgr-docs release-4.4 (how_to/35-migrate-from-pxc.mdx, upgrade.mdx).
SuJinpei
changed the title
Port the three short-form PXC-removal admonitions from release-4.3 so an admin driving the ACP platform upgrade is warned on the pages they actually follow, not only on the Data Services upgrade page. - upgrade/pre-upgrade.mdx - upgrade/upgrade_global_cluster.mdx - upgrade/upgrade_workload_cluster.mdx Each banner is byte-identical to its release-4.3 counterpart and keeps that page's tailored wording.
Deploying alauda-container-platform with
|
| Latest commit: |
a77c0b8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5ad0242a.alauda-container-platform.pages.dev |
| Branch Preview URL: | https://docs-remove-pxc-4-4.alauda-container-platform.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
MySQL-PXC was deprecated and removed in Alauda Database Service for MySQL v4.3.0 and is no longer shipped by the MySQL operator. ACP 4.4 docs should not advertise it as an available application service — and customers upgrading with existing PXC instances need to be told to migrate first.
release-4.4branched offmaster, which never received the PXC trim that landed onrelease-4.3(#718), so all the PXC references were still present here and none of the migration warnings were.What changed
1. Remove the PXC references
docs/en/appservice/mysql/pxc.mdxmysql-pxcexternal sitesites.yamlmysql-pxcsub-site entry (was still pinned atversion: "4.3")docs/en/appservice/overview/architecture.mdxMySQL-PXC 5.7row from the storage-class compatibility matrixdocs/en/appservice/unified-om/para-template-mgt/functions/param-templates.mdxdocs/en/configure/backup/application/backup-app.mdxdocs/shared/functionresources/functionresources.yamlMySQL (PXC)functions to plainMySQL, dropped thepxc.percona.comrules, and removed the PXC-only backup/restore FunctionResource2. Add the migration warning
docs/en/appservice/upgrade.mdx:::warningPXC-removal admonition, linking the MySQL-MGR migration guide and operator upgrade guidedocs/en/upgrade/pre-upgrade.mdxdocs/en/upgrade/upgrade_global_cluster.mdxdocs/en/upgrade/upgrade_workload_cluster.mdxAll four are ported verbatim from
release-4.3, keeping each page's tailored wording — so an admin driving the platform upgrade is warned on the pages they actually follow, not only on the Data Services page.3. Regenerated artifacts
llms.txt/llmstxt-state.json— removed thepxc.mdxentry and refreshed the descriptions +sha256/sizefor every edited page.Verification
pxc/xtradboccurrences remain outside the intentional warning admonition.sites.yamlandfunctionresources.yamlparse;llmstxt-state.jsonparses.docs/shared/functionresources/functionresources.yamlis now byte-identical torelease-4.3, i.e. this reproduces exactly the trim already reviewed and merged there.release-4.3counterparts.<ExternalSiteLink name="mysql-mgr" ...>targets were confirmed to exist on mgr-docsrelease-4.4:docs/en/how_to/35-migrate-from-pxc.mdxanddocs/en/upgrade.mdx.docs/en/appservice/mysql/now contains onlyindex.mdxandmgr.mdx.Notes for reviewers
param-templates.mdxcarries asourceSHA, but there is no upstream source left to sync from:sourceSHAisdoom translate's staleness marker for the source-language file, and thedocs/zh/tree it points at was deleted from acp-docs on 2025-06-11 (ed1d1de5) and exists on no branch today. The recorded value still matches the original March 2025 zh file, so the marker went stale even before the tree was removed. Nothing can reintroduce the PXC wording; the field is vestigial.