euclidsun
commented
2 years ago Many users are using Velero as the generic BR solution for k8s, and expecting it could just work as charming. However, the reality is, k8s could be very complicated in many ways, there are some B/R use cases could not be supported well by velero today.
current we have some doc describe the limitations, for example: https://velero.io/docs/v1.9/restic/#limitations
but it is only for restic, there are some common cases which are identified velero BR procedure could not support, thus we'd better to have documentation to list those scenarios.
Proposal: Add one "Limitation" document under the "Troubleshoot" section.
We could category the known limitation as below:
- B/R in the same cluster
- B/R in different clusters
- Apps and 3rd party controllers
For each item, we could add something like:
- description of the limitation
- description of the reason
for example, for this one https://github.com/vmware-tanzu/velero/issues/1929, we could add below:
- velero can not restore the certificates signed by k8s CA into another cluster. -- the k8s CA is different on cluster basis, the certificates won't work after restored in a new cluster.
Describe the problem/challenge you have [A description of the current limitation/problem/challenge that you are experiencing.] it is common asked questions that if velero has any limitations, including use cases, resources type, workload type, etc.
Describe the solution you'd like [A clear and concise description of what you want to happen.] Add one section in the velero documentation to list these limitations. for example:
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
velero version):kubectl version):/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.