From 9cd4096f1db426a6e29b6381be5adeb1a12d1a36 Mon Sep 17 00:00:00 2001 From: youyongsong Date: Thu, 30 Apr 2026 11:42:40 +0800 Subject: [PATCH] refactor: reorganize install documentation structure - Add planning.mdx for pre-installation planning guidance - Add validation.mdx for post-installation validation steps - Add next_steps.mdx for post-installation next steps - Update install section weights and navigation - Fix internal links to use relative paths - Update llms.txt to reflect new structure Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/en/install/global_dr.mdx | 2 +- docs/en/install/index.mdx | 2 - docs/en/install/installing.mdx | 35 ++------- docs/en/install/next_steps.mdx | 33 ++++++++ docs/en/install/overview.mdx | 75 ++++++++----------- docs/en/install/planning.mdx | 51 +++++++++++++ docs/en/install/prepare/download.mdx | 24 ++++-- .../en/install/prepare/node_preprocessing.mdx | 4 +- docs/en/install/validation.mdx | 34 +++++++++ llms.txt | 7 +- 10 files changed, 182 insertions(+), 85 deletions(-) create mode 100644 docs/en/install/next_steps.mdx create mode 100644 docs/en/install/planning.mdx create mode 100644 docs/en/install/validation.mdx diff --git a/docs/en/install/global_dr.mdx b/docs/en/install/global_dr.mdx index 24972c209..3c2163de7 100644 --- a/docs/en/install/global_dr.mdx +++ b/docs/en/install/global_dr.mdx @@ -1,5 +1,5 @@ --- -weight: 40 +weight: 60 --- # Global Cluster Disaster Recovery diff --git a/docs/en/install/index.mdx b/docs/en/install/index.mdx index 80997f4fb..cf6f2aa6e 100644 --- a/docs/en/install/index.mdx +++ b/docs/en/install/index.mdx @@ -4,6 +4,4 @@ weight: 20 # Install -This document will provide all the information regarding the installation of . - diff --git a/docs/en/install/installing.mdx b/docs/en/install/installing.mdx index a28d686b3..09b00c05d 100644 --- a/docs/en/install/installing.mdx +++ b/docs/en/install/installing.mdx @@ -4,7 +4,7 @@ weight: 30 # Installing -This section describes the specific steps for installing the `global` cluster. +This section describes how to install Core and deploy the `global` cluster. Before starting the installation, please ensure that you have completed the prerequisite checks, installation package download and verification, node preprocessing, and other preparatory work. @@ -24,7 +24,7 @@ cd /root/cpaas-install/installer || exit 1 - This machine will become the first control plane node after the `global` cluster installation is complete. - After the Core Package is extracted, at least **100GB** of disk space is required. Please ensure sufficient storage resources. -- If you have already downloaded extensions, complete the ACP Core installation first, and then follow [Extend](/extend) to upload and install them. +- If you have already downloaded extensions, complete the Core installation first, and then follow [Extend](../extend/index.mdx) to upload and install them. ### Start the Installer \{#start_installer} @@ -55,32 +55,11 @@ After completing the installation parameter configuration according to the page [Parameter Description](#parameters) provides detailed descriptions of key parameters. Please read carefully and configure according to actual needs. -### Verify Successful Installation - -After the installation is complete, the platform access URL will be displayed on the page. Click the **Access** button to open the platform Web UI and verify whether the platform is accessible. - -Next, run the following commands on the installation node to verify the installation status: - -```shell -# Check if there are any failed Charts -kubectl get apprelease --all-namespaces -# Check if there are any Pods not in Running or Completed status -kubectl get pod --all-namespaces | awk '{if ($4 != "Running" && $4 != "Completed")print}' | awk -F'[/ ]+' '{if ($3 != $4)print}' -``` - -### Install Product Docs Plugin - -:::info -The **Alauda Container Platform Product Docs** plugin provides access to product documentation within the platform. All help links throughout the platform will direct users to this documentation. If this plugin is not installed, clicking help links in the platform will result in 404 access errors. -::: - -1. Navigate to **Administrator**. - -2. In the left sidebar, click **Marketplace** > **Cluster Plugins** and select the `global` cluster. + -3. Locate the **Alauda Container Platform Product Docs** plugin and click **Install**. +## Validate the Installation - +After the installer reports that Core installation is complete, validate the platform before continuing with post-install tasks. For the checklist and commands, see [Validation](./validation.mdx). ## Parameter Description \{#parameters} @@ -204,4 +183,6 @@ nerdctl rm -f minialauda-control-plane ## Additional Resources -- [Upload and Install Extensions](../extend) +- [Upload and Install Extensions](../extend/index.mdx) +- [Validation](./validation.mdx) +- [Next Steps](./next_steps.mdx) diff --git a/docs/en/install/next_steps.mdx b/docs/en/install/next_steps.mdx new file mode 100644 index 000000000..994003b98 --- /dev/null +++ b/docs/en/install/next_steps.mdx @@ -0,0 +1,33 @@ +--- +weight: 50 +--- + +# Next Steps + +After Core validation succeeds, complete the following post-install tasks according to your scenario. + +| Priority | Task | When to use | Continue with | +| --- | --- | --- | --- | +| Recommended immediately | Install the Product Docs plugin. | Install this plugin so in-console help links can open product documentation. | [Install Product Docs Plugin](#install_product_docs_plugin) | +| Conditional | Configure Global Cluster Disaster Recovery. | Use this path when your environment requires primary and standby `global` clusters. | [Global Cluster Disaster Recovery](./global_dr.mdx) | +| Conditional | Create workload clusters or connect existing clusters. | Use this path when your architecture requires workload clusters separate from the `global` cluster. | [Clusters](../configure/clusters/index.mdx) | +| Conditional | Upload and install Extensions Packages. | Use this path when you need additional platform capabilities after Core is installed. | [Extend](../extend/index.mdx) | +| Recommended before broad user onboarding | Configure identity providers, users, roles, projects, and project membership. | Use this path before onboarding administrators, project users, or application teams. | [Users and Roles](../security/users_and_roles/index.mdx) and [Projects](../security/project/index.mdx) | +| Recommended before application workloads | Prepare storage, networking, registry access, and workload prerequisites. | Use this path before application teams deploy workloads. | [Storage](../configure/storage/index.mdx), [Networking](../configure/networking/index.mdx), [Registry](../developer/registry/index.mdx), and [Clusters](../configure/clusters/index.mdx) | +| Recommended before production operation | Review backup, upgrade, monitoring, and operational documentation. | Use this path before operating the platform for production workloads. | [Backup](../configure/backup/index.mdx), [Upgrade](../upgrade/index.mdx), and [Observability](../observability/index.mdx) | + +These tasks do not all apply to every installation. Follow the paths that match your deployment architecture and operational requirements. + +## Install Product Docs Plugin \{#install_product_docs_plugin} + +The ** Product Docs** plugin provides access to product documentation within the platform. All help links throughout the platform direct users to this documentation. If this plugin is not installed, clicking help links in the platform results in 404 access errors. + + +### Open Cluster Plugins + +Navigate to **Administrator**. In the left sidebar, click **Marketplace** > **Cluster Plugins** and select the `global` cluster. + +### Install the Plugin + +Locate the ** Product Docs** plugin and click **Install**. + diff --git a/docs/en/install/overview.mdx b/docs/en/install/overview.mdx index 854391b2c..af08eda18 100644 --- a/docs/en/install/overview.mdx +++ b/docs/en/install/overview.mdx @@ -4,64 +4,49 @@ weight: 10 # Overview -By following this guide, you will complete the installation of ** Core**. -If you need to understand the concept of ** Core**, refer to [Architecture](../overview/architecture.mdx). +Use the Install section to plan and complete ** Core** installation. -Installing ** Core** refers to the process of deploying the `global` cluster. + Core installation deploys the `global` cluster, which provides the platform management plane for web console access, cluster management, users and roles, and extension management. For the platform architecture and definitions of `global` cluster and workload cluster, see [Architecture](../overview/architecture.mdx) and [Glossary](../overview/glossary.mdx). -After the installation, you can **create new workload clusters** or **connect existing ones**, and install additional **Extensions** to enhance the platform's capabilities. + Core installation does not create workload clusters, import existing clusters, or install Extensions Packages. Operators and Cluster Plugins that are delivered as Extensions are installed after Core through the [Extend](../extend/index.mdx) workflow. -Before installation, please ensure that you have completed capacity planning, environment preprocessing, and prerequisite checks to ensure that the hardware, network, and OS of each node meet the requirements. -The following content covers platform architecture design, installation methods, and key term explanations to help you grasp the core points during the actual installation process. + Core installation does not support direct installation of the `global` cluster into an existing Kubernetes environment. Prepare new nodes that meet the hardware, network, storage, and OS requirements before you start installation. -## Installation Method +## Installation Scope -The installation process of the `global` cluster is mainly divided into three stages: + Core installation provides the foundation for the platform management plane. After Core is installed and verified, you can create or connect workload clusters and install Extensions according to your platform scenario. -1. **Preparation Stage** - - **Prerequisite Check**: Ensure that all node hardware, network, and OS meet the requirements, such as kernel version, CPU architecture, and network configuration. - - **Installation Package Download**: Log in to the Customer Portal to obtain the latest installation package. - - **Node Preprocessing**: Complete the preprocessing work of all nodes. +The following work is outside the Core installation flow: -2. **Execution Stage** - - **Installation Package Upload and Extraction**: Upload the installation package to the target control plane node (recommended directory: `/root/cpaas-install`) and extract the installation resources. - - **Start the Installer**: Execute the installation script (such as `bash setup.sh`) on the control plane node, and select IP protocol mode (IPv4/IPv6/dual stack) and VIP configuration according to the actual environment. - - **Parameter Configuration**: Access the Web UI provided by the installer, and set the Kubernetes version, cluster network, node name, access address, and other key parameters in sequence to complete the installation of the `global` cluster. +- Creating workload clusters. +- Connecting existing Kubernetes clusters. +- Uploading and installing Extensions Packages. +- Installing Operators or Cluster Plugins that are delivered as Extensions. +- Configuring optional platform capabilities such as storage, monitoring, backup, registry, or identity integrations. -3. **Verification Stage** - - **System Status Check**: After the installation is complete, log in to the platform Web UI to check the cluster status and the operating status of each component. - - **CLI Verification**: Use command-line tools to check the cluster resource status to ensure that all services are running normally and there are no exceptions or failures. +## Installation Workflow -The following chapters will further explain the detailed operations, configuration parameters, and verification methods of each installation stage. Please read carefully and complete the corresponding preparatory work before the formal installation. + Core installation follows this high-level path: -## Appendix — Customer Portal +1. [Plan](./planning.mdx). Choose the deployment architecture and confirm install-time decisions. +2. [Prepare for installation](./prepare/index.mdx). Prepare resources, network access, storage, and nodes. +3. [Download](./prepare/download.mdx). Obtain the official Core Package from the Customer Portal. +4. [Installing](./installing.mdx). Upload the Core Package, start the installer, and configure installation parameters. +5. [Validation](./validation.mdx). Confirm that the platform Web UI, core applications, and Pods are healthy. +6. [Next Steps](./next_steps.mdx). Install the Product Docs plugin and follow scenario-based next steps. -** Customer Portal** is 's unified customer service and delivery platform that provides centralized access to all product-related resources and support services. It serves as the official entry point for customers, partners, and delivery teams to obtain software packages, documentation, support, and license management in a secure and consistent manner. +The Customer Portal is the official source for installation packages. For download requirements and package architecture options, see [Download](./prepare/download.mdx). -### Purpose and Overview - -The Customer Portal streamlines the end-to-end product lifecycle—from installation and configuration to maintenance and support—by consolidating all essential resources into one platform. It ensures that every deployment is based on verified software versions and official technical guidance. - -### Key Features - -* **Product Downloads** - Provides access to verified installation and upgrade packages, ensuring that deployments are consistent with the latest supported product versions. - -* **Knowledge Base** - Offers comprehensive product documentation, technical articles, troubleshooting guides, and best practices to assist with installation, configuration, and operations. - -* **Support Tickets** - Enables users to submit, track, and manage support requests directly online, ensuring timely issue resolution and full visibility into support progress. - -* **Application Marketplace** - Delivers a curated collection of official and third-party extensions that can be installed to extend or customize the platform's capabilities. - -* **License Management** - Supports the application, activation, and renewal of software licenses, providing traceable and compliant license usage across all environments. + +If you have already downloaded Extensions Packages, install Core first. Upload and install Extensions Packages only after Core installation is complete. + -### Usage Guidance +## Related Documentation -Before starting installation or upgrade activities, users should log in to the ** Customer Portal** using their authorized account to download the required installation packages and verify license status. -For customer delivery and production environments, the versions and documentation published on the Customer Portal should always be regarded as the **official baseline** for deployment and maintenance. +- [Architecture](../overview/architecture.mdx) +- [Glossary](../overview/glossary.mdx) +- [Kubernetes Support Matrix](../overview/kubernetes-support-matrix.mdx) +- [Disk Configuration Requirements](../configure/scalability/disk_configuration.mdx) +- [Extend](../extend/index.mdx) diff --git a/docs/en/install/planning.mdx b/docs/en/install/planning.mdx new file mode 100644 index 000000000..148faeb58 --- /dev/null +++ b/docs/en/install/planning.mdx @@ -0,0 +1,51 @@ +--- +weight: 15 +--- + +# Plan + +Before you start the installer, choose the deployment architecture and confirm the installation settings that affect later operations. + + + Core installation deploys the `global` cluster on prepared nodes. It does not support direct installation of the `global` cluster into an existing Kubernetes environment. + + +## Choose a Deployment Architecture + +Choose the architecture that matches your business scenario, management model, workload placement, resource planning, and isolation requirements. + +| Architecture | Use when | Planning notes | +| --- | --- | --- | +| Multi-Cluster | You need one `global` cluster to manage multiple workload clusters. | Avoid running non-platform workloads on the `global` cluster. Plan resources for the expected number of managed workload clusters. | +| Single Cluster | You intentionally use one cluster for platform components and application workloads. | Single Cluster supports production use when it fits the business scenario. Because the `global` cluster also runs application workloads, plan resources and platform/workload isolation before installation. | +| Single Node | You need a test or proof-of-concept environment. | Do not use Single Node for production. | + +For resource requirements and sizing guidance, see [Prerequisites](./prepare/prerequisites.mdx). + +## Confirm Install-Time Decisions + +Confirm the following decisions before running the installer: + +| Decision | What to confirm | Continue with | +| --- | --- | --- | +| Package architecture | Choose an x86, ARM, or hybrid Core Package. | [Download](./prepare/download.mdx) | +| Cluster network protocol | Choose IPv4, IPv6, or dual stack before starting the installer. | [Installing](./installing.mdx#start_installer) | +| Cluster Endpoint and Platform Access Address | Prepare the access addresses that cluster components, administrators, and users will use. | [Prerequisites](./prepare/prerequisites.mdx#network-resources) and [Parameter Description](./installing.mdx#parameters) | +| Load balancing | Decide whether to use an external load balancer or Self-built VIP. | [Prerequisites](./prepare/prerequisites.mdx#network-resources) and [LoadBalancer Forwarding Rules](./prepare/prerequisites.mdx#port-forward) | +| Certificates | Decide whether to use installer-generated self-signed certificates or trusted certificates that you provide. | [Prerequisites](./prepare/prerequisites.mdx#network-resources) and [Parameter Description](./installing.mdx#parameters) | +| Image repository | Decide whether to use the platform deployment image repository or an external image repository. | [Parameter Description](./installing.mdx#parameters) | +| Nodes | Confirm node names, node roles, and whether platform node isolation is required. | [Node Preprocessing](./prepare/node_preprocessing.mdx) and [Parameter Description](./installing.mdx#parameters) | +| Global Cluster Disaster Recovery | Decide whether your environment requires primary and standby `global` clusters. | [Global Cluster Disaster Recovery](./global_dr.mdx) | + +If you plan to use Global Cluster Disaster Recovery, read [Global Cluster Disaster Recovery](./global_dr.mdx) before installing Core. Disaster recovery planning affects domain names, VIPs, certificates, load balancer rules, image registry choices, package architecture, and installation parameter consistency. + +## Read Before You Install + +Use the following pages as the source of truth before running the installer: + +- [Prerequisites](./prepare/prerequisites.mdx): Prepare resource, network, and storage requirements. +- [Disk Configuration Requirements](../configure/scalability/disk_configuration.mdx): Confirm disk capacity and performance requirements. +- [Node Preprocessing](./prepare/node_preprocessing.mdx): Check and prepare each node before installation. +- [Download](./prepare/download.mdx): Download the Core Package and select the package architecture. +- [Global Cluster Disaster Recovery](./global_dr.mdx): Plan primary and standby `global` clusters if disaster recovery is required. +- [Installing](./installing.mdx): Upload the Core Package, start the installer, and configure parameters. diff --git a/docs/en/install/prepare/download.mdx b/docs/en/install/prepare/download.mdx index a7eb1de7d..742a12cd3 100644 --- a/docs/en/install/prepare/download.mdx +++ b/docs/en/install/prepare/download.mdx @@ -1,22 +1,34 @@ --- weight: 20 -title: Download --- +# Download \{#download_core_package} -# Download Core Package \{#download_core_package} +Before installation, download the **Core Package** from the ** Customer Portal**. -Before installation, you need to download the **Core Package**. +## About the Customer Portal + +The ** Customer Portal** is the official service and delivery portal for product resources. Use it to obtain verified software packages and official technical guidance for installation, upgrade, and maintenance activities. + +The Customer Portal provides access to the following resources: + +- Product downloads, including installation, upgrade, and extension packages. +- Product documentation and technical guidance. +- Support resources for submitting, tracking, and managing support requests. +- Marketplace packages for extending platform capabilities. +- License-related resources for deployment and maintenance planning. + +Use an authorized account to download the package required for your environment. If you do not have a registered account, contact technical support. Starting from v4.1, if you download both the **Core Package** and the **Extensions Packages**, you must complete the installation of the **Core Package** before uploading and installing **Extensions Packages**. -Log in to the ** Customer Portal** to download the **Core Package**. +For customer delivery and production environments, use the package versions and documentation published on the Customer Portal as the official deployment and maintenance baseline. -Packages are available for **x86**, **ARM**, and **hybrid** architectures. The hybrid package includes images for both x86 and ARM, resulting in a larger package size. Select the package that best matches your environment. +## Choose a Package Architecture -If you do not have a registered account, please contact technical support. +Packages are available for **x86**, **ARM**, and **hybrid** architectures. The hybrid package includes images for both x86 and ARM, resulting in a larger package size. Select the package that best matches your environment. ## Migrating from Single-Architecture to Hybrid diff --git a/docs/en/install/prepare/node_preprocessing.mdx b/docs/en/install/prepare/node_preprocessing.mdx index 32346b4f6..91f28b47a 100644 --- a/docs/en/install/prepare/node_preprocessing.mdx +++ b/docs/en/install/prepare/node_preprocessing.mdx @@ -21,9 +21,9 @@ The platform enforces strict version matching policies for official support: ::: :::info -`x86-64-v2` is a CPU instruction set baseline used by some operating systems, platform images, or optional components. For user-provided operating systems, ACP does not impose a universal `x86-64-v2` requirement on all x86 nodes. If you use older CPUs, verify CPU compatibility according to the selected operating system and the components you plan to deploy. +`x86-64-v2` is a CPU instruction set baseline used by some operating systems, platform images, or optional components. For user-provided operating systems, does not impose a universal `x86-64-v2` requirement on all x86 nodes. If you use older CPUs, verify CPU compatibility according to the selected operating system and the components you plan to deploy. -For ACP-provided immutable operating system images or platform images, follow the CPU baseline requirements documented for those images. +For -provided immutable operating system images or platform images, follow the CPU baseline requirements documented for those images. ::: ### x86 diff --git a/docs/en/install/validation.mdx b/docs/en/install/validation.mdx new file mode 100644 index 000000000..8096339d6 --- /dev/null +++ b/docs/en/install/validation.mdx @@ -0,0 +1,34 @@ +--- +weight: 35 +--- + +# Validation + +Validate Core after the installer completes and before you continue with post-install tasks. + +## Prerequisites + +- Core installation completed. +- You can access the platform Web UI address shown by the installer. +- You can run `kubectl` from the installation node. + +## Validate Web UI Access + +After the installation is complete, the installer displays the platform access URL. Click **Access** to open the platform Web UI and verify that the platform login page is reachable. + +## Validate Core Applications and Pods + +Run the following commands on the installation node: + +```shell +# Check if there are any failed Charts +kubectl get apprelease --all-namespaces +# Check if there are any Pods not in Running or Completed status +kubectl get pod --all-namespaces | awk '{if ($4 != "Running" && $4 != "Completed")print}' | awk -F'[/ ]+' '{if ($3 != $4)print}' +``` + +The installation is ready for post-install tasks when the platform Web UI is accessible, core applications are not failed, and Pods are in the expected `Running` or `Completed` states. + +## Next Step + +After validation succeeds, continue with [Next Steps](./next_steps.mdx). diff --git a/llms.txt b/llms.txt index 16d65afd8..a2c65f540 100644 --- a/llms.txt +++ b/llms.txt @@ -313,11 +313,14 @@ Includes CRD definitions and comprehensive platform guides. ## install - [docs/en/install/global_dr.mdx](docs/en/install/global_dr.mdx): Global cluster disaster recovery guide for ACP using primary and standby global clusters with real-time etcd synchronization. It covers supported failure scenarios, excluded namespaces and data limitations, DNS and VIP planning, primary and standby installation requirements, encryption key copying, etcd Synchronizer plugin configuration, sync verification, failover steps, service restarts, package upload considerations, and routine consistency checks. -- [docs/en/install/installing.mdx](docs/en/install/installing.mdx): Step-by-step guide for installing the ACP `global` cluster from the Core Package. It covers extracting the installer, starting `setup.sh` with optional IPv6 mode, configuring installation parameters in the web UI, verifying app releases and Pods with `kubectl`, installing the Product Docs plugin, detailed parameter guidance for Kubernetes version, endpoints, certificates, image registry, networking, nodes, and cleanup of the installer container. -- [docs/en/install/overview.mdx](docs/en/install/overview.mdx): Overview of ACP Core installation, defining installation as deployment of the `global` cluster before creating or importing workload clusters and installing extensions. It explains preparation, execution, and verification stages, and introduces the Alauda Customer Portal as the official source for downloads, documentation, support, marketplace packages, and license management. +- [docs/en/install/installing.mdx](docs/en/install/installing.mdx): Installing guide for ACP Core and the ACP `global` cluster from the Core Package. It covers extracting the installer, starting `setup.sh` with optional IPv6 mode, configuring installation parameters in the web UI, linking to ACP Core validation, detailed parameter guidance for Kubernetes version, endpoints, certificates, image registry, networking, nodes, and cleanup of the installer container. +- [docs/en/install/next_steps.mdx](docs/en/install/next_steps.mdx): Next steps after ACP Core validation. It directs users to Product Docs plugin installation, Global Cluster Disaster Recovery, workload cluster onboarding, Extensions, identity and access setup, storage, networking, registry access, backup, upgrade, and observability documentation, and includes the Product Docs plugin installation steps. +- [docs/en/install/overview.mdx](docs/en/install/overview.mdx): Overview of ACP Core installation, defining installation as deployment of the `global` cluster and separating ACP Core from workload clusters, imported clusters, Extensions Packages, Operators, and Cluster Plugins. It provides the install route map across planning, preparation, download, installation, validation, and post-install tasks. +- [docs/en/install/planning.mdx](docs/en/install/planning.mdx): Planning guide for ACP Core installation. It compares Multi-Cluster, Single Cluster, and Single Node deployment architectures; lists install-time decisions such as package architecture, IP family, endpoints, load balancing, certificates, image repository, nodes, and Global DR; and links to read-before-install source pages. - [docs/en/install/prepare/download.mdx](docs/en/install/prepare/download.mdx): Preparation guide for downloading the ACP Core Package from the Alauda Customer Portal. It explains architecture choices for x86, ARM, and hybrid packages, the requirement to install Core before extension packages in ACP v4.1 and later, and the process for migrating a single-architecture installation to hybrid by syncing images and removing the `cpaas.io/node-arch-constraint` label if present. - [docs/en/install/prepare/node_preprocessing.mdx](docs/en/install/prepare/node_preprocessing.mdx): Node preprocessing checklist for ACP global cluster installation. It lists supported OS and kernel versions, CPU architecture notes, the `init.sh` quick configuration script, required checks for grub parameters, kernel modules, SELinux, swap, SSH, DNS, routes, ports, packages, temporary mounts, conflicting container or Kubernetes software, filesystem cleanup, cross-node connectivity, unique hostnames, and clock synchronization. - [docs/en/install/prepare/prerequisites.mdx](docs/en/install/prepare/prerequisites.mdx): Prerequisites and resource planning guide for installing an ACP global cluster. It covers deployment architectures for multi-cluster, single-cluster, and single-node setups, minimum CPU and memory guidance including ARM sizing notes, required VIPs, external IPs, domain names, certificates, bandwidth, latency, network segments, and load balancer forwarding rules for ports such as 443, 6443, 11443, and optionally 2379. +- [docs/en/install/validation.mdx](docs/en/install/validation.mdx): ACP Core installation validation guide. It covers Web UI access validation, `kubectl` checks for failed app releases, Pod health checks, expected successful states, and the next step after validation. ## networking