Installing
This section describes the specific steps for installing 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.
TOC
Process
Upload and Extract Installation Package
Upload the Core Package installation package to any machine of the global cluster control plane nodes, and extract it according to the following command:
- This machine will become the first control plane node after the
globalcluster 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 downloaded the Extensions Package, please extract it and refer to the documentation included within the package before proceeding to the next steps.
Start the Installer
Execute the following installation script to start the installer. After the installer starts successfully, the command line terminal will output the web console access address.
After waiting for about 5 minutes, you can use a browser on your PC to access the web console provided by the installer.
Ensure that the IP address and port 8080 of the node where the installer is located can be accessed normally, so that the web console provided by the installer can be accessed smoothly after the installer starts successfully.
Network Mode and IP Family
The --network-mode parameter affects the CNI of the global cluster created by the installer. If this parameter is not specified, the CNI of the global cluster will default to Kube-OVN. If you want Calico as the CNI, you must explicitly specify --network-mode calico.
If you plan to create a global cluster with Single-stack Network IPv6, you must explicitly specify --ip-family ipv6 when starting the installer. Without this parameter, the global cluster created by the installer will support Single-stack Network IPv4 and Dual-stack Network by default.
Parameter Configuration
After completing the installation parameter configuration according to the page guide, confirm the installation.
Parameter Description 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 address will be displayed on the page. Click the Access button to jump to the platform Web UI.
In the Administrator view, click Cluster Management > Clusters in sequence, and find the cluster named global.
Select CLI Tools from the drop-down menu on the right, and execute the following command to verify the installation status:
Install Product Docs Plugin
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.
-
Navigate to Administrator.
-
In the left sidebar, click Marketplace > Cluster Plugins and select the
globalcluster. -
Locate the Alauda Container Platform Product Docs plugin and click Install.
Parameter Description
| Parameter | Description |
|---|---|
| Kubernetes Version | All optional versions are rigorously tested for stability and compatibility. |
| Cluster Network Protocol | Supports three modes: IPv4 single stack, IPv6 single stack, IPv4/IPv6 dual stack. |
| Cluster Address |
Enter the pre-prepared domain name. If no domain name is available, enter the pre-prepared Tip: For single-node deployments in feature experience scenarios, you can directly enter the node IP. There is no need to enable |
| Platform Access Address |
If you do not need to distinguish between Cluster Address and Platform Access Address, enter the same address as the Cluster Address. Tip: If you need to configure more platform access addresses, you can add them in Other Settings > Other Platform Access Addresses in the next step. Or, after installation, add them in platform management according to the user manual. |
| Certificate | The platform provides self-signed certificates to support HTTPS access by default. |
| Image Repository | The |
| Container Network | The default subnet and Service network segment of the cluster cannot overlap. |
| Node Name | If you select |
global Cluster Platform Node Isolation | Enable only when you plan to run application workloads in the
|
| Add Node | Control Plane Node:
When using Kube-OVN, you can specify the node network card by entering the gateway name. If the node availability check fails, please adjust it according to the page prompt and add it again. |
Installer Cleanup
Normally, the installer will be automatically deleted after installation. If the installer is not automatically deleted after 30 minutes of installation, please execute the following command on the node where the installer is located to force delete the installer container: