Basic Cluster Management

Node Expansion

The cluster created by installation from the host supports node expansion operations. Click Node Expansion on the cluster page to enter the node configuration management page. Add additional nodes and select their attributes as with orchestrating nodes when adding a cluster. It should be noted that existing nodes cannot be changed, only new nodes can be added. The new node needs to meet the corresponding requirements as the node when it was first installed. After the arrangement is complete, click Expand to enter the expansion process.

It should be noted that node expansion, especially the expansion of management nodes and ETCD nodes, may have a certain impact on cluster services, and you need to choose an appropriate time to proceed. The expansion of computing nodes has no impact on existing services.

Cluster Uninstall

Kato Region Service Uninstall

The initialized and unconnected cluster can be uninstalled by clicking the uninstall button in the Kubernetes cluster list. If the connected cluster needs to be uninstalled, you need to delete the connected cluster in the enterprise view cluster management. After the Kato Region service is uninstalled, the Kubernetes cluster will be in an uninitialized state.

Please note that cluster uninstallation is a dangerous operation, and data cannot be recovered after uninstallation.

Uninstall from the Kubernetes Cluster Installed on the Host

If you really need to uninstall the Kubernetes cluster installed from the host, you only need to do the following:

  1. Delete the kubernetes related containers of all nodes.
  2. Delete the /etc/kubernetes directory.
  3. Delete the cluster record from the platform.

Modify Cluster Metadata

The cluster metadata includes the following:

Cluster name: The cluster name displayed on the platform, generally needs to be set to a name that is easy to recognize.

API address: The control API address of the cluster, which is bound to the certificate and cannot be changed at will.

WebSocket address: websocket communication address, facing browser, mainly used for log push and file download.

HTTP application default depressed suffix: used to assign a default domain name, which needs to be pan-resolution to the cluster gateway IP address.

TCP application access IP: cluster gateway IP address or VIP address.

The certificate is used for two-way authentication during communication. If you need to modify it, you need to synchronize it with the API service of the cluster.