Importing a target managed cluster to the IBM Multicloud Manager hub cluster

You can import clusters from different Kubernetes cloud providers, including IBM Cloud Private. After you configure your file and run cloudctl mc cluster import, the targeted cluster becomes a managed cluster for the IBM Multicloud Manager hub cluster. Unless otherwise specified, complete the import tasks anywhere where you can access the hub cluster and the targeted managed cluster.

Notes:

You need the IBM Cloud Private monitoring service enabled on your hub cluster if you want monitoring integrated with your managed cluster after import.
You cannot import a hub cluster. A hub cluster cannot manage another hub cluster.

Choose from the following instructions to set up your managed cluster:

Required user type or access level: Cluster administrator

See the IBM Multicloud Manager configuration overview for more topics.

If you receive a timeout error, clean-up the failed cluster with the following steps:

While logged into the hub cluster, run the following to check to see if the cluster exists in the list:
```
kubectl get clusters --all-namespaces
```
If the failed managed cluster is in the list, remove it while logged into the hub cluster. If not, then skip to the next step.
```
kubectl delete cluster mycluster -n mycluster
```

While logged into the hub cluster, regenerate your cluster-config.yaml file:

cloudctl mc cluster template mycluster -n mycluster > cluster-import.yaml

Edit the cluster-import.yaml file and change the inception image value from latest to the current version:
```
inception_image: ibmcom/icp-inception:3.2.0
```
Save the file and retry the import.