You can deploy the patch by using the CLI or the VMware Telco Cloud Automation UI.

Deploy the Patch Bundle on your Cluster Using the CLI

  1. Login to the Deployment Host and create a directory called Patch under /root directory.
  2. Download the patch bundle in the Deployment Host under the /root/patch directory.
  3. Extract the downloaded bundle and installer. For procedure, see Extract the Downloaded Package and Installer topic.
  4. Navigate to the deployment directory where the patch was extracted.

    /root/patch/tcx-deployer/scripts/deployment/

    The deploy.settings file in the Patch must be updated with the values from the deploy.settings file which was used to deploy the Base GA build.

  5. Download and launch the Deployment Container. For procedure, see Download and Launch the Deployment Container section.
    Note: Ensure that you set $TCSA_WORK_SPACE=/root/patch.
  6. Run ./tcx_app_deployment.sh from the Deployment Container.
    Manually check the VMware Telco Cloud Service Assurance Patch deployment status using the following command:
    root [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct
    Alternatively, you can run the following command to check the Patch deployment status:
    root [ ~/tcx-deployer/scripts ]# kubectl get apps

    For all the apps, the reconcilation status must be successful.

  7. To verify if the correct image is selected, run the following command:
    kubectl describe app <app name>
    The image parameter and image tag must point to the patched imgpkg bundles with their corresponding tags.
Note: After the patch is deployed, you can view the patch versions in the About page of VMware Telco Cloud Service Assurance UI.

Deploy the Patch Bundle on your Cluster Using the VMware Telco Cloud Automation UI

To deploy the patch using the VMware Telco Cloud Automation UI, perform the following steps:
  1. Download the patch bundle in the Deployment Host under the /root/patch directory.
  2. Extract the downloaded bundle and installer. For procedure, see Extract the Downloaded Package and Installer topic.
  3. Download and launch the Deployment Container. For procedure, see Download and Launch the Deployment Container section.
    Note: Ensure that you set $TCSA_WORK_SPACE=/root/patch.
  4. Run the scripts to push artifacts to registry. For more information, see Push Artifacts to Registry.
  5. Run the merge-product-yaml-files.sh script as described in step 1.c for generating merged_yamls.yaml file required for patch deployment and copy the resulting merged_yamls.yaml file to your local machine.
    Note: Retain the same footprint value used during initial deployment.
  6. Update the values for the parameters in the merged_yamls.yaml which is generated in Step 5 as shown in the following screenshot:

    Set them to the same values used during initial VMware Telco Cloud Service Assurance deployment.

    1. ingressHostname.product=<LoadBalancerIP>
    2. registryRootUrl=<your-registry-url/your-project-name/tcx>
    3. Update the statusChecker.enabled parameter. The default value is true. Set the value as false.
    4. Update the retentionInterval value with the same value used during initial CNF instantiation.
    5. Update the additionalValuesFile parameter in the merged_yamls.yaml file based on the retention interval value. For more information on updating retention interval values, see Configure Deploy.Settings File for Retention Period of Metrics. The following screenshot is an example of a 2.5 K footprint.

    6. Update the following parameters in the merged_yamls.yaml file to the required footprint.
      • footprint
      • helmOverride.productInfo.footPrint
      Note: Based on the footprint size of deployment, update the value for footprint.
  7. If deploying MinIO as a gateway, or if you want to use AWS storage for backup and restore, update the accessKey, secretKey, and backupBucketName parameters in the merged_yamls.yaml file as shown in the following screenshot:

  8. Launch the VMware Telco Cloud Automation and navigate to Catalog > Inventory > Network Function.
  9. Click TCSA CNF and select Reconfigure.
  10. Upload the updated merged_yamls.yaml file which is generated in Step 5 in VMware Telco Cloud Automation UI.
  11. Click Next > Finish.
Manually check the VMware Telco Cloud Service Assurance patch rollback status by running the following command from deployment VM:
root [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct 
 OR
root [ ~/tcx-deployer/scripts ]# kubectl get apps

For all the apps, the reconcilation status must be successful.

Note: After the patch is deployed, you can view the patch versions in the About page of VMware Telco Cloud Service Assurance UI.