Complete the Registration of a Supervisor Cluster in vSphere with Tanzu

As a vSphere administrator, you can register a Tanzu Kubernetes Grid Service Supervisor Cluster running in vSphere with Tanzu with Tanzu Mission Control.

Note: The procedure described in this topic explains how to complete the registration of a Supervisor Cluster running in vSphere with Tanzu using the command-line approach. You can also accomplish this task using the vSphere Client web interface, as described in Integrate the Tanzu Kubernetes Grid on the Supervisor with Tanzu Mission Control in the vSphere with Tanzu Configuration and Management documentation.

Prerequisites

This procedure assumes that you have already started the registration process in Tanzu Mission Control as described in Register a Management Cluster with Tanzu Mission Control, and that you have a Tanzu Kubernetes Grid Service Supervisor Cluster running in vSphere with Tanzu.

To register a Supervisor Cluster running in vSphere with Tanzu with Tanzu Mission Control so that you can manage the lifecycle of its workload clusters, your vSphere instance must be one of the following:

vSphere 7.0 U3a or later
vSphere 8.0 U1 or later

Procedure

In a command window, log in to the Supervisor Cluster with administrative credentials, as described in Connect to the Supervisor Cluster as a vCenter Single Sign-On User in the vSphere with Tanzu Configuration and Management documentation.
Make sure your current context is set appropriately for the Supervisor Cluster you want to register.
You might need to run a kubectl config use-context command to explicitly set the context, for example:
```
kubectl config use-context CONTEXT-NAME-IP
```
Use the context that is listed as an IP address.
Locate the Tanzu Mission Control namespace on the Supervisor Cluster.
The following kubectl command returns namespaces on the cluster.
```
kubectl get ns
```
The Tanzu Mission Control namespace begins with svc-tmc-, for example:
```
svc-tmc-c8                                  Active   14m
```

Create a YAML file to contain the AgentInstall resource information, for example tmc-registration.yaml.

Enter the following YAML code in the file.

apiVersion: installers.tmc.cloud.vmware.com/v1alpha1
kind: AgentInstall
metadata:
  name: tmc-agent-installer-config
  namespace: TMC-NAMESPACE
spec:
  operation: INSTALL
  registrationLink: TMC-REGISTRATION-URL

Replace TMC-NAMESPACE with the name of namespace that you retrieved from the cluster.

Replace TMC-REGISTRATION-URL with the URL provided by Tanzu Mission Control when you started the registration process.

The resulting YAML file should look something like this:

apiVersion: installers.tmc.cloud.vmware.com/v1alpha1
kind: AgentInstall
metadata:
  name: tmc-agent-installer-config
  namespace: svc-tmc-c8
spec:
  operation: INSTALL
  registrationLink: https://myorg.tmc.cloud.vmware.com/installer?id=121f2verylongstring23e&source=registration

Save and close the file.

In your command window, run a kubectl create command to apply the registration YAML to your Supervisor Cluster.
For example:
```
kubectl create -f tmc-registration.yaml
```
When you run this command the Tanzu Mission Control cluster agent is installed on the Supervisor Cluster. The resulting output looks something like this:
```
agentinstall.installers.tmc.cloud.vmware.com/tmc-agent-installer-config created
```
You can optionally run a kubectl describe command like the following to monitor the progress of the installation.
```
kubectl -n TMC-NAMESPACE describe agentinstall tmc-agent-installer-config
```
When the status: line at the bottom of the output changes from INSTALLATION_IN_PROGRESS to INSTALLED, the installation is complete.

Results

When the installation is complete, your Supervisor Cluster running in vSphere with Tanzu is registered with Tanzu Mission Control. You can return to the Tanzu Mission Control console and view the registered Supervisor Cluster on the Management clusters tab of the Administration page. It might take a few minutes for Tanzu Mission Control to start receiving health information from the Supervisor Cluster.