Ensure object creation does not exceed Kubernetes maximum name length

[msfrucht]

Describe the problem/challenge you have

Some of the existing Velero functionality such as BackupRepository creation relies on concatenating based on keys that use the names of other objects.

This can cause object creation to fail with name length exceeding 254 or 64 characters depending on the object type.

Kubernetes names should never use other object names as substrings without verification of valid name length and a fallback to handle the excessive length.

Describe the solution you'd like

1. Remove object names being used as substrings to other object names.

Or

2. Ensure the object name length will be valid in a consistent manner. Consistent may require different mechanisms depending on object type and context rather than across all of Velero.

Anything else you would like to add:

Known objects affected:

BackupRepository (includes name of BackupStorageLocation)
DataUpload (includes name of Backup)
DataDownload (includes name of Restore)

Environment:

• Velero version (use velero version): 1.15

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.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

[msfrucht]

Updated issue definition to include addition objects found to also be created by concatenating other object names.

DataUpload (includes name of Backup)
DataDownload (includes name of Restore)

[kaovilai]

Since no assignee, moving to 1.19