Velero Status Shows Unhealthy in TCA Due to Missing backup-driver or datamgr-for-vsphere-plugin

Products

• VMware Telco Cloud Automation

Issue/Introduction

In VMware Telco Cloud Automation (TCA), the Velero component may be reported as "Unhealthy" or in a failure state by the tca-monitor-operator.

This occurs even if Velero was not deployed as a standard TCA add-on.

Symptoms:

• The tca-monitor-operator reports a status failure for Velero.

• Velero core functionality may appear operational, but the TCA dashboard reflects an unhealthy state.

• Specific deployments or daemonsets expected by the monitor are missing from the cluster.

Environment

3.4

Cause

The tca-monitor-operator is hard-coded to verify the presence and "Running" status of four specific components once a Velero installation is detected. If any of these are missing, the operator triggers an unhealthy status. The required components are:

1. velero (Deployment)

2. node-agent (DaemonSet)

3. backup-driver (Deployment)

4. datamgr-for-vsphere-plugin (DaemonSet)

In this scenario, the "Unhealthy" state is caused by the absence of the backup-driver and the datamgr-for-vsphere-plugin, which were not included in the customer's specific Velero deployment.

Resolution

To resolve the unhealthy status and ensure full compatibility with the TCA monitoring stack, it is recommended to deploy Velero as an official TCA Add-on.