Deployment Configuration for Azure

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 [ ~/base/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.

Set ACR registry URL.

# 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

Set the desired footprint value.

# (string) footprint is the number of devices monitored by TCSA.
# allowed values for footprint "demo", "25k", "50k", "75k", "100k", "125k", "150k", "175k", "200k"
footprint:

Set dashboardStaticAccessIp with the IP address of your cluster and edgeServicesAccessIp parameter with the IP address used to access 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>

# (string) Set edgeServicesAccessIp to the IP address to be used to access kafka-edge. Leave empty for EKS public networks.
edgeServicesAccessIp: <IPAddress2>

# (string) Set dashboardDynamicAccessIp to the external IP assigned dynamically by the cloud provider to istio-ingressgateway service in istio-ingressgateway namespace.
dashboardDynamicAccessIp: null

Note: Configure dashboardStaticAccessIp with hostname/FQDN if you want to access the VMware Telco Cloud Service Assurance using hostname/FQDN instead of the IP address.

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
```
- For Kubenet network plugin, IPAddress1 and IPAddress2 must be specified in the values.yaml file.
  IPAddress1 is a public IP and must be created in the same region and resource group where AKS cluster is created. IPAddress1 is the IP address VMware Telco Cloud Service Assurance and IPAddress2 is the IP address of Edge Kafka.
  1. If using Azure CNI plugin, IPAddress1 and IPAddress2 must be set to empty.
  2. If using Kubenet plugin, IPAddress1 and IPAddress2 must be set to valid IP address as follows:
    - For the public networks get Azure public IPs using the az CLI. For more information, see Azure Network Public IP.
    - For the private network, get IP addresses from the subnet used for the AKS cluster private network. You can use the az CLI to list free IP addresses in a subnet. For more information, see Azure Network VNet.
      - Set privateNetwork: to true.
If you want to update the metrics retention interval period during deployment, see Configure Metrics Retention Interval Period topic.

Note: If you want to configure backup and restore with AWS S3 or vSAN storage, then update the parameters accordingly in values.yaml file during deployment. For more information, see Customizing Backup and Restore Configurations topic.