This section provides instructions to trigger the deployment of VMware Telco Cloud Service Assurance on VMware Tanzu Kubernetes Grid using the tcxctl
CLI.
Note: If you do not want to specify the registry username and password in the installation script, perform Docker login. To login to Docker, run the following command:
docker login <harbor-fqdn>
Ensure that the --registry-password
does not have the comma character in it. If the comma is used, escape it using the backslash.
Trigger deployment using
tcxctl
CLI.
root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/clis root [ ~/base/tcx-deployer/clis ]# ./tcxctl deploy all --bundle-path <$TCSA_WORK_SPACE>/tcx-deployer --kubeconfig <your-kubeconfig-location> --registry <harbor-registry-fqdn>/<project-name> --registry-password <harbor-registry-password> --registry-username <harbor-registry-username> --timeout <time-in-mins>
Note:
- The
--registry-cert
is an optional parameter. If you are using a private certification-based Harbor, you must pass a certificate path value to it. - The
<project-name>
specified in the registry URL will be autoatically created with the same name in Harbor registry during deployment.
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 OR root [ ~/base/tcx-deployer/scripts ]# kubectl get apps
For all the apps, the reconciliation status must be successful.
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct NAME STATUS READY MESSAGE AGE tcsa updateCompleted True All App CRs reconciled successfully 30h
Note: After successful deployment, you can launch the VMware Telco Cloud Service Assurance UI. For more information, see
Accessing VMware Telco Cloud Service Assurance UI topic.
If all the apps are not reconciled, the deployment fails. For more information, see VMware Telco Cloud Automation Installation Issue in the VMware Telco Cloud Service Assurance Troubleshooting Guide.