Deployment Configuration for Demo Footrpint with VMware vSAN or Block Storage

Configure the values.yaml file for Demo footprint with VMware vSAN or Block Storage available in $TCSA_WORK_SPACE/tcx-deployer/product-helm-charts/tcsa directory.

Update the required parameters in the values.yaml file.

Set the registry URL.

root [ ~ ]# cd tcx-deployer/product-helm-charts/tcsa
root [ ~/tcx-deployer/product-helm-charts/tcsa ]# vi values.yaml

# 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: <HarborIP>/tcx

Note: Use the same Harbor IP which was used during Native Kubernetes deployment.

Set the footprint value to demo.

# (string) footprint is the number of devices monitored by TCSA.
# allowed values for footprint "demo"
footprint: demo

For dashboardAccess, set the ip to the selected static IP address and type as Loadbalancer.
Note: The free Static IP should be in the same subnet as that of the management IP's of the cluster Nodes.
```
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: <static-IPAddress1-for-loadbalancer>
  # (string) LoadBalancer for on-prem.
  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.
Set edgeServicesAccessIp parameter to the available free static IP address.
```
edgeServicesAccessIp: <static-IPAddress2-for-edgeservice>
```
Note: The free Static IP must be in the same subnet as that of the management IP's of the cluster Nodes.

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 on-prem for deploying VMware Telco Cloud Service Assurance on Native Kubernetes.

# (string) cloud indicates the cloud/K8s provider. Valid values are "tkg", "aws", "azure" and "on-prem"
cloud: on-prem

Set localStorageHostPath parameter to the value "<storage_dir>/kubernetes/persistent_volumes. The <storage_dir> value should be same as that specified in vars.yaml during the Kubernetes deployment.

Note: For Demo Footprint, the Flexible configuration parameters in the values.yaml file should not be updated. Flexible Scaling is not supported as part of Demo Footprint.