Configure the values.yaml file available in $TCSA_WORK_SPACE/tcx-deployer/product-helm-charts/tcsa.

root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/product-helm-charts/tcsa
root [ ~ /upgrade/tcx-deployer/product-helm-charts/tcsa ]# vi values.yaml
Update the required parameters in the values.yaml file.
  • Use the same registryRootUrl as the previously deployed VMware Telco Cloud Service Assurance version.
    # Default values for tcsa.
    # This is a YAML-formatted file.
    # Customize your TCSA deployment here by configuring the parameters that are exposed.
    # Uncomment the relevant lines and configure them according to your environment.
    .
    .
    # (string) registryRootUrl is the FQDN of the registry that has the artifacts.
    registryRootUrl: <harbor-registry-fqdn>/<project-name>
  • Use the same footprint size as the previously deployed VMware Telco Cloud Service Assurance version.
    # (string) footprint is the number of devices monitored by TCSA.
    # allowed values for footprint "demo", "25k", "50k", "75k", "100k", "125k", "150k", "175k", "200k"
    footprint: <Footprint-of-previuosly-deployed-version>
  • Set the dashboardStaticAccessIp and edgeServicesAccessIp parameters to the IP address of the previously deployed VMware Telco Cloud Service Assurance version.
    # (string) Set dashboardStaticAccessIp to the IP address used to access the TCSA dashboard. Leave empty or commented out for EKS private network deployments.
    dashboardStaticAccessIp: <ClusterIP-of-the-previously-deployed-version>
    
    # (string) Set edgeServicesAccessIp to the IP address to be used to access kafka-edge. Leave empty for EKS public networks.
    edgeServicesAccessIp: <ClusterIP-of-the-previously-deployed-version>
  • Set privateNetwork to false.
    # ----IaaS configuration----
    # (bool) privateNetwork indicates if TCSA is being deployed on a private EKS or AKS network
    privateNetwork: false
  • Set cloud provider as tkg for deploying VMware Telco Cloud Service Assurance on TKG.
    # (string) cloud indicates the cloud/K8s provider. Valid values are "tkg", "aws", "azure" and "on-prem"
    cloud: tkg
  • Use the same retention interval as the previously deployed VMware Telco Cloud Service Assurance version.
    elasticsearch:
      retentionInterval: <retention-interval-previously-deployed>
  • All the Backup and Restore values must be same as specified during the previous VMware Telco Cloud Service Assurance deployment.