#Overview

By following this guide, you will complete the installation of Core. If you need to understand the concept of Core, refer to Architecture.

Installing Core refers to the process of deploying the global cluster.

After the installation, you can create new workload clusters or connect existing ones, and install additional Extensions to enhance the platform's capabilities.

#Installation Method

The installation process of the global cluster is mainly divided into three stages:

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.

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 the network plugin (Kube-OVN or Calico), 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.

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.

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.

#Appendix — Customer Portal

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.

#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.

#Usage Guidance

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.