You must perform the following steps to access the VMware Telco Cloud Service Assurance UI and Grafana Dashboard using Fully Qualified Domain Name (FQDN).
Procedure
- Update the
dashboardAccess.ip
in/tcx-deployer/product-helm-charts/tcsa/values-user-overrides.yaml.yaml
with the FQDN that you want to use to access the VMware Telco Cloud Service Assurance UI and Grafana Dashboard.Example: appDeploymentInterval: 2s 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: <your FQDN> # (string) Can be either NodePort or LoadBalancer. Defaults to NodePort for TKG and LoadBalancer for Azure/AWS. For on-prem it can be either. type: <NodePort or LoadBalancer>
- Run
tcxctl deploy product tcsa
for the changes to take place.export TCSA_WORK_SPACE=/root/base cd $TCSA_WORK_SPACE ./tcxctl deploy product --name tcsa --kubeconfig <KUBECONFIG> --registry-password <REGISTRY PASSWORD> --registry-username <REGISTRY USERNAME> --timeout=5 --path $TCSA_WORK_SPACE/tcx-deployer/product-helm-charts/tcsa
Note:- The
--registry-cert
is an optional parameter. If you are using a self-signed certificate Harbor, you must pass a certificate path value to it. - Ensure that the
--registry-password
is passed inside single quotation if you are passing this to the installation script.
The VMware Telco Cloud Service AssuranceUI becomes accessible with the FQDN. - The
- Run the following command to check the
root_url
ingrafana-ini
config map to check that the Grafafana pads have restarted.kubectl get cm grafana-ini -n tcsa-system -o yaml apiVersion: v1 data: grafana.ini: | [server] protocol = http http_port = 3000 domain = localhost root_url = https://<FQDN>:443/adhoc/ ----> Should point to the FQDN now instead of the IP
- Access the Grafana Dashboard using the FQDN.