The installation of the Prometheus add-on is currently stalled in TCA version 3.x

Products

• VMware Telco Cloud Automation

Issue/Introduction

The installation of the Prometheus add-on in TCA version 3.x within the TKG cluster encountered problems, specifically becoming stuck. Initial investigations indicated that permission issues were logged in the CSI Controller. This document outlines the cause of the issue and the steps taken to resolve it.

 

 

Cause

The permission issues were linked to insufficient privileges assigned to the existing role for the vSphere CSI (Container Storage Interface). The required privileges for successful installation were not fully configured, which prevented the proper functioning of the Prometheus add-on.

 

 

Resolution

The following privileges were recommended to be checked for the vSphere CSI role:

• • Host > Configuration > Storage partition configuration
  • Virtual machine > Change Configuration > Add existing disk
  • Virtual Machine > Change Configuration > Add or remove device
  • CNS > Searchable
  • Note: VM storage policies > View VM storage policies is necessary only if a storage class is configured with a storage policy.

1. Propagation of Permissions: Ensure that the Global Permissions for vSphere CSI have the "Propagate to children" option checked.
2. Action Taken: The user was advised to recreate the Persistent Volume Claim (PVC) and Pod, specifically by deleting and re-adding the Prometheus add-on.
3. Outcome: The installation issue was resolved, and the user confirmed successful installation without the "View VM storage policies" privilege, as it was not required for their configuration in vCenter 7.

This document serves to assist teams in troubleshooting similar issues in the future and emphasizes the importance of proper role configurations for successful add-on installations.