ingress: virtual_host_fqdn: "grafana.corinternal.com"
It was when I tried to install the Grafana package with that values file that I encountered the following error:
$ tanzu package install grafana -p grafana.tanzu.vmware.com -v 7.5.7+vmware.1-tkg.1 --values-file grafana.yaml - Installing package 'grafana.tanzu.vmware.com' | Getting namespace 'default' | Getting package metadata for 'grafana.tanzu.vmware.com' | Creating service account 'grafana-default-sa' | Creating cluster admin role 'grafana-default-cluster-role' | Creating cluster role binding 'grafana-default-cluster-rolebinding' | Creating secret 'grafana-default-values' - Creating package resource / Package install status: Reconciling Please consider using 'tanzu package installed update' to update the installed package with correct settings Error: package reconciliation failed: kapp: Error: Ownership errors: - Resource 'namespace/tanzu-system-monitoring (v1) cluster' is already associated with a different app 'prometheus-ctrl' namespace: default (label 'kapp.k14s.io/app=1632306561798628761') Usage: tanzu package install INSTALLED_PACKAGE_NAME --package-name PACKAGE_NAME --version VERSION [flags]
namespace: tanzu-system-dashboard ingress: virtual_host_fqdn: "grafana.corinternal.com"
$ tanzu package install grafana -p grafana.tanzu.vmware.com -v 7.5.7+vmware.1-tkg.1 --values-file grafana.yaml - Installing package 'grafana.tanzu.vmware.com' | Getting namespace 'default' | Getting package metadata for 'grafana.tanzu.vmware.com' | Creating service account 'grafana-default-sa' | Creating cluster admin role 'grafana-default-cluster-role' | Creating cluster role binding 'grafana-default-cluster-rolebinding' | Creating secret 'grafana-default-values' - Creating package resource | Package install status: Reconciling Added installed package 'grafana' in namespace 'default' $ kubectl get pods -A | grep grafana tanzu-system-dashboard grafana-857cb96d5-hvjqv 2/2 Running 0 5m40s $ kubectl get svc -A | grep grafana tanzu-system-dashboard grafana LoadBalancer 100.67.2.164 XX.XX.13.199 80:32313/TCP 5m48s
And now if you connect to one of the available Grafana dashboards, it should be possible to see the Prometheus metrics scraped from the cluster displayed in the dashboard. This is because a Prometheus data source (taken from the Prometheus package) gets automatically added to this Grafana configuration. Note that there are two Grafana dashboards automatically included in the package.