766ab5d3ee
* Account for possible missing schemas on v1 CRDs If a v1beta1 CRD without a Schema was submitted to a Kubernets v1.16 cluster, then Kubernetes will server it back as a v1 CRD without a schema. However, when Velero tries to restore this document, the request will be rejected as a v1 CRD must have a schema. This commit has some defensive coding on the restore side, as well as potential fixes on the backup side for getting around this. Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Back up nonstructural CRDs as v1beta1 Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Add tests for remapping plugin Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Add builders for v1 CRDs Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Address review feedback Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Remove extraneous log message Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Add changelog Signed-off-by: Nolan Brubaker <brubakern@vmware.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| server | ||
| util | ||
| velero | ||
| errors.go | ||