This section provides instructions to trigger the deployment of VMware Telco Cloud Service Assurance on VMware Tanzu Kubernetes Grid using the installation script.

This is an optional parameter that is required to be set based on the harbor version as specified in the following link.

For Self-signed certificates for Harbor, follow the below procedure:
  • Copy the Harbor Certs file in /etc/ssl/certs directory.
  • If you do not have permission to the directory /etc/ssl/certs, then put the Harbor Cert in any other location where you have access, and run the below command:
    trust anchor <path-to-cert>
    • If trust command is not available, then install p11-kit-trust package which contains trust command.
Note: If you do not want to specify the registry user name and password in the installation script, perform Docker login. To login to Docker, run the following command: 
docker login <harbor-fqdn> --compat-auth-file=/root/.docker/config.json
Trigger deployment using the installation script 
export TCSA_WORK_SPACE=/root/base
root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/scripts
root [ ~/base/tcx-deployer/scripts ]# ./installTCSA.sh --kubeconfig <your-kubeconfig-location> --registry <harbor-registry-fqdn>/<project-name> --registry-password <harbor-registry-password> --registry-username <harbor-registry-username> --timeout <timeout in minute>
Note:
  • The --registry-cert is an optional parameter. If you are using a self-signed certificate Harbor, you must pass a certificate path value to it.
  • Ensure that the --registry-password is passed inside single quotation if you are passing this to the installation script.
  • The <project-name> specified in the registry URL will be automatically created with the same name in Harbor registry during deployment.
  • You can specify 90 minutes for the timeout value. If there is any latency in the network, you can increase this value.
After the deployment script exits, manually check the VMware Telco Cloud Service Assurance deployment status by running the following command from deployment VM. 
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct -A
 OR
root [ ~/base/tcx-deployer/scripts ]# kubectl get apps -A
For all the apps, the reconciliation status must be successful. 
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct -A
NAME                        STATUS            READY   MESSAGE                               AGE
tcsa                        updateCompleted   True    All App CRs reconciled successfully   12h
tps-tcx-platform-services   updateCompleted   True    All App CRs reconciled successfully   13h
Note: After successful deployment, you can launch the VMware Telco Cloud Service Assurance UI. For more information, see Accessing UI topic.
If all the apps are not reconciled, the deployment fails. For more information, see VMware Telco Cloud Service Assurance Installation Issues in the VMware Telco Cloud Service Assurance Troubleshooting Guide.
Note: If the user wants to enable the Grafana Schedule and Export Reports post the deployment, then follow the procedure mentioned in the Optional feature : Enabling Grafana Schedule and Export Reports Feature section.