Configuration for Demo Footprint

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 footprint value.
```
# (string) footprint is the number of devices monitored by TCSA.
footprint: demo
```
Note: The Demo configuration does not support the flexibleConfig parameter.

For dashboardAccess, set the ip with the static IP address of your cluster and type as LoadBalancer.

dashboardAccess:
  # (string) The IP address for accessing the dashboard. If using a static pre-allocated IP, set this property on Day 0 (fresh deployment). If using a dynamically allocated IP, set this on Day 1 (post deployment)
  ip: <IPAddress1>
  # Can be either NodePort or LoadBalancer. Defaults to NodePort for TKG and LoadBalancer for Azure/AWS. 
  type: LoadBalancer

Note: Configure dashboardAccess with hostname/FQDN if you want to access the VMware Telco Cloud Service Assurance using hostname/FQDN instead of the IP address. For procedure, refer VMware Telco Cloud Service Assurance UI Access Using FQDN.

Set edgeServicesAccessIp parameter with the IP address used to access Edge Kafka.

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

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.

Trigger deployment. For more information, see Trigger Deployment Using the tcxctl CLI