4fc1c70028
* Ensure PVs and PVCs remain bound when doing a restore (#3007) * Only remove the UID from a PV's claimRef The UID is the only part of a claimRef that might prevent it from being rebound correctly on a restore. The namespace and name within the claimRef should be preserved in order to ensure that the PV is claimed by the correct PVC on restore. Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Remap PVs claimRef.namespace on relevant restores When remapping namespaces, any included PVs need to have their claimRef updated to point remapped namespaces to the new namespace name in order to be bound to the correct PVC. Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Update tests and ensure claimRef namespace remaps Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Remove lowercased uid field from unstructured PV Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Fix issues that prevented PVs from being restored Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Add changelog Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Dynamically reprovision volumes without snapshots Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Update test for lower case uid field Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Remove stray debugging print statement Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Fix typo, remove extra code, add tests. Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * fix: rename the PV if VolumeSnapshotter has modified the PV name (#2835) When VolumeSnapshotter sets the PV name via SetVolumeID and PV is not there in the cluster, velero does not rename the PV. Which causes the pvc to be in the lost state as pvc points to the old PV but pv object has been renamed by VolumeSnapshotter. Signed-off-by: Pawan <pawan@mayadata.io> * adding a test case for pv rename Signed-off-by: Pawan <pawan@mayadata.io> Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * restore proper lowercase/plural CRD resource (#2949) * restore proper lowercase/plural CRD resource This commit restores the proper resource string "customresourcedefinitions" for CRD. The prior change to "CustomResourceDefinition" was made because this was being used in another place to populate the CRD "Kind" field in remap_crd_version_action.go -- there, just use the correct Kind string instead of pulling from Resource. Signed-off-by: Scott Seago <sseago@redhat.com> * add changelog Signed-off-by: Scott Seago <sseago@redhat.com> * Update changelogs for v1.4.3 Signed-off-by: Nolan Brubaker <brubakern@vmware.com> Co-authored-by: Pawan Prakash Sharma <pawanprakash101@gmail.com> Co-authored-by: Scott Seago <sseago@redhat.com> |
||
|---|---|---|
| .github | ||
| changelogs | ||
| cmd | ||
| design | ||
| examples | ||
| hack | ||
| pkg | ||
| site | ||
| third_party/kubernetes/pkg/kubectl/cmd | ||
| .gitignore | ||
| .goreleaser.yml | ||
| ADOPTERS.md | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile-velero | ||
| Dockerfile-velero-arm | ||
| Dockerfile-velero-arm64 | ||
| Dockerfile-velero-ppc64le | ||
| Dockerfile-velero-restic-restore-helper | ||
| Dockerfile-velero-restic-restore-helper-arm | ||
| Dockerfile-velero-restic-restore-helper-arm64 | ||
| Dockerfile-velero-restic-restore-helper-ppc64le | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SUPPORT.md | ||
| go.mod | ||
| go.sum | ||
| netlify.toml | ||
README.md
Overview
Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. You can run Velero with a public cloud platform or on-premises. Velero lets you:
- Take backups of your cluster and restore in case of loss.
- Migrate cluster resources to other clusters.
- Replicate your production cluster to development and testing clusters.
Velero consists of:
- A server that runs on your cluster
- A command-line client that runs locally
Documentation
The documentation provides a getting started guide and information about building from source, architecture, extending Velero, and more.
Please use the version selector at the top of the site to ensure you are using the appropriate documentation for your version of Velero.
Troubleshooting
If you encounter issues, review the troubleshooting docs, file an issue, or talk to us on the #velero channel on the Kubernetes Slack server.
Contributing
If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our Start contributing documentation for guidance on how to setup Velero for development.
Changelog
See the list of releases to find out about feature changes.