#Installer Parameters

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

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.

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.

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.

If you do not need to distinguish between Cluster Endpoint and Platform Access Address, enter the same address as the Cluster Endpoint.
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.

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.

Platform Deployment uses the Registry deployed with the global cluster.
External uses a customer-managed platform image registry. Its address and pull credentials must match the values passed to setup.sh, and the registry must already contain the complete target-version Core and Extension payload.

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.

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

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.

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

• 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, adjust it according to the page prompt and add it again.