Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/en/install/global_dr.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
weight: 40
weight: 60
---

# Global Cluster Disaster Recovery
Expand Down
2 changes: 0 additions & 2 deletions docs/en/install/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,4 @@ weight: 20

# Install

This document will provide all the information regarding the installation of <Term name="productShort" />.

<Overview overviewHeaders={[]} />
35 changes: 8 additions & 27 deletions docs/en/install/installing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ weight: 30

# Installing

This section describes the specific steps for installing the `global` cluster.
This section describes how to install <Term name="productShort" /> 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.

Expand All @@ -24,7 +24,7 @@ cd /root/cpaas-install/installer || exit 1
<Directive type="info" title="INFO">
- 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 <Term name="productShort" /> Core installation first, and then follow [Extend](../extend/index.mdx) to upload and install them.
</Directive>

### Start the Installer \{#start_installer}
Expand Down Expand Up @@ -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.
</Steps>

3. Locate the **Alauda Container Platform Product Docs** plugin and click **Install**.
## Validate the Installation

</Steps>
After the installer reports that <Term name="productShort" /> 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}

Expand Down Expand Up @@ -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)
33 changes: 33 additions & 0 deletions docs/en/install/next_steps.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
weight: 50
---

# Next Steps

After <Term name="productShort" /> 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) |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Global Cluster Disaster Recovery should not be presented as a normal post-install next step. DR planning affects pre-install decisions such as domain names, VIPs, certificates, LoadBalancer rules, image registry choices, package architecture, and Primary/Standby installation parameter consistency. This PR already states in planning.mdx that users should read the DR guide before installing Core, so listing “Configure Global Cluster Disaster Recovery” here after Core validation can mislead users into planning DR too late. Please remove this row from Next Steps, or reword it to cover only post-install DR verification/drill actions for environments where DR was already planned before installation.

| 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 <Term name="productShort" /> 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 **<Term name="product" /> 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.

<Steps>
### Open Cluster Plugins

Navigate to **Administrator**. In the left sidebar, click **Marketplace** > **Cluster Plugins** and select the `global` cluster.

### Install the Plugin

Locate the **<Term name="product" /> Product Docs** plugin and click **Install**.
</Steps>
75 changes: 30 additions & 45 deletions docs/en/install/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,64 +4,49 @@ weight: 10

# Overview

By following this guide, you will complete the installation of **<Term name="productShort" /> Core**.
If you need to understand the concept of **<Term name="productShort" /> Core**, refer to [Architecture](../overview/architecture.mdx).
Use the Install section to plan and complete **<Term name="productShort" /> Core** installation.

Installing **<Term name="productShort" /> Core** refers to the process of deploying the `global` cluster.
<Term name="productShort" /> 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.
<Term name="productShort" /> 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 <Term name="productShort" /> Core through the [Extend](../extend/index.mdx) workflow.

<Directive type="info" title="INFO">
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.
<Term name="productShort" /> 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.
</Directive>

## Installation Method
## Installation Scope

The installation process of the `global` cluster is mainly divided into three stages:
<Term name="productShort" /> Core installation provides the foundation for the platform management plane. After <Term name="productShort" /> 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 <Term name="company" /> Customer Portal to obtain the latest installation package.
- **Node Preprocessing**: Complete the preprocessing work of all nodes.
The following work is outside the <Term name="productShort" /> 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.
<Term name="productShort" /> Core installation follows this high-level path:

## Appendix — <Term name="company" /> 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 <Term name="company" /> 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.

**<Term name="company" /> Customer Portal** is <Term name="company" />'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 <Term name="productShort" /> installation packages. For download requirements and package architecture options, see [Download](./prepare/download.mdx).

### Purpose and Overview

The <Term name="company" /> 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.
<Directive type="info" title="INFO">
If you have already downloaded Extensions Packages, install <Term name="productShort" /> Core first. Upload and install Extensions Packages only after <Term name="productShort" /> Core installation is complete.
</Directive>

### Usage Guidance
## Related Documentation

Before starting installation or upgrade activities, users should log in to the **<Term name="company" /> 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 <Term name="company" /> 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)
51 changes: 51 additions & 0 deletions docs/en/install/planning.mdx
Original file line number Diff line number Diff line change
@@ -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.

<Directive type="info" title="INFO">
<Term name="productShort" /> Core installation deploys the `global` cluster on prepared nodes. It does not support direct installation of the `global` cluster into an existing Kubernetes environment.
</Directive>

## 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 <Term name="productShort" /> 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.
Loading