For AKS configuration, use the values.yaml file available in the $TCSA_WORK_SPACE/tcx-deployer/product-helm-charts/tcsa directory.
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.
Note: Ensure that you obtain the ACR registry details such as URL, username, and password from the ACR registry section in Azure website.
- Use the same registryRoolUrl 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: <your-acr-instance>.azurecr.io/tcx
- 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-previously-deployed>
- Set dashboardStaticAccessIp with the IP address of the previously deployed VMware Telco Cloud Service Assurance version and edgeServicesAccessIp with the previous IP address of Edge Kafka.
# (string) Set dashboardStaticAccessIp to the IP address used to access the TCSA dashboard. Leave empty or commented out for EKS private network deployments. dashboardStaticAccessIp: <IPAddress1-previously-deployed> # (string) Set edgeServicesAccessIp to the IP address to be used to access kafka-edge. Leave empty for EKS public networks. edgeServicesAccessIp: <IPAddress2-previously-deployed>
- Set resourceGroup to the name of the Azure resource group.
# (map) aks holds AKS specific configuration aks: # (string) resourceGroup is the name of the Azure resource group. resourceGroup:
- Set privateNetwork to true.
# ----IaaS configuration---- # (bool) privateNetwork indicates if TCSA is being deployed on a private EKS or AKS network privateNetwork: true
- Set cloud provider as azure for deploying VMware Telco Cloud Service Assurance on Azure.
# (string) cloud indicates the cloud/K8s provider. Valid values are "tkg", "aws", "azure" and "on-prem" cloud: azure
- 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.