Procedure to Redeploy If The Harbor Credentials are Changed

You must redeploy VMware Telco Cloud Service Assurance if the harbor credentials are changed for the VMware Telco Cloud Service Assurance applications to run without failing. You must perform the following procedure to redeploy VMware Telco Cloud Service Assurance if the harbor credentials are changed.

Note: If you are not redeploying VMware Telco Cloud Service Assurance after the harbor credentials are changed then the VMware Telco Cloud Service Assurance will fail.

Procedure

1. Create new user in the Harbor registry with permission equivalent as Admin role.
2. Run docker logout harbor_ip in the Deployer Host.
3. Run docker login harbor_ip --compat-auth-file=/root/.docker/config.json with the new credentials in the Deployer Host.
4. Execute the following command

   root [ ~/base/tcx-deployer/clis]# ./tcxctl deploy app --name tcx-bootstrap --kubeconfig <Kubeconfig file path> --registry <Registry_Url> --tag-file ../scripts/imgpkg_tags.yaml 
   

   For example

   root [ ~/base/tcx-deployer/clis]# ./tcxctl deploy app --name tcx-bootstrap --kubeconfig /root/.kube/autoworkloadharbor --registry vmw-bng-127-86-008.eng.vmware.com/autoworkloadharbor --tag-file ../scripts/imgpkg_tags.yaml -u admin1 -p VMware123
   

   Note: The --registry-cert is an optional parameter. If you are using a self-signed certificate Harbor or VM based deployment, you must pass a certificate path value to it.
5. Check if all the applications are reconciled successfully by using kubectl get apps -A.