Register Cluster

Registering a cluster is a way of managing the cluster by executing commands on the registered cluster and sending registration requests to the global platform.

Prerequisites

• Depending on the type of cluster being managed, the versions and parameters of components such as Kubernetes on the managed cluster must meet the version and parameter requirements for managed clusters .

• The repository must support HTTPS access and provide a valid TLS certificate issued by a trusted certificate authority. If this requirement cannot be met, please refer to the FAQ How to trust an insecure repository?

  Tip: The use of public repositories on the public network provided by the platform already satisfies HTTPS access. You only need to verify whether platform defaults and private repositories support HTTPS access.

• If the runtime component connected to the cluster is Containerd, you need to modify the Containerd configuration before connecting to the cluster to ensure successful deployment of distributed storage.

Register Cluster

1. In the left navigation pane, click Clusters > Cluster of clusters.

2. Click Take Over Cluster > Register Cluster.

3. Refer to the following instructions to configure the repository parameters for the storage platform components images required by the registered cluster.

   Parameter	Description
   Platform Default	The repository used when deploying global.
   Private Repository	The external repository you have set up in advance. You need to enter the private repository address, port, username, and password to access the repository.
   Public Repository	Pull the required images from the public repository provided by the platform. You need to ensure that your cluster can access the public network. Before using it, please refer to Update public network repository cloud credentials to obtain repository authentication permissions.

4. Click Create to obtain the registration command on the Registration Command page and run this command in the registered cluster.

   Tip: The registration command is valid for 24 hours. Please reacquire it if it expires.

View Registration Command

You can find the cluster waiting to be registered in the cluster list, and click > View Registration Command, please perform the registration operation before the expiration date.

What’s next

Deployment plugins

After the cluster registration is successful, you can go to Plugin Management to select the necessary plugins for cluster deployment, including monitoring components, Log Agent, log storage components, etc.

Configure cluster audit capabilities

After the cluster registration is successful, it is necessary to modify the configuration related to auditing on the cluster in order to collect the audit data of the cluster through the platform. For specific operations, please refer to How to configure the audit function of a standard Kubernetes cluster registered on the platform? .

Enable Pod Debug

After the cluster registration is successful, if you need to use the Pod Debug feature, please refer to How to enable the Pod Debug feature in the registered cluster? .

Namespace under the tube cluster

After the cluster registration is successful, you can add the cluster to an existing project by creating a project based on the cluster or by adding a cluster associated with a project , and associate the newly registered cluster with the project.

Furthermore, by performing the import namespace operation, existing Kubernetes namespaces within the cluster can be included and managed under the platform’s project.

FAQ

How to Solve Distributed Storage Deployment Failure Issue when Access Cluster Runtime is Containerd?

When the runtime component connected to the cluster is Containerd, the deployment of distributed storage will fail. To resolve this issue, you need to manually modify the Containerd configuration information on all nodes of the cluster and restart Containerd.

Note: If you modify the Containerd configuration by following the steps below before deploying distributed storage, you do not need to perform step 4.

1. Log in to the cluster node and edit the /etc/systemd/system/containerd.service file. Modify the value of the LimitNOFILE parameter to 1048576.

2. Execute the command systemctl daemon-reload to reload the configuration.

3. Execute the command systemctl restart containerd to restart Containerd.

4. Execute the command kubectl delete pod --all -n rook-ceph on the cluster control node to restart all Pods within the rook-ceph namespace and apply the configuration.