Deployment Configuration for Production Footprint

Configure the
values.yaml
file for production footprint 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
    Use the same Harbor IP which was used during Native Kubernetes deployment.
  • Set the footprint value to
    production
    .
    # (string) footprint is the number of devices monitored by TCSA. # allowed values for footprint "production" footprint: production
  • For
    dashboardAccess
    , set the
    ip
    to the selected static IP address and
    type
    as Loadbalancer. The free Static IP must 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
    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. The free Static IP should be in the same subnet as that of the management IP's of the Cluster Nodes.
    edgeServicesAccessIp: <static-IPAddress2-for-edgeservice>
  • 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
For flexible deployment of VMware Telco Cloud Service Assurance based on the number of Metrics, Events, Devices, Enrichment, Alarm, Anomaly, and Retention Interval, update the values for all the flexible configuration parameters in the
values.yaml
file.
  • Set the value for
    incomingMetrics
    parameter.
    # Configure the flexible configuration for different parameters flexibleConfig: # 'incomingMetrics' is to represent the number of Metrics that TCSA should scale to , and it is represented in units of Millions. incomingMetrics: Example flexibleConfig: # The following example is for 10 million metrics incomingMetrics: 10
  • Set the value for
    incomingEvents
    and
    managedDevices
    parameters.
    # Configure the flexible configuration for different parameters flexibleConfig: # 'incomingEvents' is to represent the number of events that TCSA should scale to , and it is mentioned in units of Thousands. incomingEvents: # 'managedDevices' is to represent the number of devices that TCSA should scale to, and it is mentioned in units of Thousands. managedDevices: Example # The following example is for 250K events and 20k devices. incomingEvents: 250 managedDevices: 20
    The number of Events cannot be less than the number of Devices multiplied by 10.
  • Set the value for
    percentMetricsForAlarms
    parameter.
    # Configure the flexible configuration for different parameters flexibleConfig # The parameter ‘% number of metrics for alarms’ it is a one-to-one mapping, which means, the value given for this parameter can be directly taken as the total percentage of the ‘unique metrics’ to calculate Alarm definitions for the resource allocation. percentMetricsForAlarms: Example flexibleConfig percentMetricsForAlarms: 2
  • Set the value for
    percentMetricsForAnomaly
    parameter.
    # Configure the flexible configuration for different parameters flexibleConfig # The parameter ‘% number of metrics for alarms’ it is a one-to-one mapping, which means, the value given for this parameter can be directly taken as the total percentage of the ‘unique metrics’ to calculate Alarm definitions for the resource allocation. percentMetricsForAnomaly: Example flexibleConfig percentMetricsForAnomaly: 2
  • Set the value for
    retentionInterval
    parameter to the desired retention interval period.
    # Configure the flexible configuration for different parameters flexibleConfig retentionInterval:
    By default, the retention interval is 1w. The retention interval values can be 1w, 2w, and so on.
To enable the backup and restore with VMware vSAN storage, see Enabling VMware vSAN File Services. To configure and update the parameters in the
values.yaml
file during deployment, see Customizing Backup and Restore Configurations topic.