Prerequisites for Deploying on TKG

This topic provides the prerequisites for deploying VMware Telco Cloud Service Assurance on VMware Tanzu Kubernetes Grid.

You must reserve one static IP address for vitrual IP assingment during the VMware Tanzu Kubernetes Grid Workload cluster deployment. This ClusterIP must be used during the VMware Telco Cloud Service Assurance deployment.
Each control plane node of every cluster that you deploy requires a static IP address. This includes both management clusters and VMware Tanzu Kubernetes Grid clusters. These static IP addresses are required in addition to the static IP address that you assign to Kube-Vip when you deploy a management cluster. To make the IP addresses that your DHCP server assigned to the control plane nodes static, you can configure a DHCP reservation for each control plane node in the cluster, after you deploy it. For instructions on how to configure DHCP reservations, see your DHCP server documentation.
For more information, see the VMware Tanzu Kubernetes Grid documentation.
VMware Telco Cloud Service Assurance does not supoort TLS 1.3 for Tanzu Kubernetes Grid version 2.5, but by default Tanzu Kubernetes Grid 2.5 uses TLS 1.3. In this case, run the following command to set TLS version to 1.2, while creating TKG 2.5 Workload cluster.
```
export APISERVER_EXTRA_ARGS="tls-min-version=VersionTLS12"
```
Post the deployment of VMware Tanzu Kubernetes Grid workload cluster, export the kubeconfig file of the Workload cluster and then copy it to the deployment host. For more information, see Obtaining KUBECONFIG File from TKG Workload Cluster.
Verify that you have VMware Tanzu Kubernetes Grid workload cluster with available vsphere-sc storage class. For example, VMware vSAN.
Note: When creating a workload cluster, ensure that you refer the VMware Telco Cloud Service Assurance Sizing Sheet for calculating the number of VMs for production deployment and refer the System Requirements for Demo Footprint for demo deployment.
Kubernetes workload cluster virtual IP must be noted post deployment of workload cluster. Use the virtual IP when updating values-user-overrides.yaml file.
The recommended registry for VMware Tanzu Kubernetes Grid is Harbor. The OCI 1.1.0 complaint registry recommends to use Harbor 2.9.4 version. Ensure that you deploy Harbor and you have access permissions to it.

Increase KAPP Controller Resources

After creating the management cluster and workload cluster, you can perform the following steps to increase KAPP Controller resources.

Export the Kubeconfig file of the Management Cluster:
```
export KUBECONFIG=<<KUBECONFIG file location of Management Cluster>>
```
Note: Ensure that you use the KUBECONFIG file of TKG management cluster. TKG management kubeconfig file ( ~/.kube-tkg/config) can be found in the VM through, which TKG management cluster is deployed.
Set CLUSTER_NAME to the name of the workload cluster.
```
export CLUSTER_NAME=<your workload cluster name>
```

Pause the reconciliation of the kapp-controller application on the workload cluster.

kubectl patch packageinstall ${CLUSTER_NAME}-kapp-controller --type "json" -p '[{"op":"add","path":"/spec/paused","value": true }], {"op":"add","path":"/spec/canceled","value": true }]'

Run the following command to patch the kapp-controller's resource allocation.

export KUBECONFIG=<KUBECONFIG file location of Workload Cluster>
kubectl set resources deployment kapp-controller --limits memory=6Gi,cpu=4,ephemeralstorage=4Gi --requests memory=100Mi,cpu=120m,ephemeral-storage=256Mi -n tkg-system