Deployment Configuration for Azure

For AKS configuration, use the deploy.settings file available in the $TCSA_WORK_SPACE/tcx-deployer/scripts/deployment/ directory.

To upgrade to the latest version, use the <config> of the previously deployed VMware Telco Cloud Service Assurance version.

# ========== General configuration ========== #
# Mandatory: Path to the <config> of the Kubernetes cluster inside the deployment container (for example: /root/.kube/<config>
KUBECONFIG=

Update the VMware Telco Cloud Service Assurance details and deployment timeout period. Use the same footprint size as the previously deployed VMware Telco Cloud Service Assurance version.

# ========== Product details  ========== #
# Name of the product to be deployed/installed
PRODUCT=tcsa
# Product helm config

# allowed values for footprint "demo", "25k", "50k", "75k", "100k", "125k", "150k", "175k", "200k"
FOOTPRINT=
# Time to wait for the deployment to complete, in seconds. Maximum timeout is 3600 seconds. 
# For deployment above 50K footprint, specify the deployment timeout value in seconds to a higher value.
PRODUCT_DEPLOYMENT_TIMEOUT=1800

# ========== Deployment Location ========== #
# LOCATION can be "on-prem", "aws", "tkg", or "azure"
LOCATION=azure

# ========= Deployment modes and actions ========== #
# Options are "init", "deploy-all", "deploy-apps" or "cleanup"
DEPLOYMENT_ACTION="deploy-all"
## Set this to '--force' if you want to cleanup by force without waiting for user confirmation
DELETE_ARGS=

For the ACR registry URL, use the format as <your-acr-instance>.azurecr.io/tcx. URL must be given without https or http and must end with /tcx.
Note: Ensure that you obtain the registry details such as URL, username, and password from the ACR registry section in Azure website.
```
# ========== Registry details ========== #
# These are mandatory parameters
# Note: The "/tcx" suffix is mandatory
REGISTRY_URL=<your-acr-instance>.azurecr.io/tcx
REGISTRY_USERNAME=<ACR registry username>
REGISTRY_PASSWORD=<ACR registry password>
```
If you are using docker login <harbor-registry-fqdn> command, then you do not have to update <REGISTRY_USERNAME> and <REGISTRY_PASSWORD> in deploy.settings file. For more information, see Prerequisites for Setting up Deployment Container.
Update the following parameters in the values-user-overrides.yaml which is available in the <TCSA_WORK_SPACE>/product-helm-chart/tcsa directory. Uncomment and update the parameters in the file.
```
ingressHostname:
  product: <IPAddress1-Previously-deployed>
  edgeServices: <IPAddress2-Previously-deployed>
  
grafana:
 accessIp: <IPAddress1>

# AKS configuration
aks:
  resourceGroup: <resource-group-name>

privateNetwork: true
```
For Kubenet network plugin IPAddress1 and IPAddress2 must be specified in the values-user-overrides.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 of the previously deployed VMware Telco Cloud Service Assurance IP and IPAddress2 is the IP address of the previously deployed Kafka Edge service.
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 addresses 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 deploy on vSAN without any other storage available for AWS S3 compatible storage, you must deploy MinIO. For more information, see Customizing Backup and Restore Configurations topic.