Need for consistency in metadata reported about backed up volumes

[gsadhani]

Describe the problem/challenge you have

For PVs backed up by Restic, Velero has the following data in PodVolumeBackup CRD:

1. Pod name
2. Pod namespace
3. Persistent Volume Name

For PVs backed up using CSI snapshots, Velero has the following data in the backup location which can be retrieved using CSIBackupVolumeSnapshots DownloadRequest, the data stored is raw content of VolumeSnapshot CRD :

1. Persistent Volume Claim Name
2. Volume Snapshot Class Name
3. Restore Size

There is a need for consistency in reporting data about backed up volumes.

Describe the solution you'd like A easier and generic way to retrieve metadata of backed up PVs, backed using Restic/Kopia or using CSI snapshotting.

Environment:

• Velero version (use velero version): 1.9.6
• Kubernetes version (use kubectl version): 1.24
• Kubernetes installer & version: NA
• Cloud provider or hardware configuration: NA
• OS (e.g. from /etc/os-release):NA

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• :+1: for "The project would be better with this feature added"
• :-1: for "This feature will not enhance the project in a meaningful way"

[reasonerjt]

@gsadhani

Due to historical reasons and some CRDs are not controlled by velero like Volumesnapshot, it may be not realistic to have a unified format.

Let me do some investigation and get back to you for more discussion.

[reasonerjt]

Clarified with Rahul and Astha the consumer should unify different data objects.