Deployment Configuration for VMware Tanzu Kubernetes Grid

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.

• Set Harbor 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: <harbor-registry-fqdn>/<project-name>

• 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 the dashboardStaticAccessIp and edgeServicesAccessIp parameters to the IP address of your cluster.

  # (string) Set dashboardStaticAccessIp to the IP address used to access the TCSA dashboard. Leave empty or commented out for EKS private network deployments.
  dashboardStaticAccessIp: <ClusterIP>
  
  # (string) Set edgeServicesAccessIp to the IP address to be used to access kafka-edge. Leave empty for EKS public networks.
  edgeServicesAccessIp: <ClusterIP>

  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 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 tkg for deploying VMware Telco Cloud Service Assurance on TKG.

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

• Backup and Restore parameters are optional and must be configured only in-case if you are using external AWS or vSAN file services for Backup and Restore operations.
  If AWS is used for backup, then update the following parameters:

  minioDatastoreType=s3
  bucketName : Userdefined name, where the backup will be stored in AWS environment.
  accesskey : accesskey and secretkey are specific to the individual AWS account. 
  secretkey : accesskey and secretkey are specific to the individual AWS account. 

  If VMware vSAN file service is used for backup, then update the following parameters:

  minioDatastoreType=nas 
  nfsProvisionerEnabled: true 
  nfsPath : nfspath where the backup will be stored. 
  nfsServer : nfs-server on which backup will be stored. 
  bucketName :Userdefined name, where the backup will be stored in VSAN file services. 

  For more information on configuring VMware vSAN file services, see Enabling VMware vSAN File Services topic.

• If you want to update the metrics retention interval period during deployment, see Configure Metrics Retention Interval Period topic.