Both monitoring extensions, Prometheus and Grafana, require persistent storage. To prepare for deploying these extensions, verify that the target Tanzu Kubernetes cluster is configured with a default storage class and that the vSphere Namespace has sufficient storage.

Persistent Storage Requirements for the TKG Extensions

The Tanzu Kubernetes cluster where you deploy the Prometheus or Grafana extensions should be provisioned with a default storage class. See Examples for Provisioning Tanzu Kubernetes Clusters Using the Tanzu Kubernetes Grid Service v1alpha1 API.

Alternatively, you can configure the extensions to use a persistent volume claim when you deploy them. The configuration for this approach is provided as part of the deployment instructions for each extension.

The storage limit for the vSphere Namespace where the cluster is provisioned on which you are installing the extension must be larger than the total persistent volume claim size.
Table 1. Default Storage Requirements for the TKG Extensions
Component TKG Extension Default Storage Size
Grafana Grafana 8 Gi
Prometheus Server Prometheus 8 Gi
Alert Manager Prometheus 8 Gi
Harbor Harbor Registry Varies by PVC

Adjust the vSphere Namespace Storage Limit

To adjust the storage limit for the vSphere Namespace where the Tanzu Kubernetes cluster is provisioned:
  1. Using the vSphere Client, log in to the vCenter Server where vSphere with Tanzu is enabled.
  2. Select the vSphere Namespace where the target Tanzu Kubernetes cluster is provisioned.
  3. Select Configure > Resource Limits .
  4. Click Edit.
  5. Adjust the Storage limit so that it is larger than the total size of the persistent volume claims required for the Prometheus and Grafana extensions.