Remove the necessity of object storage as primary backup location

[rahulgit1988]

Describe the problem/challenge you have
Nowadays, object storage solution is very pupular and common in OSS forums.
I think that is the reasone Velero backup supports only object storage as backup location.
But for users on-premises or private enviorment, object storage is not very common soultion. and that is the major problem/limitation of Velero.

Describe the solution you'd like

• A Object Storage(for example: MINIO) as cache ==> pod solution "Velero" with "MINIO" as side car in the containerized cluster enviorment.
• Download objects from "Object storage cache" and save them as file in Pod's PV, which is backup with snapshot or safer separated storage in user's enviorment.

Anything else you would like to add:
Here we can automate the process of downloading the object from Cache to File storage.

Environment:
Openshift Enviorment, K8S Enviorment

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

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"

[nrb]

Closing this as a duplicate of #1229