From cbfe98312474e31de7114856dbcd2c81195f3c49 Mon Sep 17 00:00:00 2001 From: huizhang Date: Wed, 4 Nov 2026 23:00:53 +0800 Subject: [PATCH] docs: clarify ACP 4.4 registry storage support --- docs/en/solutions/ACP_Registry_v2_Migration_Runbook.mdx | 7 ++++++- docs/zh/solutions/ACP_Registry_v2_Migration_Runbook.mdx | 5 ++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/en/solutions/ACP_Registry_v2_Migration_Runbook.mdx b/docs/en/solutions/ACP_Registry_v2_Migration_Runbook.mdx index af843fb0a..f448354b6 100644 --- a/docs/en/solutions/ACP_Registry_v2_Migration_Runbook.mdx +++ b/docs/en/solutions/ACP_Registry_v2_Migration_Runbook.mdx @@ -541,7 +541,12 @@ ac rollout status deployment/image-api-server -n "$MODERN_REGISTRY_NAMESPACE" -- ### Object Storage Reuse -For object storage such as S3, OSS, GCS, Azure, Swift, or IBM COS, configure Registry v2 to use the same bucket or container, endpoint, region, path prefix, credentials, CA, and access parameters that the legacy Registry used. +For S3-compatible object storage, configure the target Registry with the source bucket, endpoint, +region, path prefix, credentials, CA, and access parameters required by the approved migration plan. +ACP 4.4 supports S3, PVC, hostPath-backed PV/PVC, and disposable `emptyDir` storage. Other storage +fields can remain in the API schema, but those backends are outside the ACP 4.4 support scope. +Storage support alone does not establish a migration procedure; contact technical support for a +source backend that is not covered by the approved plan. Do not reuse the S3 procedure for it. If the legacy Registry uses a path prefix and Registry v2 cannot configure the same prefix, use Scenario B instead. Also use Scenario B if the Registry v2 Operator does not support the legacy object storage type or a required access parameter. diff --git a/docs/zh/solutions/ACP_Registry_v2_Migration_Runbook.mdx b/docs/zh/solutions/ACP_Registry_v2_Migration_Runbook.mdx index c60df9854..c51471e13 100644 --- a/docs/zh/solutions/ACP_Registry_v2_Migration_Runbook.mdx +++ b/docs/zh/solutions/ACP_Registry_v2_Migration_Runbook.mdx @@ -542,7 +542,10 @@ ac rollout status deployment/image-api-server -n "$MODERN_REGISTRY_NAMESPACE" -- ### 对象存储重用 -对于 S3、OSS、GCS、Azure、Swift 或 IBM COS 等对象存储,配置 Registry v2 使用与遗留 Registry 相同的存储桶或容器、端点、地域、路径前缀、凭据、CA 和访问参数。 +对于兼容 S3 的对象存储,按照已确认的迁移方案,为目标 Registry 配置源存储桶、端点、地域、路径前缀、凭据、CA 和访问参数。 +ACP 4.4 支持 S3、PVC、基于 hostPath 的 PV/PVC,以及用于可丢弃数据的 `emptyDir`。 +API schema 中可能保留其他存储字段,但这些后端不属于 ACP 4.4 承诺支持的范围。 +存储类型受支持并不代表已有对应的迁移流程;源存储不在已确认方案范围内时,请联系技术支持,不要套用 S3 迁移步骤。 如果遗留 Registry 使用路径前缀且 Registry v2 无法配置相同的前缀,则请改用场景 B。如果 Registry v2 Operator 不支持遗留对象存储类型或所需的访问参数,也请使用场景 B。