cluster-reaper-service in the VMSP prelude namespace will show logs such as:2026-04-13T19:16:08.307069085Z stdout F {""component"":""reaper-job"",""level"":""error"",""msg"":""PollService: failed, service=data-protection, job=Cluster Job rid=(rid:c:ef1a360d-####-####-####-99837aa3c484:<cluster>-6w5yf:<cluster>-00), uid=(c:01KN7#################), force=true, step=PollServices, error=rpc error: code = Unavailable desc = connection error: desc = \""transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-13T19:15:00Z is after 2026-01-06T15:12:05Z\"""",""request-id"":""ef72c5af-####-####-####-1d4af36de18a"",""time"":""2026-04-13T19:16:08Z"",""trace-id"":""4b8cecbb-####-####-####-31b74e71d52d""}"
This issue occurs as the dataprotection-server does not automatically restart following a certificate rotation.
It continues to present the old certificate causing other services to fail to connect.
To resolve the certificate issue, you will need to restart the dataprotection-server deployment on the VCF Automation (VCFA) Node.
vmware-system-user and provide the password for the account.sudo -iexport KUBECONFIG=/etc/kubernetes/admin.confkubectl rollout restart deployment -n prelude dataprotection-server