Alauda Container Platform

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.

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:

# Assume that the /root/cpaas-install folder already exists on the machine
tar -xvf {Path to Core Package File}/{Core Package File Name} -C /root/cpaas-install
cd /root/cpaas-install/installer || exit 1
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 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.

bash setup.sh
WARNING

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

bash setup.sh --network-mode calico

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.

bash setup.sh --ip-family ipv6

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 Platform Management 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:

# Check if there are failed Charts
kubectl get apprelease --all-namespaces
# Check if there are failed Pods
kubectl get pod --all-namespaces | awk '{if ($4 != "Running" && $4 != "Completed")print}' | awk -F'[/ ]+' '{if ($3 != $4)print}'

Parameter Description

ParameterDescription
Kubernetes Version

All optional versions are rigorously tested for stability and compatibility.
Recommendation: Choose the latest version for optimal features and support.

Cluster Network Protocol

Supports three modes: IPv4 single stack, IPv6 single stack, IPv4/IPv6 dual stack.
Note: If you select dual stack mode, ensure all nodes have correctly configured IPv6 addresses; the network protocol cannot be changed after setting.

Cluster Address

    Enter the pre-prepared domain name. If no domain name is available, enter the pre-prepared global VIP.
    Self-Built VIP is disabled by default, only enable it if you have not provided a LoadBalancer. After enabling, the installer will automatically deploy keepalived to provide software load balancing support.
    Note: The following conditions must be met when using Self-Built VIP,

    • A usable VRID is available;
    • The host network supports the VRRP protocol;
    • All control plane nodes and the VIP must be on the same subnet.

    Tip: For single-node deployments in feature experience scenarios, you can directly enter the node IP. There is no need to enable Self-Built VIP or prepare network resources such as global VIP.

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.
    If you need to distinguish, for example, if the global cluster is only for internal network access and the platform needs to provide external network access, enter the pre-prepared domain name or External IP.
    The platform uses HTTPS access by default and does not enable HTTP. If you need to enable HTTP access, enable it in Advanced Settings (not recommended).
    Note: A domain name must be entered in the following cases,

    • A disaster recovery plan for the global cluster is planned;
    • The platform needs to support IPv6 access.

    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.
If you need to use a custom certificate, you can upload an existing certificate.

Image Repository

The Platform Deployment image repository is used by default, which contains images of all components.
If you need to use an External image repository, please contact technical support to obtain the image synchronization plan before configuring.

Container Network

The default subnet and Service network segment of the cluster cannot overlap.
When using the Kube-OVN Overlay network, ensure that the container network and the host network are not in the same network segment, otherwise it may cause network exceptions.

Node Name

If you select Host Name as Node Name, ensure that the host names of all nodes are unique.

global Cluster Platform Node Isolation

Enable only when you plan to run application workloads in the global cluster.
After enabling:

  • Nodes can be set to Platform Exclusive, i.e., only run platform components, ensuring platform and application workloads are isolated;
  • Workloads of the DaemonSet type are excluded.
Add NodeControl Plane Node:
    • Supports adding 1 or 3 control plane nodes (3 for high availability configuration);
    • If Platform Exclusive is enabled, Deployable Applications is forced to be disabled, and control plane nodes only run platform components;
    • If Platform Exclusive is disabled, you can choose whether to enable Deployable Applications, allowing control plane nodes to run application workloads.
Worker Node:
    • If Platform Exclusive is enabled, Deployable Applications is forced to be disabled;
    • If Platform Exclusive is disabled, Deployable Applications is forced to be enabled.

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:

docker rm -f minialauda-control-plane
ON THIS PAGE