diff --git a/site/_data/master-toc.yml b/site/_data/master-toc.yml index eea1bbf49..e5d69d0b0 100644 --- a/site/_data/master-toc.yml +++ b/site/_data/master-toc.yml @@ -13,9 +13,7 @@ toc: subfolderitems: - page: Overview url: /install-overview - - page: Upgrade to 1.0 - url: /upgrade-to-1.0 - - page: Quick Start with In-Cluster Minio + - page: Quick start with in-cluster MinIO url: /get-started - page: Run on AWS url: /aws-config @@ -23,14 +21,18 @@ toc: url: /azure-config - page: Run on GCP url: /gcp-config - - page: Restic Setup + - page: Restic setup url: /restic - title: Use subfolderitems: - - page: Disaster Recovery + - page: Disaster recovery url: /disaster-case - page: Cluster migration url: /migration-case + - page: Backup reference + url: /backup-reference + - page: Restore reference + url: /restore-reference - title: Troubleshoot subfolderitems: - page: Troubleshooting @@ -41,7 +43,7 @@ toc: url: /debugging-restores - page: Troubleshoot Restic url: /restic#troubleshooting - - title: Customize Velero + - title: Customize subfolderitems: - page: Build from source url: /build-from-source diff --git a/site/_includes/version-warning.html b/site/_includes/version-warning.html index fa89a0cfb..63e9f5e88 100644 --- a/site/_includes/version-warning.html +++ b/site/_includes/version-warning.html @@ -22,11 +22,5 @@ For up-to-date documentation, see the latest version.

{% endif %} -

- - Heptio Ark is now Velero! v0.11 is our first release with the new name. For instructions on - migrating your Ark deployments and data to Velero, please see the Upgrade section in the latest version. - For more details on the renaming, please read our blog post. -

{% endif %} diff --git a/site/docs/master/backup-reference.md b/site/docs/master/backup-reference.md new file mode 100644 index 000000000..797230d67 --- /dev/null +++ b/site/docs/master/backup-reference.md @@ -0,0 +1,9 @@ +# Backup Reference + +## Exclude Specific Items from Backup + +It is possible to exclude individual items from being backed up, even if they match the resource/namespace/label selectors defined in the backup spec. To do this, label the item as follows: + +```bash +kubectl label -n / velero.io/exclude-from-backup=true +``` diff --git a/site/docs/master/restore-reference.md b/site/docs/master/restore-reference.md new file mode 100644 index 000000000..8cbc43eea --- /dev/null +++ b/site/docs/master/restore-reference.md @@ -0,0 +1,41 @@ +# Restore Reference + +## Restoring Into a Different Namespace + +Velero can restore resources into a different namespace than the one they were backed up from. To do this, use the `--namespace-mappings` flag: + +```bash +velero restore create RESTORE_NAME \ + --from-backup BACKUP_NAME \ + --namespace-mappings old-ns-1:new-ns-1,old-ns-2:new-ns-2 +``` + +## Changing PV/PVC Storage Classes + +Velero can change the storage class of persistent volumes and persistent volume claims during restores. To configure a storage class mapping, create a config map in the Velero namespace like the following: + +```yaml +apiVersion: v1 +kind: ConfigMap +metadata: + # any name can be used; Velero uses the labels (below) + # to identify it rather than the name + name: change-storage-class-config + # must be in the velero namespace + namespace: velero + # the below labels should be used verbatim in your + # ConfigMap. + labels: + # this value-less label identifies the ConfigMap as + # config for a plugin (i.e. the built-in change storage + # class restore item action plugin) + velero.io/plugin-config: "" + # this label identifies the name and kind of plugin + # that this ConfigMap is for. + velero.io/change-storage-class: RestoreItemAction +data: + # add 1+ key-value pairs here, where the key is the old + # storage class name and the value is the new storage + # class name. + : +```