diff --git a/changelogs/unreleased/9844-Copilot b/changelogs/unreleased/9844-Copilot new file mode 100644 index 000000000..222faed8a --- /dev/null +++ b/changelogs/unreleased/9844-Copilot @@ -0,0 +1 @@ +Replace vmware-tanzu/velero GitHub org references with velero-io/velero (#9844) diff --git a/site/README-HUGO.md b/site/README-HUGO.md index d384a57f3..3b6154be2 100644 --- a/site/README-HUGO.md +++ b/site/README-HUGO.md @@ -14,7 +14,7 @@ If you are running a build on Ubuntu you will need the following packages: # Local Development -1. Clone down your own fork, or clone the main repo `git clone https://github.com/vmware-tanzu/velero` and add your own remote. +1. Clone down your own fork, or clone the main repo `git clone https://github.com/velero-io/velero` and add your own remote. 1. `cd velero/site` 1. Serve the site and watch for markup/sass changes `hugo serve`. 1. View your website at http://127.0.0.1:1313/ diff --git a/site/content/_index.md b/site/content/_index.md index fc131c1ce..5d34a41a3 100644 --- a/site/content/_index.md +++ b/site/content/_index.md @@ -13,7 +13,7 @@ hero: url: /blog/Velero-1.11/ cta_link2: text: Download Velero - url: https://github.com/vmware-tanzu/velero/releases/latest + url: https://github.com/velero-io/velero/releases/latest promo1: icon: /img/disaster-recover-icon.svg title: Disaster Recovery @@ -33,6 +33,6 @@ secondary_ctas: content: Learn about Velero and how to protect your Kubernetes resources and volumes. cta2: title: How Do You Use Velero? - url: https://github.com/vmware-tanzu/velero/issues/1327 + url: https://github.com/velero-io/velero/issues/1327 content: See how Velero is helping others and tell the world how you use Velero. --- \ No newline at end of file diff --git a/site/content/community/_index.md b/site/content/community/_index.md index 70e31c869..41755f9db 100644 --- a/site/content/community/_index.md +++ b/site/content/community/_index.md @@ -5,11 +5,11 @@ id: community --- ## Do you want to help build Velero? -If you’re a newcomer, check out the “[Good first issue](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22)” and “[Help wanted](https://github.com/vmware-tanzu/velero/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+)” labels in the Velero repository. +If you’re a newcomer, check out the “[Good first issue](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22)” and “[Help wanted](https://github.com/velero-io/velero/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+)” labels in the Velero repository. If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our [Start contributing](https://velero.io/docs/main/start-contributing/) documentation for guidance on how to setup Velero for development. -You can follow the work we do, see our milestones, and our backlog on our [GitHub project boards](https://github.com/vmware-tanzu/velero/projects). +You can follow the work we do, see our milestones, and our backlog on our [GitHub project boards](https://github.com/velero-io/velero/projects). * Follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero) * Join our Kubernetes Slack channel and talk to over 800 other community members: [#velero-users](https://kubernetes.slack.com/messages/velero-users) @@ -19,4 +19,4 @@ Bi-weekly community meeting alternating every week between Beijing Friendly tim * US/Europe friendly - we start at 10am ET(bound to ET) / 7am PT / 3pm CET / 10pm(11pm) CST - [Convert to your time zone](https://dateful.com/convert/est-edt-eastern-time?t=10) - [Google meet link](https://meet.google.com/dyr-djtj-sko) * Read and comment on the [meeting notes](https://hackmd.io/fCDVjqGuTG23CoOWQpoEVg) * See previous community meetings on our [YouTube Channel](https://www.youtube.com/playlist?list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM) -* Have a question to discuss in the community meeting? Please add it to our [Q&A Discussion board](https://github.com/vmware-tanzu/velero/discussions/categories/community-support-q-a) +* Have a question to discuss in the community meeting? Please add it to our [Q&A Discussion board](https://github.com/velero-io/velero/discussions/categories/community-support-q-a) diff --git a/site/content/docs/main/_index.md b/site/content/docs/main/_index.md index 87c43588e..46ea37f6e 100644 --- a/site/content/docs/main/_index.md +++ b/site/content/docs/main/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/main/backup-hooks.md b/site/content/docs/main/backup-hooks.md index a3b50e892..5f43926c2 100644 --- a/site/content/docs/main/backup-hooks.md +++ b/site/content/docs/main/backup-hooks.md @@ -123,4 +123,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/main/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/main/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/main/backup-reference.md b/site/content/docs/main/backup-reference.md index 220d97acc..f2045211f 100644 --- a/site/content/docs/main/backup-reference.md +++ b/site/content/docs/main/backup-reference.md @@ -106,7 +106,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/main/basic-install.md b/site/content/docs/main/basic-install.md index 018fea341..32c58a5c2 100644 --- a/site/content/docs/main/basic-install.md +++ b/site/content/docs/main/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation, ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -65,7 +65,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/main/build-from-source.md b/site/content/docs/main/build-from-source.md index 5f617c8ae..72f1e9098 100644 --- a/site/content/docs/main/build-from-source.md +++ b/site/content/docs/main/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -193,6 +193,6 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx diff --git a/site/content/docs/main/code-standards.md b/site/content/docs/main/code-standards.md index a8edd49ff..07988fa9f 100644 --- a/site/content/docs/main/code-standards.md +++ b/site/content/docs/main/code-standards.md @@ -82,15 +82,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/main/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/main/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/main/contributions/ibm-config.md b/site/content/docs/main/contributions/ibm-config.md index 464f53c82..a34fe3625 100644 --- a/site/content/docs/main/contributions/ibm-config.md +++ b/site/content/docs/main/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/main/contributions/minio.md b/site/content/docs/main/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/main/contributions/minio.md +++ b/site/content/docs/main/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/main/contributions/oracle-config.md b/site/content/docs/main/contributions/oracle-config.md index eeaca1c66..2a41ebfb8 100644 --- a/site/content/docs/main/contributions/oracle-config.md +++ b/site/content/docs/main/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/main/csi-snapshot-data-movement.md b/site/content/docs/main/csi-snapshot-data-movement.md index cde862209..154abb198 100644 --- a/site/content/docs/main/csi-snapshot-data-movement.md +++ b/site/content/docs/main/csi-snapshot-data-movement.md @@ -67,7 +67,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -406,7 +406,7 @@ The `RestorePVC` serves as an intermediate Persistent Volume Claim (PVC) utilize Sometimes, `RestorePVC` needs to be configured to increase the performance of restore operations. [This document][19] outlines advanced configuration options for `RestorePVC`, allowing users to fine-tune access modes and storage class settings based on their storage provider's capabilities. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ @@ -422,7 +422,7 @@ Sometimes, `RestorePVC` needs to be configured to increase the performance of re [15]: data-movement-node-selection.md [16]: data-movement-backup-pvc-configuration.md [17]: backup-repository-configuration.md -[18]: https://github.com/vmware-tanzu/velero/pull/7576 +[18]: https://github.com/velero-io/velero/pull/7576 [19]: data-movement-restore-pvc-configuration.md [20]: node-agent-prepare-queue-length.md [21]: data-movement-cache-volume.md diff --git a/site/content/docs/main/csi.md b/site/content/docs/main/csi.md index 53843841d..fddc5f258 100644 --- a/site/content/docs/main/csi.md +++ b/site/content/docs/main/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -130,7 +130,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/main/custom-plugins.md b/site/content/docs/main/custom-plugins.md index 8e3cf3f37..b0881d579 100644 --- a/site/content/docs/main/custom-plugins.md +++ b/site/content/docs/main/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -117,5 +117,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/main/pkg/plugin/logger.go diff --git a/site/content/docs/main/customize-installation.md b/site/content/docs/main/customize-installation.md index 7774565f1..e42d6a3f8 100644 --- a/site/content/docs/main/customize-installation.md +++ b/site/content/docs/main/customize-installation.md @@ -523,16 +523,16 @@ The new workflow is: ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/main/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/main/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/main/data-movement-node-selection.md b/site/content/docs/main/data-movement-node-selection.md index f25b02ff9..9efd1ca94 100644 --- a/site/content/docs/main/data-movement-node-selection.md +++ b/site/content/docs/main/data-movement-node-selection.md @@ -199,7 +199,7 @@ The other VGDP instances will run on nodes, which instance type is `Standard_B4m } ``` -Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/vmware-tanzu/velero/pull/7982). +Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/velero-io/velero/pull/7982). In this example, if the backup target PVC's StorageClass is `kibishii-storage-class`, its backupPVC should use StorageClass `worker-storagepolicy`. Because the final StorageClass is `worker-storagepolicy`, the backupPod uses the loadAffinity specified by `loadAffinity`'s elements with `StorageClass` field set to `worker-storagepolicy`. backupPod will be assigned to nodes, which instance type is `Standard_B2ms`. diff --git a/site/content/docs/main/data-movement-pod-resource-configuration.md b/site/content/docs/main/data-movement-pod-resource-configuration.md index a90217ea8..303e3ddcf 100644 --- a/site/content/docs/main/data-movement-pod-resource-configuration.md +++ b/site/content/docs/main/data-movement-pod-resource-configuration.md @@ -121,7 +121,7 @@ kubectl create cm node-agent-config -n velero --from-file=node-agent-config.json ### Pod Labels Add customized labels for data mover pods to support third-party integrations and environment-specific requirements. -If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). +If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). If `podLabels` is not configured, Velero uses the in-tree third-party labels for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. @@ -142,7 +142,7 @@ The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVo ### Pod Annotations Add customized annotations for data mover pods to support third-party integrations and pod-level configuration. -If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). +If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). If `podAnnotations` is not configured, Velero uses the in-tree third-party annotations for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. diff --git a/site/content/docs/main/examples.md b/site/content/docs/main/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/main/examples.md +++ b/site/content/docs/main/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/main/file-system-backup.md b/site/content/docs/main/file-system-backup.md index d78368da3..853ee715e 100644 --- a/site/content/docs/main/file-system-backup.md +++ b/site/content/docs/main/file-system-backup.md @@ -539,7 +539,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -745,7 +745,7 @@ Velero still effectively manage restic repository, though you cannot write any n [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-file-system-backup -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher @@ -758,7 +758,7 @@ Velero still effectively manage restic repository, though you cannot write any n [14]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/ [15]: customize-installation.md#customize-resource-requests-and-limits [16]: performance-guidance.md -[17]: https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy +[17]: https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#deprecation-policy [18]: backup-repository-configuration.md [19]: node-agent-concurrency.md [20]: node-agent-prepare-queue-length.md diff --git a/site/content/docs/main/image-tagging.md b/site/content/docs/main/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/main/image-tagging.md +++ b/site/content/docs/main/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/main/locations.md b/site/content/docs/main/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/main/locations.md +++ b/site/content/docs/main/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/main/maintainers.md b/site/content/docs/main/maintainers.md index 579fb3109..0165f7d64 100644 --- a/site/content/docs/main/maintainers.md +++ b/site/content/docs/main/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/main/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/main/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/main/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/main/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/main/migration-case.md b/site/content/docs/main/migration-case.md index fee41b1ea..ff15e4186 100644 --- a/site/content/docs/main/migration-case.md +++ b/site/content/docs/main/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/main/overview-plugins.md b/site/content/docs/main/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/main/overview-plugins.md +++ b/site/content/docs/main/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/main/plugin-release-instructions.md b/site/content/docs/main/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/main/plugin-release-instructions.md +++ b/site/content/docs/main/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/main/release-instructions.md b/site/content/docs/main/release-instructions.md index 5ed47e3c4..1d82c70dd 100644 --- a/site/content/docs/main/release-instructions.md +++ b/site/content/docs/main/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/main/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/main/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/main/repository-maintenance.md b/site/content/docs/main/repository-maintenance.md index e6a45920f..7aa07e940 100644 --- a/site/content/docs/main/repository-maintenance.md +++ b/site/content/docs/main/repository-maintenance.md @@ -200,5 +200,5 @@ Note that priority class configuration is only read from the global configuratio [1]: velero-install.md#usage [2]: node-agent-concurrency.md [3]: backup-repository-configuration.md#full-maintenance-interval-customization -[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 -[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 +[4]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 +[5]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 diff --git a/site/content/docs/main/restore-reference.md b/site/content/docs/main/restore-reference.md index 6c5394cf0..b14a1dac9 100644 --- a/site/content/docs/main/restore-reference.md +++ b/site/content/docs/main/restore-reference.md @@ -217,7 +217,7 @@ data: Velero removes PVC's `volume.kubernetes.io/selected-node` annotation during restore, so that the restored PVC could be provisioned appropriately according to ```WaitForFirstConsumer``` rules, storage topologies and the restored pod's schedule result, etc. -For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/vmware-tanzu/velero/issues/9053. +For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/velero-io/velero/issues/9053. ## Restoring into a different namespace diff --git a/site/content/docs/main/self-signed-certificates.md b/site/content/docs/main/self-signed-certificates.md index 6d9af90c1..e1ef5728b 100644 --- a/site/content/docs/main/self-signed-certificates.md +++ b/site/content/docs/main/self-signed-certificates.md @@ -144,7 +144,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/main/start-contributing.md b/site/content/docs/main/start-contributing.md index a421e1dfd..c9536ec12 100644 --- a/site/content/docs/main/start-contributing.md +++ b/site/content/docs/main/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/main/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/main/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/main/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/main/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/main/support-process.md b/site/content/docs/main/support-process.md index 51cdc492c..d142329f8 100644 --- a/site/content/docs/main/support-process.md +++ b/site/content/docs/main/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/main/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/main/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/main/supported-configmaps/node-agent-configmap.md b/site/content/docs/main/supported-configmaps/node-agent-configmap.md index 1953d34d9..fc90d4436 100644 --- a/site/content/docs/main/supported-configmaps/node-agent-configmap.md +++ b/site/content/docs/main/supported-configmaps/node-agent-configmap.md @@ -432,7 +432,7 @@ For detailed information, see [Cache PVC Configuration for Data Movement Restore Add customized labels for data mover pods to support third-party integrations and environment-specific requirements. -If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). +If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). If `podLabels` is not configured, Velero uses the in-tree third-party labels for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. @@ -465,7 +465,7 @@ The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVo Add customized annotations for data mover pods to support third-party integrations and pod-level configuration. -If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). +If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). If `podAnnotations` is not configured, Velero uses the in-tree third-party annotations for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. diff --git a/site/content/docs/main/supported-providers.md b/site/content/docs/main/supported-providers.md index 11ea60a15..b71571017 100644 --- a/site/content/docs/main/supported-providers.md +++ b/site/content/docs/main/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/main/tilt.md b/site/content/docs/main/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/main/tilt.md +++ b/site/content/docs/main/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/main/troubleshooting.md b/site/content/docs/main/troubleshooting.md index e61eb0d7e..dc692771c 100644 --- a/site/content/docs/main/troubleshooting.md +++ b/site/content/docs/main/troubleshooting.md @@ -235,12 +235,12 @@ If the ownership conflict error(`maintenance must be run by designated user`) al Velero doesn't handle the conflict by design. To resolve it, please use Kopia maintenance CLI to set the ownership correctly, e.g. `kopia maintenance set --owner=default@default`. -Please refer to [Issue 9007](https://github.com/vmware-tanzu/velero/issues/9007) for more information. +Please refer to [Issue 9007](https://github.com/velero-io/velero/issues/9007) for more information. [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/main/upgrade-to-1.18.md b/site/content/docs/main/upgrade-to-1.18.md index 0bf839fe3..ba830680e 100644 --- a/site/content/docs/main/upgrade-to-1.18.md +++ b/site/content/docs/main/upgrade-to-1.18.md @@ -20,7 +20,7 @@ If you're not yet running at least Velero v1.17, see the following: - [Upgrading to v1.16][9] - [Upgrading to v1.17][10] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.0.0/_index.md b/site/content/docs/v1.0.0/_index.md index a07247a06..ed15c26b1 100644 --- a/site/content/docs/v1.0.0/_index.md +++ b/site/content/docs/v1.0.0/_index.md @@ -57,14 +57,14 @@ Feedback and discussion are available on [the mailing list][24]. See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[5]: https://github.com/vmware-tanzu/velero/blob/main/CONTRIBUTING.md -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[5]: https://github.com/velero-io/velero/blob/main/CONTRIBUTING.md +[6]: https://github.com/velero-io/velero/releases -[8]: https://github.com/vmware-tanzu/velero/blob/main/CODE_OF_CONDUCT.md +[8]: https://github.com/velero-io/velero/blob/main/CODE_OF_CONDUCT.md [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos [11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1 diff --git a/site/content/docs/v1.0.0/aws-config.md b/site/content/docs/v1.0.0/aws-config.md index dd19327d5..8ca983466 100644 --- a/site/content/docs/v1.0.0/aws-config.md +++ b/site/content/docs/v1.0.0/aws-config.md @@ -14,9 +14,9 @@ If you do not have the `aws` CLI locally installed, follow the [user guide][5] t ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.0.0/azure-config.md b/site/content/docs/v1.0.0/azure-config.md index dd7e0c941..cb907d1ae 100644 --- a/site/content/docs/v1.0.0/azure-config.md +++ b/site/content/docs/v1.0.0/azure-config.md @@ -25,9 +25,9 @@ consider using Premium Managed Disks, which are SSD backed. ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.0.0/build-from-source.md b/site/content/docs/v1.0.0/build-from-source.md index 0b1d12c9f..2692ce8de 100644 --- a/site/content/docs/v1.0.0/build-from-source.md +++ b/site/content/docs/v1.0.0/build-from-source.md @@ -24,7 +24,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -32,7 +32,7 @@ Where `go` is your [import path][4] for Go. For Go development, it is recommended to add the Go import path (`$HOME/go` in this example) to your path. ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -235,13 +235,13 @@ If you need to add or update the vendored dependencies, see [Vendoring dependenc [3]: #build [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[6]: https://github.com/vmware-tanzu/velero/tree/main/examples +[6]: https://github.com/velero-io/velero/tree/main/examples [7]: #run [8]: config-definition.md [10]: #vendoring-dependencies [11]: vendoring-dependencies.md [12]: #test -[13]: https://github.com/vmware-tanzu/velero/blob/main/hack/generate-proto.sh +[13]: https://github.com/velero-io/velero/blob/main/hack/generate-proto.sh [14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3 [15]: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#the-shared-credentials-file [16]: https://cloud.google.com/docs/authentication/getting-started#setting_the_environment_variable @@ -250,4 +250,4 @@ If you need to add or update the vendored dependencies, see [Vendoring dependenc [19]: ../examples/README.md [20]: api-types/backupstoragelocation.md [21]: api-types/volumesnapshotlocation.md -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.0.0/faq.md b/site/content/docs/v1.0.0/faq.md index bd201ba8a..68dcf7b00 100644 --- a/site/content/docs/v1.0.0/faq.md +++ b/site/content/docs/v1.0.0/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/main/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.0.0/gcp-config.md b/site/content/docs/v1.0.0/gcp-config.md index 8ad68409d..d36844695 100644 --- a/site/content/docs/v1.0.0/gcp-config.md +++ b/site/content/docs/v1.0.0/gcp-config.md @@ -12,9 +12,9 @@ If you do not have the `gcloud` and `gsutil` CLIs locally installed, follow the ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.0.0/get-started.md b/site/content/docs/v1.0.0/get-started.md index 81eaabf7d..4acb2b4fe 100644 --- a/site/content/docs/v1.0.0/get-started.md +++ b/site/content/docs/v1.0.0/get-started.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -268,6 +268,6 @@ In this case: [3]: install-overview.md [17]: restic.md [18]: debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [31]: #expose-minio-outside-your-cluster diff --git a/site/content/docs/v1.0.0/hooks.md b/site/content/docs/v1.0.0/hooks.md index 02b33313e..34aa1c6a3 100644 --- a/site/content/docs/v1.0.0/hooks.md +++ b/site/content/docs/v1.0.0/hooks.md @@ -80,5 +80,5 @@ velero backup logs nginx-hook-test | grep hookCommand [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.0.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.0.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.0.0/ibm-config.md b/site/content/docs/v1.0.0/ibm-config.md index 389f1defe..5f3c6521c 100644 --- a/site/content/docs/v1.0.0/ibm-config.md +++ b/site/content/docs/v1.0.0/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.0.0/image-tagging.md b/site/content/docs/v1.0.0/image-tagging.md index 6e2468031..84c4fd666 100644 --- a/site/content/docs/v1.0.0/image-tagging.md +++ b/site/content/docs/v1.0.0/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `gcr.io/heptio-images/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `gcr.io/heptio-images/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `gcr.io/heptio-images/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.0.0/migrating-to-velero.md b/site/content/docs/v1.0.0/migrating-to-velero.md index 1fbff6c72..58dc187fe 100644 --- a/site/content/docs/v1.0.0/migrating-to-velero.md +++ b/site/content/docs/v1.0.0/migrating-to-velero.md @@ -39,7 +39,7 @@ kubectl scale --namespace heptio-ark deployment/ark --replicas 0 ARCH="amd64" # Download the velero client/example tarball to and unpack -curl -L https://github.com/vmware-tanzu/velero/releases/download/v0.11.0/velero-v0.11.0-${OS}-${ARCH}.tar.gz --output velero-v0.11.0-${OS}-${ARCH}.tar.gz +curl -L https://github.com/velero-io/velero/releases/download/v0.11.0/velero-v0.11.0-${OS}-${ARCH}.tar.gz --output velero-v0.11.0-${OS}-${ARCH}.tar.gz tar xvf velero-v0.11.0-${OS}-${ARCH}.tar.gz # Create the prerequisite CRDs and namespace diff --git a/site/content/docs/v1.0.0/oracle-config.md b/site/content/docs/v1.0.0/oracle-config.md index aed44a41b..38ac02651 100644 --- a/site/content/docs/v1.0.0/oracle-config.md +++ b/site/content/docs/v1.0.0/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.0.0/plugins.md b/site/content/docs/v1.0.0/plugins.md index 0005bff8e..51f5104be 100644 --- a/site/content/docs/v1.0.0/plugins.md +++ b/site/content/docs/v1.0.0/plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -80,6 +80,6 @@ Then, in your plugin's implementation, you can read this ConfigMap to fetch the for an example of this -- in particular, the `getPluginConfig(...)` function. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/main/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/main/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.0.0/restic.md b/site/content/docs/v1.0.0/restic.md index 00b012624..8c1cdae14 100644 --- a/site/content/docs/v1.0.0/restic.md +++ b/site/content/docs/v1.0.0/restic.md @@ -330,7 +330,7 @@ on to running other init containers/the main containers. [1]: https://github.com/restic/restic [2]: install-overview.md -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.0.0/support-matrix.md b/site/content/docs/v1.0.0/support-matrix.md index 3ef327d52..02bd09717 100644 --- a/site/content/docs/v1.0.0/support-matrix.md +++ b/site/content/docs/v1.0.0/support-matrix.md @@ -60,10 +60,10 @@ After you publish your plugin, open a PR that adds your plugin to the appropriat [5]: ibm-config.md [6]: https://docs.portworx.com/scheduler/kubernetes/ark.html [7]: https://github.com/StackPointCloud/ark-plugin-digitalocean -[8]: https://github.com/vmware-tanzu/velero-plugin-example/ +[8]: https://github.com/velero-io/velero-plugin-example/ [9]: get-started.md [10]: https://kubernetes.slack.com/messages/velero -[11]: https://github.com/vmware-tanzu/velero/issues +[11]: https://github.com/velero-io/velero/issues [12]: https://github.com/aws/aws-sdk-go [13]: https://portworx.slack.com/messages/px-k8s [14]: https://github.com/portworx/ark-plugin/issues diff --git a/site/content/docs/v1.0.0/troubleshooting.md b/site/content/docs/v1.0.0/troubleshooting.md index 132506863..a1d1ac5f7 100644 --- a/site/content/docs/v1.0.0/troubleshooting.md +++ b/site/content/docs/v1.0.0/troubleshooting.md @@ -73,6 +73,6 @@ Backups in the `InProgress` phase have not uploaded any files to object storage. [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [25]: https://kubernetes.slack.com/messages/velero diff --git a/site/content/docs/v1.0.0/upgrade-to-1.0.md b/site/content/docs/v1.0.0/upgrade-to-1.0.md index b796904c1..676430a67 100644 --- a/site/content/docs/v1.0.0/upgrade-to-1.0.md +++ b/site/content/docs/v1.0.0/upgrade-to-1.0.md @@ -143,5 +143,5 @@ _*backups created prior to v0.10 stored snapshot metadata in the `status.volumeB ``` [0]: https://velero.io/docs/v0.11.0/migrating-to-velero -[1]: https://github.com/vmware-tanzu/velero/releases/tag/v0.11.1 -[2]: https://github.com/vmware-tanzu/velero/releases/tag/v1.0.0 +[1]: https://github.com/velero-io/velero/releases/tag/v0.11.1 +[2]: https://github.com/velero-io/velero/releases/tag/v1.0.0 diff --git a/site/content/docs/v1.1.0/_index.md b/site/content/docs/v1.1.0/_index.md index 4b96e5a00..c57db724c 100644 --- a/site/content/docs/v1.1.0/_index.md +++ b/site/content/docs/v1.1.0/_index.md @@ -45,11 +45,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.1.0/aws-config.md b/site/content/docs/v1.1.0/aws-config.md index 3ab0c82f5..5ca308c8d 100644 --- a/site/content/docs/v1.1.0/aws-config.md +++ b/site/content/docs/v1.1.0/aws-config.md @@ -14,9 +14,9 @@ If you do not have the `aws` CLI locally installed, follow the [user guide][5] t ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.1.0/azure-config.md b/site/content/docs/v1.1.0/azure-config.md index 831244975..379b14b79 100644 --- a/site/content/docs/v1.1.0/azure-config.md +++ b/site/content/docs/v1.1.0/azure-config.md @@ -25,9 +25,9 @@ consider using Premium Managed Disks, which are SSD backed. ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.1.0/build-from-source.md b/site/content/docs/v1.1.0/build-from-source.md index a259eca4b..fec6f1a48 100644 --- a/site/content/docs/v1.1.0/build-from-source.md +++ b/site/content/docs/v1.1.0/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -100,4 +100,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.1.0/development.md b/site/content/docs/v1.1.0/development.md index 86fec9ba8..a572340c4 100644 --- a/site/content/docs/v1.1.0/development.md +++ b/site/content/docs/v1.1.0/development.md @@ -34,5 +34,5 @@ To run unit tests, use `make test`. If you need to add or update the vendored dependencies, see [Vendoring dependencies][11]. [11]: vendoring-dependencies.md -[13]: https://github.com/vmware-tanzu/velero/blob/main/hack/generate-proto.sh +[13]: https://github.com/velero-io/velero/blob/main/hack/generate-proto.sh [14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3 diff --git a/site/content/docs/v1.1.0/faq.md b/site/content/docs/v1.1.0/faq.md index 104872c05..f7faf077f 100644 --- a/site/content/docs/v1.1.0/faq.md +++ b/site/content/docs/v1.1.0/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.1.0/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/v1.1.0/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.1.0/gcp-config.md b/site/content/docs/v1.1.0/gcp-config.md index 7c373b2a4..5ba9536c0 100644 --- a/site/content/docs/v1.1.0/gcp-config.md +++ b/site/content/docs/v1.1.0/gcp-config.md @@ -12,9 +12,9 @@ If you do not have the `gcloud` and `gsutil` CLIs locally installed, follow the ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.1.0/get-started.md b/site/content/docs/v1.1.0/get-started.md index 81eaabf7d..4acb2b4fe 100644 --- a/site/content/docs/v1.1.0/get-started.md +++ b/site/content/docs/v1.1.0/get-started.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -268,6 +268,6 @@ In this case: [3]: install-overview.md [17]: restic.md [18]: debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [31]: #expose-minio-outside-your-cluster diff --git a/site/content/docs/v1.1.0/hooks.md b/site/content/docs/v1.1.0/hooks.md index 2d0e83ade..02473c938 100644 --- a/site/content/docs/v1.1.0/hooks.md +++ b/site/content/docs/v1.1.0/hooks.md @@ -80,5 +80,5 @@ velero backup logs nginx-hook-test | grep hookCommand [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.1.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.1.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.1.0/ibm-config.md b/site/content/docs/v1.1.0/ibm-config.md index 0fdd3a3b4..71692af3a 100644 --- a/site/content/docs/v1.1.0/ibm-config.md +++ b/site/content/docs/v1.1.0/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.1.0/image-tagging.md b/site/content/docs/v1.1.0/image-tagging.md index 6e2468031..84c4fd666 100644 --- a/site/content/docs/v1.1.0/image-tagging.md +++ b/site/content/docs/v1.1.0/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `gcr.io/heptio-images/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `gcr.io/heptio-images/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `gcr.io/heptio-images/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.1.0/migrating-to-velero.md b/site/content/docs/v1.1.0/migrating-to-velero.md index 1fbff6c72..58dc187fe 100644 --- a/site/content/docs/v1.1.0/migrating-to-velero.md +++ b/site/content/docs/v1.1.0/migrating-to-velero.md @@ -39,7 +39,7 @@ kubectl scale --namespace heptio-ark deployment/ark --replicas 0 ARCH="amd64" # Download the velero client/example tarball to and unpack -curl -L https://github.com/vmware-tanzu/velero/releases/download/v0.11.0/velero-v0.11.0-${OS}-${ARCH}.tar.gz --output velero-v0.11.0-${OS}-${ARCH}.tar.gz +curl -L https://github.com/velero-io/velero/releases/download/v0.11.0/velero-v0.11.0-${OS}-${ARCH}.tar.gz --output velero-v0.11.0-${OS}-${ARCH}.tar.gz tar xvf velero-v0.11.0-${OS}-${ARCH}.tar.gz # Create the prerequisite CRDs and namespace diff --git a/site/content/docs/v1.1.0/oracle-config.md b/site/content/docs/v1.1.0/oracle-config.md index da2def5fd..f6993a405 100644 --- a/site/content/docs/v1.1.0/oracle-config.md +++ b/site/content/docs/v1.1.0/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.1.0/plugins.md b/site/content/docs/v1.1.0/plugins.md index 0b9d40997..a36218d6f 100644 --- a/site/content/docs/v1.1.0/plugins.md +++ b/site/content/docs/v1.1.0/plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -80,6 +80,6 @@ Then, in your plugin's implementation, you can read this ConfigMap to fetch the for an example of this -- in particular, the `getPluginConfig(...)` function. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.1.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.1.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.1.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.1.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.1.0/restic.md b/site/content/docs/v1.1.0/restic.md index d73e8db57..000efa4ae 100644 --- a/site/content/docs/v1.1.0/restic.md +++ b/site/content/docs/v1.1.0/restic.md @@ -375,7 +375,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: install-overview.md -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.1.0/start-contributing.md b/site/content/docs/v1.1.0/start-contributing.md index b70bdfbca..5d5d2bfbd 100644 --- a/site/content/docs/v1.1.0/start-contributing.md +++ b/site/content/docs/v1.1.0/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ### Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page. @@ -20,5 +20,5 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/main/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/main/CONTRIBUTING.md +[1]: https://github.com/velero-io/velero/blob/main/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/main/CONTRIBUTING.md diff --git a/site/content/docs/v1.1.0/support-matrix.md b/site/content/docs/v1.1.0/support-matrix.md index a43ab838e..0e3375fd7 100644 --- a/site/content/docs/v1.1.0/support-matrix.md +++ b/site/content/docs/v1.1.0/support-matrix.md @@ -61,10 +61,10 @@ After you publish your plugin, open a PR that adds your plugin to the appropriat [5]: ibm-config.md [6]: https://docs.portworx.com/scheduler/kubernetes/ark.html [7]: https://github.com/StackPointCloud/ark-plugin-digitalocean -[8]: https://github.com/vmware-tanzu/velero-plugin-example/ +[8]: https://github.com/velero-io/velero-plugin-example/ [9]: get-started.md [10]: https://kubernetes.slack.com/messages/velero -[11]: https://github.com/vmware-tanzu/velero/issues +[11]: https://github.com/velero-io/velero/issues [12]: https://github.com/aws/aws-sdk-go [13]: https://portworx.slack.com/messages/px-k8s [14]: https://github.com/portworx/ark-plugin/issues diff --git a/site/content/docs/v1.1.0/troubleshooting.md b/site/content/docs/v1.1.0/troubleshooting.md index 132506863..a1d1ac5f7 100644 --- a/site/content/docs/v1.1.0/troubleshooting.md +++ b/site/content/docs/v1.1.0/troubleshooting.md @@ -73,6 +73,6 @@ Backups in the `InProgress` phase have not uploaded any files to object storage. [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [25]: https://kubernetes.slack.com/messages/velero diff --git a/site/content/docs/v1.1.0/upgrade-to-1.1.md b/site/content/docs/v1.1.0/upgrade-to-1.1.md index 2a5221841..a36d98e34 100644 --- a/site/content/docs/v1.1.0/upgrade-to-1.1.md +++ b/site/content/docs/v1.1.0/upgrade-to-1.1.md @@ -25,4 +25,4 @@ kubectl patch deployment/velero -n \ -p='[{"op":"add","path":"/spec/template/spec/containers/0/env/0","value":{"name":"VELERO_NAMESPACE", "valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}}}]' ``` -[1]: https://github.com/vmware-tanzu/velero/releases/tag/v1.0.0 +[1]: https://github.com/velero-io/velero/releases/tag/v1.0.0 diff --git a/site/content/docs/v1.10/_index.md b/site/content/docs/v1.10/_index.md index 492121411..a88c2eb08 100644 --- a/site/content/docs/v1.10/_index.md +++ b/site/content/docs/v1.10/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.10/backup-hooks.md b/site/content/docs/v1.10/backup-hooks.md index 449cbeb8c..18cbf890c 100644 --- a/site/content/docs/v1.10/backup-hooks.md +++ b/site/content/docs/v1.10/backup-hooks.md @@ -104,4 +104,4 @@ Note that the container must support the shell command you use. [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.10.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.10/backup-reference.md b/site/content/docs/v1.10/backup-reference.md index b0eddab29..02c02a404 100644 --- a/site/content/docs/v1.10/backup-reference.md +++ b/site/content/docs/v1.10/backup-reference.md @@ -72,7 +72,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). ## Kubernetes API Pagination diff --git a/site/content/docs/v1.10/basic-install.md b/site/content/docs/v1.10/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.10/basic-install.md +++ b/site/content/docs/v1.10/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.10/build-from-source.md b/site/content/docs/v1.10/build-from-source.md index 083cdc202..d25205c01 100644 --- a/site/content/docs/v1.10/build-from-source.md +++ b/site/content/docs/v1.10/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.10/code-standards.md b/site/content/docs/v1.10/code-standards.md index 256ddbcfa..7640bd392 100644 --- a/site/content/docs/v1.10/code-standards.md +++ b/site/content/docs/v1.10/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.10.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.10.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.10/contributions/ibm-config.md b/site/content/docs/v1.10/contributions/ibm-config.md index 332d0a570..0f9d722db 100644 --- a/site/content/docs/v1.10/contributions/ibm-config.md +++ b/site/content/docs/v1.10/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.10/contributions/minio.md b/site/content/docs/v1.10/contributions/minio.md index b04354a1f..b5649c89a 100644 --- a/site/content/docs/v1.10/contributions/minio.md +++ b/site/content/docs/v1.10/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.10/contributions/oracle-config.md b/site/content/docs/v1.10/contributions/oracle-config.md index 9ac240024..49f16ce9e 100644 --- a/site/content/docs/v1.10/contributions/oracle-config.md +++ b/site/content/docs/v1.10/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.10/csi.md b/site/content/docs/v1.10/csi.md index 22bafca11..d8c3c5eff 100644 --- a/site/content/docs/v1.10/csi.md +++ b/site/content/docs/v1.10/csi.md @@ -68,7 +68,7 @@ When the Velero backup expires, the VolumeSnapshot objects will be deleted and t For more details on how each plugin works, see the [CSI plugin repo][2]'s documentation. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. [1]: customize-installation.md#enable-server-side-features [2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ diff --git a/site/content/docs/v1.10/custom-plugins.md b/site/content/docs/v1.10/custom-plugins.md index c26698dc0..5baa6379b 100644 --- a/site/content/docs/v1.10/custom-plugins.md +++ b/site/content/docs/v1.10/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -111,5 +111,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.10.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.10/customize-installation.md b/site/content/docs/v1.10/customize-installation.md index ab176ab94..0d2946a05 100644 --- a/site/content/docs/v1.10/customize-installation.md +++ b/site/content/docs/v1.10/customize-installation.md @@ -378,13 +378,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.10.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.10/examples.md b/site/content/docs/v1.10/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.10/examples.md +++ b/site/content/docs/v1.10/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.10/file-system-backup.md b/site/content/docs/v1.10/file-system-backup.md index 0ba10c618..a648ae5f4 100644 --- a/site/content/docs/v1.10/file-system-backup.md +++ b/site/content/docs/v1.10/file-system-backup.md @@ -492,7 +492,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository design](https://github.com/vmware-tanzu/velero/pull/4926) +Velero's [Unified Repository design](https://github.com/velero-io/velero/pull/4926) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -588,7 +588,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher diff --git a/site/content/docs/v1.10/image-tagging.md b/site/content/docs/v1.10/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.10/image-tagging.md +++ b/site/content/docs/v1.10/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.10/locations.md b/site/content/docs/v1.10/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.10/locations.md +++ b/site/content/docs/v1.10/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.10/maintainers.md b/site/content/docs/v1.10/maintainers.md index cad29c63b..ecea92a9e 100644 --- a/site/content/docs/v1.10/maintainers.md +++ b/site/content/docs/v1.10/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.10.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.10.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.10.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.10.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.10/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.10/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.10.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.10.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.10.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.10.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.10/migration-case.md b/site/content/docs/v1.10/migration-case.md index 12c916619..e92cf2be4 100644 --- a/site/content/docs/v1.10/migration-case.md +++ b/site/content/docs/v1.10/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.10/overview-plugins.md b/site/content/docs/v1.10/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.10/overview-plugins.md +++ b/site/content/docs/v1.10/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.10/plugin-release-instructions.md b/site/content/docs/v1.10/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.10/plugin-release-instructions.md +++ b/site/content/docs/v1.10/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.10/release-instructions.md b/site/content/docs/v1.10/release-instructions.md index 615b03536..e49c5ca39 100644 --- a/site/content/docs/v1.10/release-instructions.md +++ b/site/content/docs/v1.10/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.10.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.10.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.10/self-signed-certificates.md b/site/content/docs/v1.10/self-signed-certificates.md index 9724606de..33faee166 100644 --- a/site/content/docs/v1.10/self-signed-certificates.md +++ b/site/content/docs/v1.10/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premise environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.10/start-contributing.md b/site/content/docs/v1.10/start-contributing.md index 7f5857dbf..0975b17ca 100644 --- a/site/content/docs/v1.10/start-contributing.md +++ b/site/content/docs/v1.10/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.10.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.10.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.10.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.10.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.10.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.10/support-process.md b/site/content/docs/v1.10/support-process.md index bcc12afcd..ea205fb77 100644 --- a/site/content/docs/v1.10/support-process.md +++ b/site/content/docs/v1.10/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.10.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.10.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.10/supported-providers.md b/site/content/docs/v1.10/supported-providers.md index 4536d1bfa..164544d59 100644 --- a/site/content/docs/v1.10/supported-providers.md +++ b/site/content/docs/v1.10/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.10/tilt.md b/site/content/docs/v1.10/tilt.md index 19ec6003b..ac0582a47 100644 --- a/site/content/docs/v1.10/tilt.md +++ b/site/content/docs/v1.10/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.10/troubleshooting.md b/site/content/docs/v1.10/troubleshooting.md index d7588f23a..9952ac6df 100644 --- a/site/content/docs/v1.10/troubleshooting.md +++ b/site/content/docs/v1.10/troubleshooting.md @@ -218,7 +218,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.10/upgrade-to-1.10.md b/site/content/docs/v1.10/upgrade-to-1.10.md index 9887f6fb1..cc7c06921 100644 --- a/site/content/docs/v1.10/upgrade-to-1.10.md +++ b/site/content/docs/v1.10/upgrade-to-1.10.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.6, see the following: - [Upgrading to v1.8][4] - [Upgrading to v1.9][5] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.11/_index.md b/site/content/docs/v1.11/_index.md index 2143f5c59..3dbc24a5b 100644 --- a/site/content/docs/v1.11/_index.md +++ b/site/content/docs/v1.11/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.11/backup-hooks.md b/site/content/docs/v1.11/backup-hooks.md index cbe39c24b..7de8ed848 100644 --- a/site/content/docs/v1.11/backup-hooks.md +++ b/site/content/docs/v1.11/backup-hooks.md @@ -104,4 +104,4 @@ Note that the container must support the shell command you use. [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.11.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.11/backup-reference.md b/site/content/docs/v1.11/backup-reference.md index 00a1daf20..ce06e89bc 100644 --- a/site/content/docs/v1.11/backup-reference.md +++ b/site/content/docs/v1.11/backup-reference.md @@ -73,7 +73,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). #### Cannot support backup data immutability Starting from 1.11, Velero's backups may not work as expected when the target object storage has some kind of an "immutability" option configured. These options are known by different names (see links below for some examples). The main reason is that Velero first saves the state of a backup as Finalizing and then checks whether there are any async operations in progress. If there are, it needs to wait for all of them to be finished before moving the backup state to Complete. If there are no async operations, the state is moved to Complete right away. In either case, Velero needs to modify the metadata in object storage and that will not be possible if some kind of immutability is configured on the object storage. diff --git a/site/content/docs/v1.11/basic-install.md b/site/content/docs/v1.11/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.11/basic-install.md +++ b/site/content/docs/v1.11/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.11/build-from-source.md b/site/content/docs/v1.11/build-from-source.md index 083cdc202..d25205c01 100644 --- a/site/content/docs/v1.11/build-from-source.md +++ b/site/content/docs/v1.11/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.11/code-standards.md b/site/content/docs/v1.11/code-standards.md index e3f7c127a..eb38e3281 100644 --- a/site/content/docs/v1.11/code-standards.md +++ b/site/content/docs/v1.11/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.11.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.11.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.11/contributions/ibm-config.md b/site/content/docs/v1.11/contributions/ibm-config.md index 332d0a570..0f9d722db 100644 --- a/site/content/docs/v1.11/contributions/ibm-config.md +++ b/site/content/docs/v1.11/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.11/contributions/minio.md b/site/content/docs/v1.11/contributions/minio.md index b04354a1f..b5649c89a 100644 --- a/site/content/docs/v1.11/contributions/minio.md +++ b/site/content/docs/v1.11/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.11/contributions/oracle-config.md b/site/content/docs/v1.11/contributions/oracle-config.md index 20aff675c..b9a9f3482 100644 --- a/site/content/docs/v1.11/contributions/oracle-config.md +++ b/site/content/docs/v1.11/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.11/csi.md b/site/content/docs/v1.11/csi.md index 09b9e555c..bfeb68d4e 100644 --- a/site/content/docs/v1.11/csi.md +++ b/site/content/docs/v1.11/csi.md @@ -70,7 +70,7 @@ When the Velero backup expires, the VolumeSnapshot objects will be deleted and t For more details on how each plugin works, see the [CSI plugin repo][2]'s documentation. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. [1]: customize-installation.md#enable-server-side-features [2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ diff --git a/site/content/docs/v1.11/custom-plugins.md b/site/content/docs/v1.11/custom-plugins.md index fce6282e8..cc6808e7f 100644 --- a/site/content/docs/v1.11/custom-plugins.md +++ b/site/content/docs/v1.11/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -111,5 +111,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.11.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.11/customize-installation.md b/site/content/docs/v1.11/customize-installation.md index e3a834003..1f76bc6b0 100644 --- a/site/content/docs/v1.11/customize-installation.md +++ b/site/content/docs/v1.11/customize-installation.md @@ -378,13 +378,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.11.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.11/examples.md b/site/content/docs/v1.11/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.11/examples.md +++ b/site/content/docs/v1.11/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.11/file-system-backup.md b/site/content/docs/v1.11/file-system-backup.md index 4104bebeb..cf74ff599 100644 --- a/site/content/docs/v1.11/file-system-backup.md +++ b/site/content/docs/v1.11/file-system-backup.md @@ -492,7 +492,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository design](https://github.com/vmware-tanzu/velero/pull/4926) +Velero's [Unified Repository design](https://github.com/velero-io/velero/pull/4926) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -588,7 +588,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher diff --git a/site/content/docs/v1.11/image-tagging.md b/site/content/docs/v1.11/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.11/image-tagging.md +++ b/site/content/docs/v1.11/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.11/locations.md b/site/content/docs/v1.11/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.11/locations.md +++ b/site/content/docs/v1.11/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.11/maintainers.md b/site/content/docs/v1.11/maintainers.md index 2e5a08d23..b1409c14a 100644 --- a/site/content/docs/v1.11/maintainers.md +++ b/site/content/docs/v1.11/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.11.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.11.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.11.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.11.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.11.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.11.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.11.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.11.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.11.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.11.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.11/migration-case.md b/site/content/docs/v1.11/migration-case.md index b3b6bf562..7f5031f6c 100644 --- a/site/content/docs/v1.11/migration-case.md +++ b/site/content/docs/v1.11/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.11/overview-plugins.md b/site/content/docs/v1.11/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.11/overview-plugins.md +++ b/site/content/docs/v1.11/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.11/plugin-release-instructions.md b/site/content/docs/v1.11/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.11/plugin-release-instructions.md +++ b/site/content/docs/v1.11/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.11/release-instructions.md b/site/content/docs/v1.11/release-instructions.md index 4e45e6846..aff3a5cf6 100644 --- a/site/content/docs/v1.11/release-instructions.md +++ b/site/content/docs/v1.11/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.11.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.11.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.11/self-signed-certificates.md b/site/content/docs/v1.11/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.11/self-signed-certificates.md +++ b/site/content/docs/v1.11/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.11/start-contributing.md b/site/content/docs/v1.11/start-contributing.md index 2f4ebb0e2..8968a62bb 100644 --- a/site/content/docs/v1.11/start-contributing.md +++ b/site/content/docs/v1.11/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.11.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.11.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.11.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.11.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.11.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.11/support-process.md b/site/content/docs/v1.11/support-process.md index 084930692..b20214c1d 100644 --- a/site/content/docs/v1.11/support-process.md +++ b/site/content/docs/v1.11/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.11.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.11.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.11/supported-providers.md b/site/content/docs/v1.11/supported-providers.md index 4536d1bfa..164544d59 100644 --- a/site/content/docs/v1.11/supported-providers.md +++ b/site/content/docs/v1.11/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.11/tilt.md b/site/content/docs/v1.11/tilt.md index 19ec6003b..ac0582a47 100644 --- a/site/content/docs/v1.11/tilt.md +++ b/site/content/docs/v1.11/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.11/troubleshooting.md b/site/content/docs/v1.11/troubleshooting.md index a3bd3caa3..ac7539517 100644 --- a/site/content/docs/v1.11/troubleshooting.md +++ b/site/content/docs/v1.11/troubleshooting.md @@ -224,7 +224,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.11/upgrade-to-1.11.md b/site/content/docs/v1.11/upgrade-to-1.11.md index ee412a0fa..dee5f1e3c 100644 --- a/site/content/docs/v1.11/upgrade-to-1.11.md +++ b/site/content/docs/v1.11/upgrade-to-1.11.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.6, see the following: - [Upgrading to v1.9][4] - [Upgrading to v1.10][5] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.12/_index.md b/site/content/docs/v1.12/_index.md index 183bee3a9..ec337a572 100644 --- a/site/content/docs/v1.12/_index.md +++ b/site/content/docs/v1.12/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.12/backup-hooks.md b/site/content/docs/v1.12/backup-hooks.md index 03827ca42..af9b457af 100644 --- a/site/content/docs/v1.12/backup-hooks.md +++ b/site/content/docs/v1.12/backup-hooks.md @@ -104,4 +104,4 @@ Note that the container must support the shell command you use. [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.12.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.12/backup-reference.md b/site/content/docs/v1.12/backup-reference.md index 3d54cfb57..eb52cd8d9 100644 --- a/site/content/docs/v1.12/backup-reference.md +++ b/site/content/docs/v1.12/backup-reference.md @@ -74,7 +74,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). #### Cannot support backup data immutability Starting from 1.11, Velero's backups may not work as expected when the target object storage has some kind of an "immutability" option configured. These options are known by different names (see links below for some examples). The main reason is that Velero first saves the state of a backup as Finalizing and then checks whether there are any async operations in progress. If there are, it needs to wait for all of them to be finished before moving the backup state to Complete. If there are no async operations, the state is moved to Complete right away. In either case, Velero needs to modify the metadata in object storage and that will not be possible if some kind of immutability is configured on the object storage. diff --git a/site/content/docs/v1.12/basic-install.md b/site/content/docs/v1.12/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.12/basic-install.md +++ b/site/content/docs/v1.12/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.12/build-from-source.md b/site/content/docs/v1.12/build-from-source.md index 083cdc202..d25205c01 100644 --- a/site/content/docs/v1.12/build-from-source.md +++ b/site/content/docs/v1.12/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.12/code-standards.md b/site/content/docs/v1.12/code-standards.md index 3370354db..4f4cea0ef 100644 --- a/site/content/docs/v1.12/code-standards.md +++ b/site/content/docs/v1.12/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.12.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.12.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.12/contributions/ibm-config.md b/site/content/docs/v1.12/contributions/ibm-config.md index 332d0a570..0f9d722db 100644 --- a/site/content/docs/v1.12/contributions/ibm-config.md +++ b/site/content/docs/v1.12/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.12/contributions/minio.md b/site/content/docs/v1.12/contributions/minio.md index b04354a1f..b5649c89a 100644 --- a/site/content/docs/v1.12/contributions/minio.md +++ b/site/content/docs/v1.12/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.12/contributions/oracle-config.md b/site/content/docs/v1.12/contributions/oracle-config.md index b2cc32efb..9bf550d50 100644 --- a/site/content/docs/v1.12/contributions/oracle-config.md +++ b/site/content/docs/v1.12/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.12/csi-snapshot-data-movement.md b/site/content/docs/v1.12/csi-snapshot-data-movement.md index 7bba2129b..8e18cfea4 100644 --- a/site/content/docs/v1.12/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.12/csi-snapshot-data-movement.md @@ -401,7 +401,7 @@ However, Velero cancels the `DataUpload`/`DataDownload` in below scenarios autom Customized data movers that support cancellation could cancel their ongoing tasks and clean up any intermediate resources. If you are using Velero built-in data mover, the cancellation is supported. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ diff --git a/site/content/docs/v1.12/csi.md b/site/content/docs/v1.12/csi.md index 5a4e2d422..57ecffc7a 100644 --- a/site/content/docs/v1.12/csi.md +++ b/site/content/docs/v1.12/csi.md @@ -112,7 +112,7 @@ When the Velero backup expires, the VolumeSnapshot objects will be deleted and t For more details on how each plugin works, see the [CSI plugin repo][2]'s documentation. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. [1]: customize-installation.md#enable-server-side-features [2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ diff --git a/site/content/docs/v1.12/custom-plugins.md b/site/content/docs/v1.12/custom-plugins.md index 351d8ff30..a2bc73918 100644 --- a/site/content/docs/v1.12/custom-plugins.md +++ b/site/content/docs/v1.12/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -111,5 +111,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.12.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.12/customize-installation.md b/site/content/docs/v1.12/customize-installation.md index c6640d27c..9ac71d661 100644 --- a/site/content/docs/v1.12/customize-installation.md +++ b/site/content/docs/v1.12/customize-installation.md @@ -378,13 +378,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.12.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.12/examples.md b/site/content/docs/v1.12/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.12/examples.md +++ b/site/content/docs/v1.12/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.12/file-system-backup.md b/site/content/docs/v1.12/file-system-backup.md index 6799a4006..24b6cb296 100644 --- a/site/content/docs/v1.12/file-system-backup.md +++ b/site/content/docs/v1.12/file-system-backup.md @@ -506,7 +506,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository design](https://github.com/vmware-tanzu/velero/pull/4926) +Velero's [Unified Repository design](https://github.com/velero-io/velero/pull/4926) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -602,7 +602,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher diff --git a/site/content/docs/v1.12/image-tagging.md b/site/content/docs/v1.12/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.12/image-tagging.md +++ b/site/content/docs/v1.12/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.12/locations.md b/site/content/docs/v1.12/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.12/locations.md +++ b/site/content/docs/v1.12/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.12/maintainers.md b/site/content/docs/v1.12/maintainers.md index 365f2def6..ef1b9af5f 100644 --- a/site/content/docs/v1.12/maintainers.md +++ b/site/content/docs/v1.12/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.12.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.12.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.12.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.12.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.12.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.12.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.12.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.12.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.12.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.12.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.12/migration-case.md b/site/content/docs/v1.12/migration-case.md index 84687e50b..2b8e239be 100644 --- a/site/content/docs/v1.12/migration-case.md +++ b/site/content/docs/v1.12/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.12/overview-plugins.md b/site/content/docs/v1.12/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.12/overview-plugins.md +++ b/site/content/docs/v1.12/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.12/plugin-release-instructions.md b/site/content/docs/v1.12/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.12/plugin-release-instructions.md +++ b/site/content/docs/v1.12/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.12/release-instructions.md b/site/content/docs/v1.12/release-instructions.md index 10a525358..523fb5458 100644 --- a/site/content/docs/v1.12/release-instructions.md +++ b/site/content/docs/v1.12/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.12.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.12.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.12/self-signed-certificates.md b/site/content/docs/v1.12/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.12/self-signed-certificates.md +++ b/site/content/docs/v1.12/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.12/start-contributing.md b/site/content/docs/v1.12/start-contributing.md index 32ae8dd93..c3f4f77a1 100644 --- a/site/content/docs/v1.12/start-contributing.md +++ b/site/content/docs/v1.12/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.12.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.12.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.12.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.12.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.12.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.12/support-process.md b/site/content/docs/v1.12/support-process.md index 4cb25c79e..391ac4033 100644 --- a/site/content/docs/v1.12/support-process.md +++ b/site/content/docs/v1.12/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.12.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.12.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.12/supported-providers.md b/site/content/docs/v1.12/supported-providers.md index 4536d1bfa..164544d59 100644 --- a/site/content/docs/v1.12/supported-providers.md +++ b/site/content/docs/v1.12/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.12/tilt.md b/site/content/docs/v1.12/tilt.md index 19ec6003b..ac0582a47 100644 --- a/site/content/docs/v1.12/tilt.md +++ b/site/content/docs/v1.12/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.12/troubleshooting.md b/site/content/docs/v1.12/troubleshooting.md index a3bd3caa3..ac7539517 100644 --- a/site/content/docs/v1.12/troubleshooting.md +++ b/site/content/docs/v1.12/troubleshooting.md @@ -224,7 +224,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.12/upgrade-to-1.12.md b/site/content/docs/v1.12/upgrade-to-1.12.md index c974b1fd5..1e73f0a35 100644 --- a/site/content/docs/v1.12/upgrade-to-1.12.md +++ b/site/content/docs/v1.12/upgrade-to-1.12.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.7, see the following: - [Upgrading to v1.10][4] - [Upgrading to v1.11][5] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.13/_index.md b/site/content/docs/v1.13/_index.md index eabcd98e9..95e598642 100644 --- a/site/content/docs/v1.13/_index.md +++ b/site/content/docs/v1.13/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.13/backup-hooks.md b/site/content/docs/v1.13/backup-hooks.md index cfcde82b6..d575cefcf 100644 --- a/site/content/docs/v1.13/backup-hooks.md +++ b/site/content/docs/v1.13/backup-hooks.md @@ -104,4 +104,4 @@ Note that the container must support the shell command you use. [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.13.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.13/backup-reference.md b/site/content/docs/v1.13/backup-reference.md index 8b4ff5711..47d1a999d 100644 --- a/site/content/docs/v1.13/backup-reference.md +++ b/site/content/docs/v1.13/backup-reference.md @@ -79,7 +79,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.13/basic-install.md b/site/content/docs/v1.13/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.13/basic-install.md +++ b/site/content/docs/v1.13/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.13/build-from-source.md b/site/content/docs/v1.13/build-from-source.md index 083cdc202..d25205c01 100644 --- a/site/content/docs/v1.13/build-from-source.md +++ b/site/content/docs/v1.13/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.13/code-standards.md b/site/content/docs/v1.13/code-standards.md index aeb53d580..f03f537a2 100644 --- a/site/content/docs/v1.13/code-standards.md +++ b/site/content/docs/v1.13/code-standards.md @@ -80,15 +80,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.13.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.13.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.13/contributions/ibm-config.md b/site/content/docs/v1.13/contributions/ibm-config.md index 332d0a570..0f9d722db 100644 --- a/site/content/docs/v1.13/contributions/ibm-config.md +++ b/site/content/docs/v1.13/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.13/contributions/minio.md b/site/content/docs/v1.13/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.13/contributions/minio.md +++ b/site/content/docs/v1.13/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.13/contributions/oracle-config.md b/site/content/docs/v1.13/contributions/oracle-config.md index 85d866cd6..b7deed9c0 100644 --- a/site/content/docs/v1.13/contributions/oracle-config.md +++ b/site/content/docs/v1.13/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.13/csi-snapshot-data-movement.md b/site/content/docs/v1.13/csi-snapshot-data-movement.md index 57523b6b7..561404b24 100644 --- a/site/content/docs/v1.13/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.13/csi-snapshot-data-movement.md @@ -420,7 +420,7 @@ However, Velero cancels the `DataUpload`/`DataDownload` in below scenarios autom Customized data movers that support cancellation could cancel their ongoing tasks and clean up any intermediate resources. If you are using Velero built-in data mover, the cancellation is supported. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ diff --git a/site/content/docs/v1.13/csi.md b/site/content/docs/v1.13/csi.md index 6fd1f9a72..d09eacb59 100644 --- a/site/content/docs/v1.13/csi.md +++ b/site/content/docs/v1.13/csi.md @@ -112,7 +112,7 @@ When the Velero backup expires, the VolumeSnapshot objects will be deleted and t For more details on how each plugin works, see the [CSI plugin repo][2]'s documentation. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. [1]: customize-installation.md#enable-server-side-features [2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ diff --git a/site/content/docs/v1.13/custom-plugins.md b/site/content/docs/v1.13/custom-plugins.md index 216868cb5..a82e3a5a5 100644 --- a/site/content/docs/v1.13/custom-plugins.md +++ b/site/content/docs/v1.13/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -116,5 +116,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.13.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.13/customize-installation.md b/site/content/docs/v1.13/customize-installation.md index 27d070ad5..abd06c1d8 100644 --- a/site/content/docs/v1.13/customize-installation.md +++ b/site/content/docs/v1.13/customize-installation.md @@ -411,13 +411,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.13.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.13/examples.md b/site/content/docs/v1.13/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.13/examples.md +++ b/site/content/docs/v1.13/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.13/file-system-backup.md b/site/content/docs/v1.13/file-system-backup.md index 0580b55e9..ea2971ff4 100644 --- a/site/content/docs/v1.13/file-system-backup.md +++ b/site/content/docs/v1.13/file-system-backup.md @@ -493,7 +493,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository design](https://github.com/vmware-tanzu/velero/pull/4926) +Velero's [Unified Repository design](https://github.com/velero-io/velero/pull/4926) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -589,7 +589,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher diff --git a/site/content/docs/v1.13/image-tagging.md b/site/content/docs/v1.13/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.13/image-tagging.md +++ b/site/content/docs/v1.13/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.13/locations.md b/site/content/docs/v1.13/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.13/locations.md +++ b/site/content/docs/v1.13/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.13/maintainers.md b/site/content/docs/v1.13/maintainers.md index 873bef942..43853b186 100644 --- a/site/content/docs/v1.13/maintainers.md +++ b/site/content/docs/v1.13/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.13.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.13.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.13.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.13.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.13.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.13.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.13.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.13.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.13.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.13.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.13/migration-case.md b/site/content/docs/v1.13/migration-case.md index 4409117f6..89a6b84f2 100644 --- a/site/content/docs/v1.13/migration-case.md +++ b/site/content/docs/v1.13/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.13/overview-plugins.md b/site/content/docs/v1.13/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.13/overview-plugins.md +++ b/site/content/docs/v1.13/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.13/plugin-release-instructions.md b/site/content/docs/v1.13/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.13/plugin-release-instructions.md +++ b/site/content/docs/v1.13/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.13/release-instructions.md b/site/content/docs/v1.13/release-instructions.md index 776866d6b..74c82788d 100644 --- a/site/content/docs/v1.13/release-instructions.md +++ b/site/content/docs/v1.13/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.13.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.13.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.13/self-signed-certificates.md b/site/content/docs/v1.13/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.13/self-signed-certificates.md +++ b/site/content/docs/v1.13/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.13/start-contributing.md b/site/content/docs/v1.13/start-contributing.md index be4f922c6..5452c9a2b 100644 --- a/site/content/docs/v1.13/start-contributing.md +++ b/site/content/docs/v1.13/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.13.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.13.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.13.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.13.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.13.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.13/support-process.md b/site/content/docs/v1.13/support-process.md index cbd910f1f..5cdb104c2 100644 --- a/site/content/docs/v1.13/support-process.md +++ b/site/content/docs/v1.13/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.13.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.13.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.13/supported-providers.md b/site/content/docs/v1.13/supported-providers.md index 4536d1bfa..164544d59 100644 --- a/site/content/docs/v1.13/supported-providers.md +++ b/site/content/docs/v1.13/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.13/tilt.md b/site/content/docs/v1.13/tilt.md index 19ec6003b..ac0582a47 100644 --- a/site/content/docs/v1.13/tilt.md +++ b/site/content/docs/v1.13/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.13/troubleshooting.md b/site/content/docs/v1.13/troubleshooting.md index 6010b45a5..310289768 100644 --- a/site/content/docs/v1.13/troubleshooting.md +++ b/site/content/docs/v1.13/troubleshooting.md @@ -226,7 +226,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.13/upgrade-to-1.13.md b/site/content/docs/v1.13/upgrade-to-1.13.md index e2bb8138d..7ae1ba7b5 100644 --- a/site/content/docs/v1.13/upgrade-to-1.13.md +++ b/site/content/docs/v1.13/upgrade-to-1.13.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.8, see the following: - [Upgrading to v1.11][4] - [Upgrading to v1.12][5] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.14/_index.md b/site/content/docs/v1.14/_index.md index 46a1848e1..f0f125649 100644 --- a/site/content/docs/v1.14/_index.md +++ b/site/content/docs/v1.14/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.14/backup-hooks.md b/site/content/docs/v1.14/backup-hooks.md index e6be086e3..5b4f389e3 100644 --- a/site/content/docs/v1.14/backup-hooks.md +++ b/site/content/docs/v1.14/backup-hooks.md @@ -120,4 +120,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.14.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.14/backup-reference.md b/site/content/docs/v1.14/backup-reference.md index 8b4ff5711..47d1a999d 100644 --- a/site/content/docs/v1.14/backup-reference.md +++ b/site/content/docs/v1.14/backup-reference.md @@ -79,7 +79,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.14/basic-install.md b/site/content/docs/v1.14/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.14/basic-install.md +++ b/site/content/docs/v1.14/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.14/build-from-source.md b/site/content/docs/v1.14/build-from-source.md index 798800036..3abd0f459 100644 --- a/site/content/docs/v1.14/build-from-source.md +++ b/site/content/docs/v1.14/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.14/code-standards.md b/site/content/docs/v1.14/code-standards.md index c944684ca..c213e9915 100644 --- a/site/content/docs/v1.14/code-standards.md +++ b/site/content/docs/v1.14/code-standards.md @@ -80,15 +80,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.14.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.14.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.14/contributions/ibm-config.md b/site/content/docs/v1.14/contributions/ibm-config.md index 332d0a570..0f9d722db 100644 --- a/site/content/docs/v1.14/contributions/ibm-config.md +++ b/site/content/docs/v1.14/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.14/contributions/minio.md b/site/content/docs/v1.14/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.14/contributions/minio.md +++ b/site/content/docs/v1.14/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.14/contributions/oracle-config.md b/site/content/docs/v1.14/contributions/oracle-config.md index c3455fb96..4725a205c 100644 --- a/site/content/docs/v1.14/contributions/oracle-config.md +++ b/site/content/docs/v1.14/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.14/csi-snapshot-data-movement.md b/site/content/docs/v1.14/csi-snapshot-data-movement.md index 60d72aecf..1f4b39c76 100644 --- a/site/content/docs/v1.14/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.14/csi-snapshot-data-movement.md @@ -188,7 +188,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -494,7 +494,7 @@ For the restore, this is not supported because sometimes the data movement resto -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ diff --git a/site/content/docs/v1.14/csi.md b/site/content/docs/v1.14/csi.md index 42d0b653c..a78c6cc74 100644 --- a/site/content/docs/v1.14/csi.md +++ b/site/content/docs/v1.14/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -117,7 +117,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/v1.14/custom-plugins.md b/site/content/docs/v1.14/custom-plugins.md index 348b3fc82..e25d1a4ef 100644 --- a/site/content/docs/v1.14/custom-plugins.md +++ b/site/content/docs/v1.14/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -116,5 +116,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.14.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.14/customize-installation.md b/site/content/docs/v1.14/customize-installation.md index 358ea9393..e3994407d 100644 --- a/site/content/docs/v1.14/customize-installation.md +++ b/site/content/docs/v1.14/customize-installation.md @@ -424,16 +424,16 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.14.0/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/v1.14/examples.md b/site/content/docs/v1.14/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.14/examples.md +++ b/site/content/docs/v1.14/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.14/file-system-backup.md b/site/content/docs/v1.14/file-system-backup.md index 2a508f05d..929d21524 100644 --- a/site/content/docs/v1.14/file-system-backup.md +++ b/site/content/docs/v1.14/file-system-backup.md @@ -490,7 +490,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/v1.14.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/v1.14.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -647,7 +647,7 @@ For Kopia repository, the cache is stored in the node-agent pod's root file syst [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher diff --git a/site/content/docs/v1.14/image-tagging.md b/site/content/docs/v1.14/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.14/image-tagging.md +++ b/site/content/docs/v1.14/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.14/locations.md b/site/content/docs/v1.14/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.14/locations.md +++ b/site/content/docs/v1.14/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.14/maintainers.md b/site/content/docs/v1.14/maintainers.md index 19a264df0..df4e1f56e 100644 --- a/site/content/docs/v1.14/maintainers.md +++ b/site/content/docs/v1.14/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.14.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.14.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.14.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.14.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.14.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.14.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.14.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.14.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.14.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.14.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.14/migration-case.md b/site/content/docs/v1.14/migration-case.md index a23100993..a41c6f7b8 100644 --- a/site/content/docs/v1.14/migration-case.md +++ b/site/content/docs/v1.14/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.14/overview-plugins.md b/site/content/docs/v1.14/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.14/overview-plugins.md +++ b/site/content/docs/v1.14/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.14/plugin-release-instructions.md b/site/content/docs/v1.14/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.14/plugin-release-instructions.md +++ b/site/content/docs/v1.14/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.14/release-instructions.md b/site/content/docs/v1.14/release-instructions.md index 6783f8cb1..a2c6385d7 100644 --- a/site/content/docs/v1.14/release-instructions.md +++ b/site/content/docs/v1.14/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.14.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.14.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.14/self-signed-certificates.md b/site/content/docs/v1.14/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.14/self-signed-certificates.md +++ b/site/content/docs/v1.14/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.14/start-contributing.md b/site/content/docs/v1.14/start-contributing.md index 84d9ea687..1db093e3a 100644 --- a/site/content/docs/v1.14/start-contributing.md +++ b/site/content/docs/v1.14/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.14.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.14.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.14.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.14.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.14.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.14/support-process.md b/site/content/docs/v1.14/support-process.md index b68665b68..abb32b490 100644 --- a/site/content/docs/v1.14/support-process.md +++ b/site/content/docs/v1.14/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.14.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.14.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.14/supported-providers.md b/site/content/docs/v1.14/supported-providers.md index 6977b47a3..e64aa7a25 100644 --- a/site/content/docs/v1.14/supported-providers.md +++ b/site/content/docs/v1.14/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -61,9 +61,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.14/tilt.md b/site/content/docs/v1.14/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/v1.14/tilt.md +++ b/site/content/docs/v1.14/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.14/troubleshooting.md b/site/content/docs/v1.14/troubleshooting.md index 6010b45a5..310289768 100644 --- a/site/content/docs/v1.14/troubleshooting.md +++ b/site/content/docs/v1.14/troubleshooting.md @@ -226,7 +226,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.14/upgrade-to-1.14.md b/site/content/docs/v1.14/upgrade-to-1.14.md index 1ad207177..be7292296 100644 --- a/site/content/docs/v1.14/upgrade-to-1.14.md +++ b/site/content/docs/v1.14/upgrade-to-1.14.md @@ -16,7 +16,7 @@ If you're not yet running at least Velero v1.8, see the following: - [Upgrading to v1.12][5] - [Upgrading to v1.13][6] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.15/_index.md b/site/content/docs/v1.15/_index.md index f1a9011a9..eae5f4b01 100644 --- a/site/content/docs/v1.15/_index.md +++ b/site/content/docs/v1.15/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.15/backup-hooks.md b/site/content/docs/v1.15/backup-hooks.md index e0626aad4..c02dc5f13 100644 --- a/site/content/docs/v1.15/backup-hooks.md +++ b/site/content/docs/v1.15/backup-hooks.md @@ -123,4 +123,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.15.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.15/backup-reference.md b/site/content/docs/v1.15/backup-reference.md index 220d97acc..f2045211f 100644 --- a/site/content/docs/v1.15/backup-reference.md +++ b/site/content/docs/v1.15/backup-reference.md @@ -106,7 +106,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.15/basic-install.md b/site/content/docs/v1.15/basic-install.md index b84afcdde..302b4c45e 100644 --- a/site/content/docs/v1.15/basic-install.md +++ b/site/content/docs/v1.15/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.15/build-from-source.md b/site/content/docs/v1.15/build-from-source.md index 798800036..3abd0f459 100644 --- a/site/content/docs/v1.15/build-from-source.md +++ b/site/content/docs/v1.15/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.15/code-standards.md b/site/content/docs/v1.15/code-standards.md index 0f6276b2e..0cd84f1c4 100644 --- a/site/content/docs/v1.15/code-standards.md +++ b/site/content/docs/v1.15/code-standards.md @@ -82,15 +82,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.15.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.15.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.15/contributions/ibm-config.md b/site/content/docs/v1.15/contributions/ibm-config.md index 464f53c82..a34fe3625 100644 --- a/site/content/docs/v1.15/contributions/ibm-config.md +++ b/site/content/docs/v1.15/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.15/contributions/minio.md b/site/content/docs/v1.15/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.15/contributions/minio.md +++ b/site/content/docs/v1.15/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.15/contributions/oracle-config.md b/site/content/docs/v1.15/contributions/oracle-config.md index 17719f3f6..6c4c3dd5d 100644 --- a/site/content/docs/v1.15/contributions/oracle-config.md +++ b/site/content/docs/v1.15/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.15/csi-snapshot-data-movement.md b/site/content/docs/v1.15/csi-snapshot-data-movement.md index 595db51fb..5734c800b 100644 --- a/site/content/docs/v1.15/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.15/csi-snapshot-data-movement.md @@ -62,7 +62,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -382,7 +382,7 @@ The `BackupPVC` serves as an intermediate Persistent Volume Claim (PVC) utilized In complex storage environments, optimizing `BackupPVC` configurations can significantly enhance the performance of backup operations. [This document][16] outlines advanced configuration options for `BackupPVC`, allowing users to fine-tune access modes and storage class settings based on their storage provider's capabilities. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ @@ -398,5 +398,5 @@ advanced configuration options for `BackupPVC`, allowing users to fine-tune acce [15]: data-movement-backup-node-selection.md [16]: data-movement-backup-pvc-configuration.md [17]: backup-repository-configuration.md -[18]: https://github.com/vmware-tanzu/velero/pull/7576 +[18]: https://github.com/velero-io/velero/pull/7576 diff --git a/site/content/docs/v1.15/csi.md b/site/content/docs/v1.15/csi.md index 42d0b653c..a78c6cc74 100644 --- a/site/content/docs/v1.15/csi.md +++ b/site/content/docs/v1.15/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -117,7 +117,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/v1.15/custom-plugins.md b/site/content/docs/v1.15/custom-plugins.md index 78730b66f..dfeff2994 100644 --- a/site/content/docs/v1.15/custom-plugins.md +++ b/site/content/docs/v1.15/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -117,5 +117,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.15.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.15/customize-installation.md b/site/content/docs/v1.15/customize-installation.md index 6dc530b6c..1e267ea03 100644 --- a/site/content/docs/v1.15/customize-installation.md +++ b/site/content/docs/v1.15/customize-installation.md @@ -418,16 +418,16 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.15.0/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/v1.15/examples.md b/site/content/docs/v1.15/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.15/examples.md +++ b/site/content/docs/v1.15/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.15/file-system-backup.md b/site/content/docs/v1.15/file-system-backup.md index 5dcf9317d..65d657f1c 100644 --- a/site/content/docs/v1.15/file-system-backup.md +++ b/site/content/docs/v1.15/file-system-backup.md @@ -491,7 +491,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/v1.15.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/v1.15.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -691,7 +691,7 @@ In the output of `velero backup describe` command for a backup with fs-backup: [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher @@ -704,5 +704,5 @@ In the output of `velero backup describe` command for a backup with fs-backup: [14]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/ [15]: customize-installation.md#customize-resource-requests-and-limits [16]: performance-guidance.md -[17]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/GOVERNANCE.md#deprecation-policy +[17]: https://github.com/velero-io/velero/blob/v1.15.0/GOVERNANCE.md#deprecation-policy [18]: backup-repository-configuration.md diff --git a/site/content/docs/v1.15/image-tagging.md b/site/content/docs/v1.15/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.15/image-tagging.md +++ b/site/content/docs/v1.15/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.15/locations.md b/site/content/docs/v1.15/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.15/locations.md +++ b/site/content/docs/v1.15/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.15/maintainers.md b/site/content/docs/v1.15/maintainers.md index e54b7b1cf..b122b6e3d 100644 --- a/site/content/docs/v1.15/maintainers.md +++ b/site/content/docs/v1.15/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.15.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.15.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.15.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.15.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.15.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.15.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.15.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.15.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.15.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.15.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.15/migration-case.md b/site/content/docs/v1.15/migration-case.md index 2adc4bff5..0f359700a 100644 --- a/site/content/docs/v1.15/migration-case.md +++ b/site/content/docs/v1.15/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.15/overview-plugins.md b/site/content/docs/v1.15/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.15/overview-plugins.md +++ b/site/content/docs/v1.15/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.15/plugin-release-instructions.md b/site/content/docs/v1.15/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.15/plugin-release-instructions.md +++ b/site/content/docs/v1.15/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.15/release-instructions.md b/site/content/docs/v1.15/release-instructions.md index 82e343aee..64925e1e5 100644 --- a/site/content/docs/v1.15/release-instructions.md +++ b/site/content/docs/v1.15/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.15.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.15.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.15/restore-reference.md b/site/content/docs/v1.15/restore-reference.md index 429289f57..bef2f4bcf 100644 --- a/site/content/docs/v1.15/restore-reference.md +++ b/site/content/docs/v1.15/restore-reference.md @@ -241,7 +241,7 @@ data: : ``` -Note: This feature is deprecated as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/vmware-tanzu/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. E.g., it doesn't work for PVCs with ```WaitForFirstConsumer``` as the ```volumeBindingMode```. These kind of PVCs won't be bound until the pod is scheduled and the scheduler will overwrite the selected-node annotation to the node where the pod is scheduled to. +Note: This feature is deprecated as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/velero-io/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. E.g., it doesn't work for PVCs with ```WaitForFirstConsumer``` as the ```volumeBindingMode```. These kind of PVCs won't be bound until the pod is scheduled and the scheduler will overwrite the selected-node annotation to the node where the pod is scheduled to. ## Restoring into a different namespace diff --git a/site/content/docs/v1.15/self-signed-certificates.md b/site/content/docs/v1.15/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.15/self-signed-certificates.md +++ b/site/content/docs/v1.15/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.15/start-contributing.md b/site/content/docs/v1.15/start-contributing.md index 096133ec0..1b43bde76 100644 --- a/site/content/docs/v1.15/start-contributing.md +++ b/site/content/docs/v1.15/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.15.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.15.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.15.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.15.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.15.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.15/support-process.md b/site/content/docs/v1.15/support-process.md index a2a72eef4..f10d85fee 100644 --- a/site/content/docs/v1.15/support-process.md +++ b/site/content/docs/v1.15/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.15.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.15.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.15/supported-providers.md b/site/content/docs/v1.15/supported-providers.md index 11ea60a15..b71571017 100644 --- a/site/content/docs/v1.15/supported-providers.md +++ b/site/content/docs/v1.15/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.15/tilt.md b/site/content/docs/v1.15/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/v1.15/tilt.md +++ b/site/content/docs/v1.15/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.15/troubleshooting.md b/site/content/docs/v1.15/troubleshooting.md index 6010b45a5..310289768 100644 --- a/site/content/docs/v1.15/troubleshooting.md +++ b/site/content/docs/v1.15/troubleshooting.md @@ -226,7 +226,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.15/upgrade-to-1.15.md b/site/content/docs/v1.15/upgrade-to-1.15.md index 99098ad9c..34efe025a 100644 --- a/site/content/docs/v1.15/upgrade-to-1.15.md +++ b/site/content/docs/v1.15/upgrade-to-1.15.md @@ -17,7 +17,7 @@ If you're not yet running at least Velero v1.14, see the following: - [Upgrading to v1.13][6] - [Upgrading to v1.14][7] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.16/_index.md b/site/content/docs/v1.16/_index.md index 870cd2866..b5a62b89f 100644 --- a/site/content/docs/v1.16/_index.md +++ b/site/content/docs/v1.16/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.16/backup-hooks.md b/site/content/docs/v1.16/backup-hooks.md index 1ef3336cc..9f0bf4d41 100644 --- a/site/content/docs/v1.16/backup-hooks.md +++ b/site/content/docs/v1.16/backup-hooks.md @@ -123,4 +123,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.16.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.16/backup-reference.md b/site/content/docs/v1.16/backup-reference.md index 220d97acc..f2045211f 100644 --- a/site/content/docs/v1.16/backup-reference.md +++ b/site/content/docs/v1.16/backup-reference.md @@ -106,7 +106,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.16/basic-install.md b/site/content/docs/v1.16/basic-install.md index fa7beeda8..19b7671ae 100644 --- a/site/content/docs/v1.16/basic-install.md +++ b/site/content/docs/v1.16/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -65,7 +65,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.16/build-from-source.md b/site/content/docs/v1.16/build-from-source.md index 5f617c8ae..72f1e9098 100644 --- a/site/content/docs/v1.16/build-from-source.md +++ b/site/content/docs/v1.16/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -193,6 +193,6 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx diff --git a/site/content/docs/v1.16/code-standards.md b/site/content/docs/v1.16/code-standards.md index e20df5d35..68149ebbc 100644 --- a/site/content/docs/v1.16/code-standards.md +++ b/site/content/docs/v1.16/code-standards.md @@ -82,15 +82,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.16.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.16.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.16/contributions/ibm-config.md b/site/content/docs/v1.16/contributions/ibm-config.md index 464f53c82..a34fe3625 100644 --- a/site/content/docs/v1.16/contributions/ibm-config.md +++ b/site/content/docs/v1.16/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.16/contributions/minio.md b/site/content/docs/v1.16/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.16/contributions/minio.md +++ b/site/content/docs/v1.16/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.16/contributions/oracle-config.md b/site/content/docs/v1.16/contributions/oracle-config.md index dba4858da..b610ec653 100644 --- a/site/content/docs/v1.16/contributions/oracle-config.md +++ b/site/content/docs/v1.16/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.16/csi-snapshot-data-movement.md b/site/content/docs/v1.16/csi-snapshot-data-movement.md index 5da028865..8af726363 100644 --- a/site/content/docs/v1.16/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.16/csi-snapshot-data-movement.md @@ -62,7 +62,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -387,7 +387,7 @@ The `RestorePVC` serves as an intermediate Persistent Volume Claim (PVC) utilize Sometimes, `RestorePVC` needs to be configured to increase the performance of restore operations. [This document][19] outlines advanced configuration options for `RestorePVC`, allowing users to fine-tune access modes and storage class settings based on their storage provider's capabilities. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ @@ -403,6 +403,6 @@ Sometimes, `RestorePVC` needs to be configured to increase the performance of re [15]: data-movement-backup-node-selection.md [16]: data-movement-backup-pvc-configuration.md [17]: backup-repository-configuration.md -[18]: https://github.com/vmware-tanzu/velero/pull/7576 +[18]: https://github.com/velero-io/velero/pull/7576 [19]: data-movement-restore-pvc-configuration.md diff --git a/site/content/docs/v1.16/csi.md b/site/content/docs/v1.16/csi.md index 89f697f2d..628a612bb 100644 --- a/site/content/docs/v1.16/csi.md +++ b/site/content/docs/v1.16/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -117,7 +117,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/v1.16/custom-plugins.md b/site/content/docs/v1.16/custom-plugins.md index ff2f2a806..82b2c31f7 100644 --- a/site/content/docs/v1.16/custom-plugins.md +++ b/site/content/docs/v1.16/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -117,5 +117,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.16.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.16/customize-installation.md b/site/content/docs/v1.16/customize-installation.md index 90b46939c..5e60da67a 100644 --- a/site/content/docs/v1.16/customize-installation.md +++ b/site/content/docs/v1.16/customize-installation.md @@ -418,16 +418,16 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.16.0/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/v1.16/examples.md b/site/content/docs/v1.16/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.16/examples.md +++ b/site/content/docs/v1.16/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.16/file-system-backup.md b/site/content/docs/v1.16/file-system-backup.md index 8691b6966..8b8478e7f 100644 --- a/site/content/docs/v1.16/file-system-backup.md +++ b/site/content/docs/v1.16/file-system-backup.md @@ -490,7 +490,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/v1.16.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/v1.16.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -690,7 +690,7 @@ In the output of `velero backup describe` command for a backup with fs-backup: [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-restic-integration -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher @@ -703,5 +703,5 @@ In the output of `velero backup describe` command for a backup with fs-backup: [14]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/ [15]: customize-installation.md#customize-resource-requests-and-limits [16]: performance-guidance.md -[17]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/GOVERNANCE.md#deprecation-policy +[17]: https://github.com/velero-io/velero/blob/v1.16.0/GOVERNANCE.md#deprecation-policy [18]: backup-repository-configuration.md diff --git a/site/content/docs/v1.16/image-tagging.md b/site/content/docs/v1.16/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.16/image-tagging.md +++ b/site/content/docs/v1.16/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.16/locations.md b/site/content/docs/v1.16/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.16/locations.md +++ b/site/content/docs/v1.16/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.16/maintainers.md b/site/content/docs/v1.16/maintainers.md index 27e541256..2da91bf5f 100644 --- a/site/content/docs/v1.16/maintainers.md +++ b/site/content/docs/v1.16/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.16.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.16.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.16.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.16.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.16.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.16.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.16.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.16.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.16.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.16.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.16/migration-case.md b/site/content/docs/v1.16/migration-case.md index e84377adb..6d0661a00 100644 --- a/site/content/docs/v1.16/migration-case.md +++ b/site/content/docs/v1.16/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.16/overview-plugins.md b/site/content/docs/v1.16/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.16/overview-plugins.md +++ b/site/content/docs/v1.16/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.16/plugin-release-instructions.md b/site/content/docs/v1.16/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.16/plugin-release-instructions.md +++ b/site/content/docs/v1.16/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.16/release-instructions.md b/site/content/docs/v1.16/release-instructions.md index 01554c9da..df2c9d1db 100644 --- a/site/content/docs/v1.16/release-instructions.md +++ b/site/content/docs/v1.16/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.16.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.16.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.16/repository-maintenance.md b/site/content/docs/v1.16/repository-maintenance.md index 10237de5c..987083c3c 100644 --- a/site/content/docs/v1.16/repository-maintenance.md +++ b/site/content/docs/v1.16/repository-maintenance.md @@ -176,5 +176,5 @@ Maintenance jobs will not run for backup repositories whose backup storage locat [1]: velero-install.md#usage [2]: node-agent-concurrency.md [3]: backup-repository-configuration.md#full-maintenance-interval-customization -[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 -[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 +[4]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 +[5]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 diff --git a/site/content/docs/v1.16/restore-reference.md b/site/content/docs/v1.16/restore-reference.md index e9980c601..874668c36 100644 --- a/site/content/docs/v1.16/restore-reference.md +++ b/site/content/docs/v1.16/restore-reference.md @@ -241,7 +241,7 @@ data: : ``` -Note: This feature is deprecated as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/vmware-tanzu/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. E.g., it doesn't work for PVCs with ```WaitForFirstConsumer``` as the ```volumeBindingMode```. These kind of PVCs won't be bound until the pod is scheduled and the scheduler will overwrite the selected-node annotation to the node where the pod is scheduled to. +Note: This feature is deprecated as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/velero-io/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. E.g., it doesn't work for PVCs with ```WaitForFirstConsumer``` as the ```volumeBindingMode```. These kind of PVCs won't be bound until the pod is scheduled and the scheduler will overwrite the selected-node annotation to the node where the pod is scheduled to. ## Restoring into a different namespace diff --git a/site/content/docs/v1.16/self-signed-certificates.md b/site/content/docs/v1.16/self-signed-certificates.md index b85924c73..ea572d3ed 100644 --- a/site/content/docs/v1.16/self-signed-certificates.md +++ b/site/content/docs/v1.16/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.16/start-contributing.md b/site/content/docs/v1.16/start-contributing.md index 9b7083743..e623865a9 100644 --- a/site/content/docs/v1.16/start-contributing.md +++ b/site/content/docs/v1.16/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.16.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.16.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.16.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.16.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.16.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.16/support-process.md b/site/content/docs/v1.16/support-process.md index fc286b996..0973dbfbd 100644 --- a/site/content/docs/v1.16/support-process.md +++ b/site/content/docs/v1.16/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.16.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.16.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.16/supported-providers.md b/site/content/docs/v1.16/supported-providers.md index 11ea60a15..b71571017 100644 --- a/site/content/docs/v1.16/supported-providers.md +++ b/site/content/docs/v1.16/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.16/tilt.md b/site/content/docs/v1.16/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/v1.16/tilt.md +++ b/site/content/docs/v1.16/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.16/troubleshooting.md b/site/content/docs/v1.16/troubleshooting.md index 6010b45a5..310289768 100644 --- a/site/content/docs/v1.16/troubleshooting.md +++ b/site/content/docs/v1.16/troubleshooting.md @@ -226,7 +226,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.16/upgrade-to-1.16.md b/site/content/docs/v1.16/upgrade-to-1.16.md index 47fb25409..f55c06b61 100644 --- a/site/content/docs/v1.16/upgrade-to-1.16.md +++ b/site/content/docs/v1.16/upgrade-to-1.16.md @@ -18,7 +18,7 @@ If you're not yet running at least Velero v1.15, see the following: - [Upgrading to v1.14][7] - [Upgrading to v1.15][8] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.17/_index.md b/site/content/docs/v1.17/_index.md index 971fbdcce..1e3bba37b 100644 --- a/site/content/docs/v1.17/_index.md +++ b/site/content/docs/v1.17/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.17/backup-hooks.md b/site/content/docs/v1.17/backup-hooks.md index 9894f8ec3..de9485327 100644 --- a/site/content/docs/v1.17/backup-hooks.md +++ b/site/content/docs/v1.17/backup-hooks.md @@ -123,4 +123,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.17.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.17/backup-reference.md b/site/content/docs/v1.17/backup-reference.md index 220d97acc..f2045211f 100644 --- a/site/content/docs/v1.17/backup-reference.md +++ b/site/content/docs/v1.17/backup-reference.md @@ -106,7 +106,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.17/basic-install.md b/site/content/docs/v1.17/basic-install.md index 018fea341..32c58a5c2 100644 --- a/site/content/docs/v1.17/basic-install.md +++ b/site/content/docs/v1.17/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation, ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -65,7 +65,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.17/build-from-source.md b/site/content/docs/v1.17/build-from-source.md index 5f617c8ae..72f1e9098 100644 --- a/site/content/docs/v1.17/build-from-source.md +++ b/site/content/docs/v1.17/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -193,6 +193,6 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx diff --git a/site/content/docs/v1.17/code-standards.md b/site/content/docs/v1.17/code-standards.md index eefdaf781..028daedf2 100644 --- a/site/content/docs/v1.17/code-standards.md +++ b/site/content/docs/v1.17/code-standards.md @@ -82,15 +82,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.17.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.17.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.17/contributions/ibm-config.md b/site/content/docs/v1.17/contributions/ibm-config.md index 464f53c82..a34fe3625 100644 --- a/site/content/docs/v1.17/contributions/ibm-config.md +++ b/site/content/docs/v1.17/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.17/contributions/minio.md b/site/content/docs/v1.17/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.17/contributions/minio.md +++ b/site/content/docs/v1.17/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.17/contributions/oracle-config.md b/site/content/docs/v1.17/contributions/oracle-config.md index 19871edc5..3520a9358 100644 --- a/site/content/docs/v1.17/contributions/oracle-config.md +++ b/site/content/docs/v1.17/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.17/csi-snapshot-data-movement.md b/site/content/docs/v1.17/csi-snapshot-data-movement.md index 930fc1be5..6ecea6804 100644 --- a/site/content/docs/v1.17/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.17/csi-snapshot-data-movement.md @@ -67,7 +67,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -392,7 +392,7 @@ The `RestorePVC` serves as an intermediate Persistent Volume Claim (PVC) utilize Sometimes, `RestorePVC` needs to be configured to increase the performance of restore operations. [This document][19] outlines advanced configuration options for `RestorePVC`, allowing users to fine-tune access modes and storage class settings based on their storage provider's capabilities. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ @@ -408,7 +408,7 @@ Sometimes, `RestorePVC` needs to be configured to increase the performance of re [15]: data-movement-node-selection.md [16]: data-movement-backup-pvc-configuration.md [17]: backup-repository-configuration.md -[18]: https://github.com/vmware-tanzu/velero/pull/7576 +[18]: https://github.com/velero-io/velero/pull/7576 [19]: data-movement-restore-pvc-configuration.md [20]: node-agent-prepare-queue-length.md diff --git a/site/content/docs/v1.17/csi.md b/site/content/docs/v1.17/csi.md index 53843841d..fddc5f258 100644 --- a/site/content/docs/v1.17/csi.md +++ b/site/content/docs/v1.17/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -130,7 +130,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/v1.17/custom-plugins.md b/site/content/docs/v1.17/custom-plugins.md index 5ac7eedd6..30b21fcbe 100644 --- a/site/content/docs/v1.17/custom-plugins.md +++ b/site/content/docs/v1.17/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -117,5 +117,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.17.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.17/customize-installation.md b/site/content/docs/v1.17/customize-installation.md index fde2c5280..40fad5cf4 100644 --- a/site/content/docs/v1.17/customize-installation.md +++ b/site/content/docs/v1.17/customize-installation.md @@ -505,16 +505,16 @@ The new workflow is: ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.17.0/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/v1.17/data-movement-node-selection.md b/site/content/docs/v1.17/data-movement-node-selection.md index f89b9a778..5bc52109a 100644 --- a/site/content/docs/v1.17/data-movement-node-selection.md +++ b/site/content/docs/v1.17/data-movement-node-selection.md @@ -199,7 +199,7 @@ The other VGDP instances will run on nodes, which instance type is `Standard_B4m } ``` -Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/vmware-tanzu/velero/pull/7982). +Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/velero-io/velero/pull/7982). In this example, if the backup target PVC's StorageClass is `kibishii-storage-class`, its backupPVC should use StorageClass `worker-storagepolicy`. Because the final StorageClass is `worker-storagepolicy`, the backupPod uses the loadAffinity specified by `loadAffinity`'s elements with `StorageClass` field set to `worker-storagepolicy`. backupPod will be assigned to nodes, which instance type is `Standard_B2ms`. diff --git a/site/content/docs/v1.17/examples.md b/site/content/docs/v1.17/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.17/examples.md +++ b/site/content/docs/v1.17/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.17/file-system-backup.md b/site/content/docs/v1.17/file-system-backup.md index 02dc2f78d..7b61c5c0a 100644 --- a/site/content/docs/v1.17/file-system-backup.md +++ b/site/content/docs/v1.17/file-system-backup.md @@ -539,7 +539,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/v1.17.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/v1.17.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -749,7 +749,7 @@ Velero still effectively manage restic repository, though you cannot write any n [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-file-system-backup -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher @@ -762,7 +762,7 @@ Velero still effectively manage restic repository, though you cannot write any n [14]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/ [15]: customize-installation.md#customize-resource-requests-and-limits [16]: performance-guidance.md -[17]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/GOVERNANCE.md#deprecation-policy +[17]: https://github.com/velero-io/velero/blob/v1.17.0/GOVERNANCE.md#deprecation-policy [18]: backup-repository-configuration.md [19]: node-agent-concurrency.md [20]: node-agent-prepare-queue-length.md diff --git a/site/content/docs/v1.17/image-tagging.md b/site/content/docs/v1.17/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.17/image-tagging.md +++ b/site/content/docs/v1.17/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.17/locations.md b/site/content/docs/v1.17/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.17/locations.md +++ b/site/content/docs/v1.17/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.17/maintainers.md b/site/content/docs/v1.17/maintainers.md index 33b38260b..830b0750b 100644 --- a/site/content/docs/v1.17/maintainers.md +++ b/site/content/docs/v1.17/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.17.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.17.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.17.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.17.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.17.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.17.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.17.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.17.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.17.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.17.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.17/migration-case.md b/site/content/docs/v1.17/migration-case.md index 5f51ac212..ad6caab54 100644 --- a/site/content/docs/v1.17/migration-case.md +++ b/site/content/docs/v1.17/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.17/overview-plugins.md b/site/content/docs/v1.17/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.17/overview-plugins.md +++ b/site/content/docs/v1.17/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.17/plugin-release-instructions.md b/site/content/docs/v1.17/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.17/plugin-release-instructions.md +++ b/site/content/docs/v1.17/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.17/release-instructions.md b/site/content/docs/v1.17/release-instructions.md index 755205aec..175663814 100644 --- a/site/content/docs/v1.17/release-instructions.md +++ b/site/content/docs/v1.17/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.17.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.17.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.17/repository-maintenance.md b/site/content/docs/v1.17/repository-maintenance.md index c9c76a677..34e590cf6 100644 --- a/site/content/docs/v1.17/repository-maintenance.md +++ b/site/content/docs/v1.17/repository-maintenance.md @@ -209,5 +209,5 @@ Note that priority class configuration is only read from the global configuratio [1]: velero-install.md#usage [2]: node-agent-concurrency.md [3]: backup-repository-configuration.md#full-maintenance-interval-customization -[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 -[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 +[4]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 +[5]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 diff --git a/site/content/docs/v1.17/restore-reference.md b/site/content/docs/v1.17/restore-reference.md index cf5418f7b..b062175cc 100644 --- a/site/content/docs/v1.17/restore-reference.md +++ b/site/content/docs/v1.17/restore-reference.md @@ -217,10 +217,10 @@ data: Velero by default removes PVC's `volume.kubernetes.io/selected-node` annotation during restore, so that the restored PVC could be provisioned appropriately according to ```WaitForFirstConsumer``` rules, storage topologies and the restored pod's schedule result, etc. -For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/vmware-tanzu/velero/issues/9053. +For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/velero-io/velero/issues/9053. As an expectation, when you provide the selected-node configuration, Velero sets the annotation to the node in the configuration, if the node doesn't exist in the cluster then the annotation will also be removed. -Note: This feature is under deprecation as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/vmware-tanzu/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. For more information, see issue https://github.com/vmware-tanzu/velero/issues/9053 for more information. +Note: This feature is under deprecation as of Velero 1.15, following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/velero-io/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. For more information, see issue https://github.com/velero-io/velero/issues/9053 for more information. To configure a selected-node, create a config map in the Velero namespace like the following: ```yaml diff --git a/site/content/docs/v1.17/self-signed-certificates.md b/site/content/docs/v1.17/self-signed-certificates.md index ac088b694..f42c83568 100644 --- a/site/content/docs/v1.17/self-signed-certificates.md +++ b/site/content/docs/v1.17/self-signed-certificates.md @@ -71,7 +71,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.17/start-contributing.md b/site/content/docs/v1.17/start-contributing.md index ae443e287..1bbad07a5 100644 --- a/site/content/docs/v1.17/start-contributing.md +++ b/site/content/docs/v1.17/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.17.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.17.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.17.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.17.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.17.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.17/support-process.md b/site/content/docs/v1.17/support-process.md index 096ae6a63..8362b5400 100644 --- a/site/content/docs/v1.17/support-process.md +++ b/site/content/docs/v1.17/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.17.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.17.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.17/supported-providers.md b/site/content/docs/v1.17/supported-providers.md index 11ea60a15..b71571017 100644 --- a/site/content/docs/v1.17/supported-providers.md +++ b/site/content/docs/v1.17/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.17/tilt.md b/site/content/docs/v1.17/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/v1.17/tilt.md +++ b/site/content/docs/v1.17/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.17/troubleshooting.md b/site/content/docs/v1.17/troubleshooting.md index e61eb0d7e..dc692771c 100644 --- a/site/content/docs/v1.17/troubleshooting.md +++ b/site/content/docs/v1.17/troubleshooting.md @@ -235,12 +235,12 @@ If the ownership conflict error(`maintenance must be run by designated user`) al Velero doesn't handle the conflict by design. To resolve it, please use Kopia maintenance CLI to set the ownership correctly, e.g. `kopia maintenance set --owner=default@default`. -Please refer to [Issue 9007](https://github.com/vmware-tanzu/velero/issues/9007) for more information. +Please refer to [Issue 9007](https://github.com/velero-io/velero/issues/9007) for more information. [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.17/upgrade-to-1.17.md b/site/content/docs/v1.17/upgrade-to-1.17.md index f6738d55c..e30c5b1f8 100644 --- a/site/content/docs/v1.17/upgrade-to-1.17.md +++ b/site/content/docs/v1.17/upgrade-to-1.17.md @@ -19,7 +19,7 @@ If you're not yet running at least Velero v1.16, see the following: - [Upgrading to v1.15][8] - [Upgrading to v1.16][9] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.18/_index.md b/site/content/docs/v1.18/_index.md index 10f2d53f3..9ceee79d4 100644 --- a/site/content/docs/v1.18/_index.md +++ b/site/content/docs/v1.18/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.18/backup-hooks.md b/site/content/docs/v1.18/backup-hooks.md index 465dedbad..6839eb6b8 100644 --- a/site/content/docs/v1.18/backup-hooks.md +++ b/site/content/docs/v1.18/backup-hooks.md @@ -123,4 +123,4 @@ HooksFailed: 0 [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.18.0/examples/nginx-app/with-pv.yaml diff --git a/site/content/docs/v1.18/backup-reference.md b/site/content/docs/v1.18/backup-reference.md index 220d97acc..f2045211f 100644 --- a/site/content/docs/v1.18/backup-reference.md +++ b/site/content/docs/v1.18/backup-reference.md @@ -106,7 +106,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). Some GitOps tools have configurations to avoid pruning the day 2 backups generated from the schedule. For example, the ArgoCD has two ways to do that: diff --git a/site/content/docs/v1.18/basic-install.md b/site/content/docs/v1.18/basic-install.md index 018fea341..32c58a5c2 100644 --- a/site/content/docs/v1.18/basic-install.md +++ b/site/content/docs/v1.18/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation, ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -65,7 +65,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.18/build-from-source.md b/site/content/docs/v1.18/build-from-source.md index 5f617c8ae..72f1e9098 100644 --- a/site/content/docs/v1.18/build-from-source.md +++ b/site/content/docs/v1.18/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -193,6 +193,6 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx diff --git a/site/content/docs/v1.18/code-standards.md b/site/content/docs/v1.18/code-standards.md index 9a6e0a014..d31feb880 100644 --- a/site/content/docs/v1.18/code-standards.md +++ b/site/content/docs/v1.18/code-standards.md @@ -82,15 +82,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.18.0/pkg/podvolume/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.18.0/pkg/podvolume/mocks/restorer.go Run: diff --git a/site/content/docs/v1.18/contributions/ibm-config.md b/site/content/docs/v1.18/contributions/ibm-config.md index 464f53c82..a34fe3625 100644 --- a/site/content/docs/v1.18/contributions/ibm-config.md +++ b/site/content/docs/v1.18/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.18/contributions/minio.md b/site/content/docs/v1.18/contributions/minio.md index 4b5aaa8e5..41d0e997f 100644 --- a/site/content/docs/v1.18/contributions/minio.md +++ b/site/content/docs/v1.18/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,13 +81,13 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + * This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. * Additionally, you can specify `--use-node-agent` to enable File System Backup support, and `--wait` to wait for the deployment to be ready. * This example also assumes you have named your Minio bucket "velero". - * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/vmware-tanzu/velero/issues/7268) is an example of this issue. + * Please make sure to set parameter `s3ForcePathStyle=true`. The parameter is used to set the Velero integrated AWS SDK data query address style. There are two types of the address: [virtual-host and path-style](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html). If the `s3ForcePathStyle=true` is not set, the default value is false, then the AWS SDK will query in virtual-host style, but the MinIO server only support path-style address by default. The miss match will mean Velero can upload data to MinIO, but **cannot download from MinIO**. This [link](https://github.com/velero-io/velero/issues/7268) is an example of this issue. It can be resolved by two ways: * Set `s3ForcePathStyle=true` for parameter `--backup-location-config` when installing Velero. This is the preferred way. * Make MinIO server support virtual-host style address. Add the [MINIO_DOMAIN environment variable](https://min.io/docs/minio/linux/reference/minio-server/settings/core.html#id5) for MinIO server will do the magic. @@ -296,6 +296,6 @@ In this case: [3]: ../customize-installation.md [17]: ../file-system-backup.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.18/contributions/oracle-config.md b/site/content/docs/v1.18/contributions/oracle-config.md index 210f32c15..5487d3ef0 100644 --- a/site/content/docs/v1.18/contributions/oracle-config.md +++ b/site/content/docs/v1.18/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.18/csi-snapshot-data-movement.md b/site/content/docs/v1.18/csi-snapshot-data-movement.md index cde862209..154abb198 100644 --- a/site/content/docs/v1.18/csi-snapshot-data-movement.md +++ b/site/content/docs/v1.18/csi-snapshot-data-movement.md @@ -67,7 +67,7 @@ On source cluster, Velero needs to manipulate CSI snapshots through the CSI volu To integrate Velero with the CSI volume snapshot APIs, you must enable the `EnableCSI` feature flag. -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -406,7 +406,7 @@ The `RestorePVC` serves as an intermediate Persistent Volume Claim (PVC) utilize Sometimes, `RestorePVC` needs to be configured to increase the performance of restore operations. [This document][19] outlines advanced configuration options for `RestorePVC`, allowing users to fine-tune access modes and storage class settings based on their storage provider's capabilities. -[1]: https://github.com/vmware-tanzu/velero/pull/5968 +[1]: https://github.com/velero-io/velero/pull/5968 [2]: csi.md [3]: file-system-backup.md [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ @@ -422,7 +422,7 @@ Sometimes, `RestorePVC` needs to be configured to increase the performance of re [15]: data-movement-node-selection.md [16]: data-movement-backup-pvc-configuration.md [17]: backup-repository-configuration.md -[18]: https://github.com/vmware-tanzu/velero/pull/7576 +[18]: https://github.com/velero-io/velero/pull/7576 [19]: data-movement-restore-pvc-configuration.md [20]: node-agent-prepare-queue-length.md [21]: data-movement-cache-volume.md diff --git a/site/content/docs/v1.18/csi.md b/site/content/docs/v1.18/csi.md index 53843841d..fddc5f258 100644 --- a/site/content/docs/v1.18/csi.md +++ b/site/content/docs/v1.18/csi.md @@ -8,7 +8,7 @@ Integrating Container Storage Interface (CSI) snapshot support into Velero enabl By supporting CSI snapshot APIs, Velero can support any volume provider that has a CSI driver, without requiring a Velero-specific plugin to be available. This page gives an overview of how to add support for CSI snapshots to Velero. ## Notice -From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/vmware-tanzu/velero` repository. +From release-1.14, the `github.com/vmware-tanzu/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reasons to merge the CSI plugin are: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. @@ -130,7 +130,7 @@ The `DeletionPolicy` on the VolumeSnapshotContent will be the same as the `Delet When the Velero backup expires, the VolumeSnapshot objects will be deleted and the VolumeSnapshotContent objects will be updated to have a `DeletionPolicy` of `Delete`, to free space on the storage system. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. From v1.14, no need to install the CSI plugin, because it is integrated into the Velero code base. [1]: customize-installation.md#enable-server-side-features diff --git a/site/content/docs/v1.18/custom-plugins.md b/site/content/docs/v1.18/custom-plugins.md index 33c6c1ba8..3a75c3b5a 100644 --- a/site/content/docs/v1.18/custom-plugins.md +++ b/site/content/docs/v1.18/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -117,5 +117,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.18.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.18/customize-installation.md b/site/content/docs/v1.18/customize-installation.md index 3aed69a74..b83e7c6e9 100644 --- a/site/content/docs/v1.18/customize-installation.md +++ b/site/content/docs/v1.18/customize-installation.md @@ -517,16 +517,16 @@ The new workflow is: ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: file-system-backup.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.18.0/pkg/apis/velero/v1/constants.go [12]: csi-snapshot-data-movement.md [13]: performance-guidance.md [14]: repository-maintenance.md diff --git a/site/content/docs/v1.18/data-movement-node-selection.md b/site/content/docs/v1.18/data-movement-node-selection.md index f25b02ff9..9efd1ca94 100644 --- a/site/content/docs/v1.18/data-movement-node-selection.md +++ b/site/content/docs/v1.18/data-movement-node-selection.md @@ -199,7 +199,7 @@ The other VGDP instances will run on nodes, which instance type is `Standard_B4m } ``` -Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/vmware-tanzu/velero/pull/7982). +Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/velero-io/velero/pull/7982). In this example, if the backup target PVC's StorageClass is `kibishii-storage-class`, its backupPVC should use StorageClass `worker-storagepolicy`. Because the final StorageClass is `worker-storagepolicy`, the backupPod uses the loadAffinity specified by `loadAffinity`'s elements with `StorageClass` field set to `worker-storagepolicy`. backupPod will be assigned to nodes, which instance type is `Standard_B2ms`. diff --git a/site/content/docs/v1.18/data-movement-pod-resource-configuration.md b/site/content/docs/v1.18/data-movement-pod-resource-configuration.md index 3440aa931..8861a75ed 100644 --- a/site/content/docs/v1.18/data-movement-pod-resource-configuration.md +++ b/site/content/docs/v1.18/data-movement-pod-resource-configuration.md @@ -119,7 +119,7 @@ kubectl create cm node-agent-config -n velero --from-file=node-agent-config.json ### Pod Labels Add customized labels for data mover pods to support third-party integrations and environment-specific requirements. -If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). +If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). If `podLabels` is not configured, Velero uses the in-tree third-party labels for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. @@ -140,7 +140,7 @@ The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVo ### Pod Annotations Add customized annotations for data mover pods to support third-party integrations and pod-level configuration. -If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). +If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). If `podAnnotations` is not configured, Velero uses the in-tree third-party annotations for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. diff --git a/site/content/docs/v1.18/examples.md b/site/content/docs/v1.18/examples.md index d774b387d..d13ffd317 100644 --- a/site/content/docs/v1.18/examples.md +++ b/site/content/docs/v1.18/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.18/file-system-backup.md b/site/content/docs/v1.18/file-system-backup.md index b47225799..8b0d32c2f 100644 --- a/site/content/docs/v1.18/file-system-backup.md +++ b/site/content/docs/v1.18/file-system-backup.md @@ -539,7 +539,7 @@ which is used to backup pod volume data the backup storage For more details, refer to [kopia architecture](https://kopia.io/docs/advanced/architecture/) and -Velero's [Unified Repository & Kopia Integration Design](https://github.com/vmware-tanzu/velero/blob/v1.18.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) +Velero's [Unified Repository & Kopia Integration Design](https://github.com/velero-io/velero/blob/v1.18.0/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md) ### Custom resource and controllers Velero has three custom resource definitions and associated controllers: @@ -745,7 +745,7 @@ Velero still effectively manage restic repository, though you cannot write any n [1]: https://github.com/restic/restic [2]: https://github.com/kopia/kopia [3]: customize-installation.md#enable-file-system-backup -[4]: https://github.com/vmware-tanzu/velero/releases/ +[4]: https://github.com/velero-io/velero/releases/ [5]: https://kubernetes.io/docs/concepts/storage/volumes/#local [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation [7]: https://github.com/bitsbeats/velero-pvc-watcher @@ -758,7 +758,7 @@ Velero still effectively manage restic repository, though you cannot write any n [14]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/ [15]: customize-installation.md#customize-resource-requests-and-limits [16]: performance-guidance.md -[17]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/GOVERNANCE.md#deprecation-policy +[17]: https://github.com/velero-io/velero/blob/v1.18.0/GOVERNANCE.md#deprecation-policy [18]: backup-repository-configuration.md [19]: node-agent-concurrency.md [20]: node-agent-prepare-queue-length.md diff --git a/site/content/docs/v1.18/image-tagging.md b/site/content/docs/v1.18/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.18/image-tagging.md +++ b/site/content/docs/v1.18/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.18/locations.md b/site/content/docs/v1.18/locations.md index db347801b..461d78410 100644 --- a/site/content/docs/v1.18/locations.md +++ b/site/content/docs/v1.18/locations.md @@ -306,8 +306,8 @@ velero snapshot-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.18/maintainers.md b/site/content/docs/v1.18/maintainers.md index e249880ab..123051c6e 100644 --- a/site/content/docs/v1.18/maintainers.md +++ b/site/content/docs/v1.18/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.18.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.18.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.18.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.18.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.18.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.18.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.18.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.18.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.18.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.18.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.18/migration-case.md b/site/content/docs/v1.18/migration-case.md index 7492a159b..105b98591 100644 --- a/site/content/docs/v1.18/migration-case.md +++ b/site/content/docs/v1.18/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.18/overview-plugins.md b/site/content/docs/v1.18/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.18/overview-plugins.md +++ b/site/content/docs/v1.18/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.18/plugin-release-instructions.md b/site/content/docs/v1.18/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.18/plugin-release-instructions.md +++ b/site/content/docs/v1.18/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.18/release-instructions.md b/site/content/docs/v1.18/release-instructions.md index d7f78739e..586dd5e52 100644 --- a/site/content/docs/v1.18/release-instructions.md +++ b/site/content/docs/v1.18/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.18.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.18.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -77,7 +77,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -88,7 +88,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -108,11 +108,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -176,4 +176,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.18/repository-maintenance.md b/site/content/docs/v1.18/repository-maintenance.md index 5ca4f3a8a..46ae0ad12 100644 --- a/site/content/docs/v1.18/repository-maintenance.md +++ b/site/content/docs/v1.18/repository-maintenance.md @@ -196,5 +196,5 @@ Note that priority class configuration is only read from the global configuratio [1]: velero-install.md#usage [2]: node-agent-concurrency.md [3]: backup-repository-configuration.md#full-maintenance-interval-customization -[4]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 -[5]: https://github.com/vmware-tanzu/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 +[4]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L19-L21 +[5]: https://github.com/velero-io/velero/blob/d5a2e7e6b9512e8ba52ec269ed5ce9a0fa23548c/pkg/util/third_party.go#L23-L25 diff --git a/site/content/docs/v1.18/restore-reference.md b/site/content/docs/v1.18/restore-reference.md index 6c5394cf0..b14a1dac9 100644 --- a/site/content/docs/v1.18/restore-reference.md +++ b/site/content/docs/v1.18/restore-reference.md @@ -217,7 +217,7 @@ data: Velero removes PVC's `volume.kubernetes.io/selected-node` annotation during restore, so that the restored PVC could be provisioned appropriately according to ```WaitForFirstConsumer``` rules, storage topologies and the restored pod's schedule result, etc. -For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/vmware-tanzu/velero/issues/9053. +For more information of how this selected-node annotation matters to PVC restore, see issue https://github.com/velero-io/velero/issues/9053. ## Restoring into a different namespace diff --git a/site/content/docs/v1.18/self-signed-certificates.md b/site/content/docs/v1.18/self-signed-certificates.md index 6d9af90c1..e1ef5728b 100644 --- a/site/content/docs/v1.18/self-signed-certificates.md +++ b/site/content/docs/v1.18/self-signed-certificates.md @@ -144,7 +144,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premises environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [File System Backup](file-system-backup.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.18/start-contributing.md b/site/content/docs/v1.18/start-contributing.md index 5c32825ad..d2ff47dbe 100644 --- a/site/content/docs/v1.18/start-contributing.md +++ b/site/content/docs/v1.18/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.18.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.18.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.18.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.18.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.18.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.18/support-process.md b/site/content/docs/v1.18/support-process.md index e0a292aa3..e79ac5049 100644 --- a/site/content/docs/v1.18/support-process.md +++ b/site/content/docs/v1.18/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.18.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.18.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.18/supported-configmaps/node-agent-configmap.md b/site/content/docs/v1.18/supported-configmaps/node-agent-configmap.md index f17df3815..0062b0391 100644 --- a/site/content/docs/v1.18/supported-configmaps/node-agent-configmap.md +++ b/site/content/docs/v1.18/supported-configmaps/node-agent-configmap.md @@ -430,7 +430,7 @@ For detailed information, see [Cache PVC Configuration for Data Movement Restore Add customized labels for data mover pods to support third-party integrations and environment-specific requirements. -If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). +If `podLabels` is configured, it supersedes Velero's [in-tree third-party labels](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L19-L21). If `podLabels` is not configured, Velero uses the in-tree third-party labels for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. @@ -463,7 +463,7 @@ The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVo Add customized annotations for data mover pods to support third-party integrations and pod-level configuration. -If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/vmware-tanzu/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). +If `podAnnotations` is configured, it supersedes Velero's [in-tree third-party annotations](https://github.com/velero-io/velero/blob/94f64639cee09c5caaa65b65ab5f42175f41c101/pkg/util/third_party.go#L23-L25). If `podAnnotations` is not configured, Velero uses the in-tree third-party annotations for compatibility with common cloud providers and networking solutions. The configurations work for DataUpload, DataDownload, PodVolumeBackup, and PodVolumeRestore pods. diff --git a/site/content/docs/v1.18/supported-providers.md b/site/content/docs/v1.18/supported-providers.md index 11ea60a15..b71571017 100644 --- a/site/content/docs/v1.18/supported-providers.md +++ b/site/content/docs/v1.18/supported-providers.md @@ -11,13 +11,13 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: file-system-backup.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.18/tilt.md b/site/content/docs/v1.18/tilt.md index 6d802220c..988c28f9b 100644 --- a/site/content/docs/v1.18/tilt.md +++ b/site/content/docs/v1.18/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -114,7 +114,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -140,7 +140,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.18/troubleshooting.md b/site/content/docs/v1.18/troubleshooting.md index e61eb0d7e..dc692771c 100644 --- a/site/content/docs/v1.18/troubleshooting.md +++ b/site/content/docs/v1.18/troubleshooting.md @@ -235,12 +235,12 @@ If the ownership conflict error(`maintenance must be run by designated user`) al Velero doesn't handle the conflict by design. To resolve it, please use Kopia maintenance CLI to set the ownership correctly, e.g. `kopia maintenance set --owner=default@default`. -Please refer to [Issue 9007](https://github.com/vmware-tanzu/velero/issues/9007) for more information. +Please refer to [Issue 9007](https://github.com/velero-io/velero/issues/9007) for more information. [1]: debugging-restores.md [2]: debugging-install.md [3]: file-system-backup.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.18/upgrade-to-1.18.md b/site/content/docs/v1.18/upgrade-to-1.18.md index 0bf839fe3..ba830680e 100644 --- a/site/content/docs/v1.18/upgrade-to-1.18.md +++ b/site/content/docs/v1.18/upgrade-to-1.18.md @@ -20,7 +20,7 @@ If you're not yet running at least Velero v1.17, see the following: - [Upgrading to v1.16][9] - [Upgrading to v1.17][10] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.2.0/_index.md b/site/content/docs/v1.2.0/_index.md index 13e3a082e..c320d04d1 100644 --- a/site/content/docs/v1.2.0/_index.md +++ b/site/content/docs/v1.2.0/_index.md @@ -36,11 +36,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.2.0/basic-install.md b/site/content/docs/v1.2.0/basic-install.md index 36bb149f8..2ea13b230 100644 --- a/site/content/docs/v1.2.0/basic-install.md +++ b/site/content/docs/v1.2.0/basic-install.md @@ -59,7 +59,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.2.0/build-from-source.md b/site/content/docs/v1.2.0/build-from-source.md index 6fbadc119..c0615269b 100644 --- a/site/content/docs/v1.2.0/build-from-source.md +++ b/site/content/docs/v1.2.0/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -158,4 +158,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.2.0/code-standards.md b/site/content/docs/v1.2.0/code-standards.md index d52581546..bbd323458 100644 --- a/site/content/docs/v1.2.0/code-standards.md +++ b/site/content/docs/v1.2.0/code-standards.md @@ -47,15 +47,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api ""github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api ""github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.2.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.2.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.2.0/contributions/ibm-config.md b/site/content/docs/v1.2.0/contributions/ibm-config.md index 299492bc0..0fa756650 100644 --- a/site/content/docs/v1.2.0/contributions/ibm-config.md +++ b/site/content/docs/v1.2.0/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.2.0/contributions/minio.md b/site/content/docs/v1.2.0/contributions/minio.md index b9c8c5110..0ef868b08 100644 --- a/site/content/docs/v1.2.0/contributions/minio.md +++ b/site/content/docs/v1.2.0/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -266,5 +266,5 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron diff --git a/site/content/docs/v1.2.0/contributions/oracle-config.md b/site/content/docs/v1.2.0/contributions/oracle-config.md index 885546870..d1594d4a0 100644 --- a/site/content/docs/v1.2.0/contributions/oracle-config.md +++ b/site/content/docs/v1.2.0/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.2.0/custom-plugins.md b/site/content/docs/v1.2.0/custom-plugins.md index 96c1bb04f..dd10bb735 100644 --- a/site/content/docs/v1.2.0/custom-plugins.md +++ b/site/content/docs/v1.2.0/custom-plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -89,6 +89,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.2.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.2.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.2.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.2.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.2.0/customize-installation.md b/site/content/docs/v1.2.0/customize-installation.md index 04950f8ab..a00403f5e 100644 --- a/site/content/docs/v1.2.0/customize-installation.md +++ b/site/content/docs/v1.2.0/customize-installation.md @@ -236,9 +236,9 @@ If you get an error like `complete:13: command not found: compdef`, then add the ``` [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 +[7]: https://github.com/velero-io/velero/issues/2077 diff --git a/site/content/docs/v1.2.0/faq.md b/site/content/docs/v1.2.0/faq.md index 22437aa2f..202dbea27 100644 --- a/site/content/docs/v1.2.0/faq.md +++ b/site/content/docs/v1.2.0/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.2.0/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/v1.2.0/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.2.0/hooks.md b/site/content/docs/v1.2.0/hooks.md index 7c7ec82eb..959c3925e 100644 --- a/site/content/docs/v1.2.0/hooks.md +++ b/site/content/docs/v1.2.0/hooks.md @@ -80,5 +80,5 @@ velero backup logs nginx-hook-test | grep hookCommand [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.2.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.2.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.2.0/image-tagging.md b/site/content/docs/v1.2.0/image-tagging.md index fbfb15617..75aa07d5e 100644 --- a/site/content/docs/v1.2.0/image-tagging.md +++ b/site/content/docs/v1.2.0/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.2.0/locations.md b/site/content/docs/v1.2.0/locations.md index b5d8ca3fc..22fffaa94 100644 --- a/site/content/docs/v1.2.0/locations.md +++ b/site/content/docs/v1.2.0/locations.md @@ -163,5 +163,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.2.0/overview-plugins.md b/site/content/docs/v1.2.0/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.2.0/overview-plugins.md +++ b/site/content/docs/v1.2.0/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.2.0/restic.md b/site/content/docs/v1.2.0/restic.md index 9242ed2b4..93278d89d 100644 --- a/site/content/docs/v1.2.0/restic.md +++ b/site/content/docs/v1.2.0/restic.md @@ -423,7 +423,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.2.0/start-contributing.md b/site/content/docs/v1.2.0/start-contributing.md index 29690ed51..94a09a91e 100644 --- a/site/content/docs/v1.2.0/start-contributing.md +++ b/site/content/docs/v1.2.0/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ### Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page. @@ -20,5 +20,5 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.2.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.2.0/CONTRIBUTING.md +[1]: https://github.com/velero-io/velero/blob/v1.2.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.2.0/CONTRIBUTING.md diff --git a/site/content/docs/v1.2.0/supported-providers.md b/site/content/docs/v1.2.0/supported-providers.md index 1c445d064..c7ea3e9ba 100644 --- a/site/content/docs/v1.2.0/supported-providers.md +++ b/site/content/docs/v1.2.0/supported-providers.md @@ -52,13 +52,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: https://aws.amazon.com -[8]: https://github.com/vmware-tanzu/velero-plugin-for-aws +[8]: https://github.com/velero-io/velero-plugin-for-aws [9]: https://azure.com -[10]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure +[10]: https://github.com/velero-io/velero-plugin-for-microsoft-azure [11]: https://cloud.google.com -[12]: https://github.com/vmware-tanzu/velero-plugin-for-gcp +[12]: https://github.com/velero-io/velero-plugin-for-gcp [15]: https://www.digitalocean.com/ [16]: https://github.com/StackPointCloud/ark-plugin-digitalocean [17]: https://openebs.io/ @@ -73,13 +73,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [26]: https://slack.hpedev.io/ [27]: https://github.com/hpe-storage/velero-plugin/issues [28]: https://kubernetes.slack.com/messages/velero -[29]: https://github.com/vmware-tanzu/velero/issues +[29]: https://github.com/velero-io/velero/issues [30]: restic.md [31]: https://portworx.com/ [32]: https://docs.portworx.com/scheduler/kubernetes/ark.html [33]: https://portworx.slack.com/messages/px-k8s [34]: https://github.com/portworx/ark-plugin/issues -[35]: https://github.com/vmware-tanzu/velero-plugin-for-aws#setup -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup -[37]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup +[35]: https://github.com/velero-io/velero-plugin-for-aws#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup +[37]: https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.2.0/troubleshooting.md b/site/content/docs/v1.2.0/troubleshooting.md index 81fda31f0..3dd3cee41 100644 --- a/site/content/docs/v1.2.0/troubleshooting.md +++ b/site/content/docs/v1.2.0/troubleshooting.md @@ -117,7 +117,7 @@ Now, visiting http://localhost:8085/metrics on a browser should show the metrics [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.2.0/upgrade-to-1.2.md b/site/content/docs/v1.2.0/upgrade-to-1.2.md index 3a5383a50..467eba8ea 100644 --- a/site/content/docs/v1.2.0/upgrade-to-1.2.md +++ b/site/content/docs/v1.2.0/upgrade-to-1.2.md @@ -99,7 +99,7 @@ _Note: if you're upgrading from v1.0, follow the [upgrading to v1.1][2] instruct Version: v1.2.0 ``` -[0]: https://github.com/vmware-tanzu/velero/releases/tag/v1.1.0 -[1]: https://github.com/vmware-tanzu/velero/releases/tag/v1.0.0 +[0]: https://github.com/velero-io/velero/releases/tag/v1.1.0 +[1]: https://github.com/velero-io/velero/releases/tag/v1.0.0 [2]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ [3]: basic-install.md#install-the-cli diff --git a/site/content/docs/v1.2.0/website-guidelines.md b/site/content/docs/v1.2.0/website-guidelines.md index 999c8bcb0..cc4afca4d 100644 --- a/site/content/docs/v1.2.0/website-guidelines.md +++ b/site/content/docs/v1.2.0/website-guidelines.md @@ -21,7 +21,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo bundle exec jekyll serve --livereload --future ``` -For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.2.0/site/README-JEKYLL.md). +For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/velero-io/velero/blob/v1.2.0/site/README-JEKYLL.md). ## Adding a blog post diff --git a/site/content/docs/v1.2.0/zenhub.md b/site/content/docs/v1.2.0/zenhub.md index a723fb184..ccce123d0 100644 --- a/site/content/docs/v1.2.0/zenhub.md +++ b/site/content/docs/v1.2.0/zenhub.md @@ -15,4 +15,4 @@ If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub fo ## Using ZenHub -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/velero-io/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.3.0/_index.md b/site/content/docs/v1.3.0/_index.md index 8c1339de9..2b9ebbe73 100644 --- a/site/content/docs/v1.3.0/_index.md +++ b/site/content/docs/v1.3.0/_index.md @@ -36,11 +36,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.3.0/basic-install.md b/site/content/docs/v1.3.0/basic-install.md index 7fdb5af3d..971ae29c9 100644 --- a/site/content/docs/v1.3.0/basic-install.md +++ b/site/content/docs/v1.3.0/basic-install.md @@ -60,7 +60,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.3.0/build-from-source.md b/site/content/docs/v1.3.0/build-from-source.md index 6fbadc119..c0615269b 100644 --- a/site/content/docs/v1.3.0/build-from-source.md +++ b/site/content/docs/v1.3.0/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -158,4 +158,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.3.0/code-standards.md b/site/content/docs/v1.3.0/code-standards.md index bd5b6a327..406d03cd4 100644 --- a/site/content/docs/v1.3.0/code-standards.md +++ b/site/content/docs/v1.3.0/code-standards.md @@ -47,15 +47,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api ""github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api ""github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.3.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.3.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.3.0/contributions/ibm-config.md b/site/content/docs/v1.3.0/contributions/ibm-config.md index 299492bc0..0fa756650 100644 --- a/site/content/docs/v1.3.0/contributions/ibm-config.md +++ b/site/content/docs/v1.3.0/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.3.0/contributions/minio.md b/site/content/docs/v1.3.0/contributions/minio.md index b9c8c5110..0ef868b08 100644 --- a/site/content/docs/v1.3.0/contributions/minio.md +++ b/site/content/docs/v1.3.0/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -266,5 +266,5 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron diff --git a/site/content/docs/v1.3.0/contributions/oracle-config.md b/site/content/docs/v1.3.0/contributions/oracle-config.md index 1a0154bd0..f92a8bfec 100644 --- a/site/content/docs/v1.3.0/contributions/oracle-config.md +++ b/site/content/docs/v1.3.0/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.3.0/custom-plugins.md b/site/content/docs/v1.3.0/custom-plugins.md index 10752a8b6..2aa54ff54 100644 --- a/site/content/docs/v1.3.0/custom-plugins.md +++ b/site/content/docs/v1.3.0/custom-plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -89,6 +89,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.3.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.3.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.3.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.3.0/customize-installation.md b/site/content/docs/v1.3.0/customize-installation.md index 9928c0944..f7ef89f05 100644 --- a/site/content/docs/v1.3.0/customize-installation.md +++ b/site/content/docs/v1.3.0/customize-installation.md @@ -241,10 +241,10 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 diff --git a/site/content/docs/v1.3.0/faq.md b/site/content/docs/v1.3.0/faq.md index c42d1e9f1..60b55c5bd 100644 --- a/site/content/docs/v1.3.0/faq.md +++ b/site/content/docs/v1.3.0/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.3.0/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/v1.3.0/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.3.0/hooks.md b/site/content/docs/v1.3.0/hooks.md index 2477a6f5a..847bb8bbe 100644 --- a/site/content/docs/v1.3.0/hooks.md +++ b/site/content/docs/v1.3.0/hooks.md @@ -80,5 +80,5 @@ velero backup logs nginx-hook-test | grep hookCommand [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.3.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.3.0/image-tagging.md b/site/content/docs/v1.3.0/image-tagging.md index fbfb15617..75aa07d5e 100644 --- a/site/content/docs/v1.3.0/image-tagging.md +++ b/site/content/docs/v1.3.0/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.3.0/locations.md b/site/content/docs/v1.3.0/locations.md index b5d8ca3fc..22fffaa94 100644 --- a/site/content/docs/v1.3.0/locations.md +++ b/site/content/docs/v1.3.0/locations.md @@ -163,5 +163,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.3.0/overview-plugins.md b/site/content/docs/v1.3.0/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.3.0/overview-plugins.md +++ b/site/content/docs/v1.3.0/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.3.0/release-instructions.md b/site/content/docs/v1.3.0/release-instructions.md index 1a433ea19..87b48757d 100644 --- a/site/content/docs/v1.3.0/release-instructions.md +++ b/site/content/docs/v1.3.0/release-instructions.md @@ -67,7 +67,7 @@ This process is the same for both pre-release and GA, except for the fact that t make release ``` -1. Navigate to the draft GitHub release, at https://github.com/vmware-tanzu/velero/releases. +1. Navigate to the draft GitHub release, at https://github.com/velero-io/velero/releases. 1. If this is a patch release (e.g. `v1.2.1`), note that the full `CHANGELOG-1.2.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. 1. Do a quick review for formatting. **Note:** the `goreleaser` process should detect if it's a pre-release version, and check that box in the GitHub release appropriately, but it's always worth double-checking. 1. Publish the release. diff --git a/site/content/docs/v1.3.0/restic.md b/site/content/docs/v1.3.0/restic.md index 9242ed2b4..93278d89d 100644 --- a/site/content/docs/v1.3.0/restic.md +++ b/site/content/docs/v1.3.0/restic.md @@ -423,7 +423,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.3.0/start-contributing.md b/site/content/docs/v1.3.0/start-contributing.md index 43088628b..daaed39d7 100644 --- a/site/content/docs/v1.3.0/start-contributing.md +++ b/site/content/docs/v1.3.0/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ### Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page. @@ -20,5 +20,5 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.3.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.0/CONTRIBUTING.md +[1]: https://github.com/velero-io/velero/blob/v1.3.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.3.0/CONTRIBUTING.md diff --git a/site/content/docs/v1.3.0/supported-providers.md b/site/content/docs/v1.3.0/supported-providers.md index 1c445d064..c7ea3e9ba 100644 --- a/site/content/docs/v1.3.0/supported-providers.md +++ b/site/content/docs/v1.3.0/supported-providers.md @@ -52,13 +52,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: https://aws.amazon.com -[8]: https://github.com/vmware-tanzu/velero-plugin-for-aws +[8]: https://github.com/velero-io/velero-plugin-for-aws [9]: https://azure.com -[10]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure +[10]: https://github.com/velero-io/velero-plugin-for-microsoft-azure [11]: https://cloud.google.com -[12]: https://github.com/vmware-tanzu/velero-plugin-for-gcp +[12]: https://github.com/velero-io/velero-plugin-for-gcp [15]: https://www.digitalocean.com/ [16]: https://github.com/StackPointCloud/ark-plugin-digitalocean [17]: https://openebs.io/ @@ -73,13 +73,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [26]: https://slack.hpedev.io/ [27]: https://github.com/hpe-storage/velero-plugin/issues [28]: https://kubernetes.slack.com/messages/velero -[29]: https://github.com/vmware-tanzu/velero/issues +[29]: https://github.com/velero-io/velero/issues [30]: restic.md [31]: https://portworx.com/ [32]: https://docs.portworx.com/scheduler/kubernetes/ark.html [33]: https://portworx.slack.com/messages/px-k8s [34]: https://github.com/portworx/ark-plugin/issues -[35]: https://github.com/vmware-tanzu/velero-plugin-for-aws#setup -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup -[37]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup +[35]: https://github.com/velero-io/velero-plugin-for-aws#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup +[37]: https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.3.0/troubleshooting.md b/site/content/docs/v1.3.0/troubleshooting.md index 81fda31f0..3dd3cee41 100644 --- a/site/content/docs/v1.3.0/troubleshooting.md +++ b/site/content/docs/v1.3.0/troubleshooting.md @@ -117,7 +117,7 @@ Now, visiting http://localhost:8085/metrics on a browser should show the metrics [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.3.0/upgrade-to-1.3.md b/site/content/docs/v1.3.0/upgrade-to-1.3.md index e06c04173..790429482 100644 --- a/site/content/docs/v1.3.0/upgrade-to-1.3.md +++ b/site/content/docs/v1.3.0/upgrade-to-1.3.md @@ -63,4 +63,4 @@ If you're not yet running Velero v1.2, see the following: [0]: basic-install.md#install-the-cli [1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ [2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ -[3]: https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 +[3]: https://github.com/velero-io/velero/releases/tag/v1.2.0 diff --git a/site/content/docs/v1.3.0/website-guidelines.md b/site/content/docs/v1.3.0/website-guidelines.md index 58a3b7580..e41e91d86 100644 --- a/site/content/docs/v1.3.0/website-guidelines.md +++ b/site/content/docs/v1.3.0/website-guidelines.md @@ -21,7 +21,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo bundle exec jekyll serve --livereload --future ``` -For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.3.0/site/README-JEKYLL.md). +For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/velero-io/velero/blob/v1.3.0/site/README-JEKYLL.md). ## Adding a blog post diff --git a/site/content/docs/v1.3.0/zenhub.md b/site/content/docs/v1.3.0/zenhub.md index a723fb184..ccce123d0 100644 --- a/site/content/docs/v1.3.0/zenhub.md +++ b/site/content/docs/v1.3.0/zenhub.md @@ -15,4 +15,4 @@ If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub fo ## Using ZenHub -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/velero-io/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.3.1/_index.md b/site/content/docs/v1.3.1/_index.md index 9aa12aa72..c22b5caf4 100644 --- a/site/content/docs/v1.3.1/_index.md +++ b/site/content/docs/v1.3.1/_index.md @@ -36,11 +36,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.3.1/basic-install.md b/site/content/docs/v1.3.1/basic-install.md index 7fdb5af3d..971ae29c9 100644 --- a/site/content/docs/v1.3.1/basic-install.md +++ b/site/content/docs/v1.3.1/basic-install.md @@ -60,7 +60,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.3.1/build-from-source.md b/site/content/docs/v1.3.1/build-from-source.md index 6fbadc119..c0615269b 100644 --- a/site/content/docs/v1.3.1/build-from-source.md +++ b/site/content/docs/v1.3.1/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -158,4 +158,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.3.1/code-standards.md b/site/content/docs/v1.3.1/code-standards.md index 6c9a1e81e..fbeed9247 100644 --- a/site/content/docs/v1.3.1/code-standards.md +++ b/site/content/docs/v1.3.1/code-standards.md @@ -46,15 +46,15 @@ Example: metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.3.1/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.3.1/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.3.1/contributions/ibm-config.md b/site/content/docs/v1.3.1/contributions/ibm-config.md index 299492bc0..0fa756650 100644 --- a/site/content/docs/v1.3.1/contributions/ibm-config.md +++ b/site/content/docs/v1.3.1/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.3.1/contributions/minio.md b/site/content/docs/v1.3.1/contributions/minio.md index b9c8c5110..0ef868b08 100644 --- a/site/content/docs/v1.3.1/contributions/minio.md +++ b/site/content/docs/v1.3.1/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -266,5 +266,5 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron diff --git a/site/content/docs/v1.3.1/contributions/oracle-config.md b/site/content/docs/v1.3.1/contributions/oracle-config.md index 7dc8ee00b..43ec019bf 100644 --- a/site/content/docs/v1.3.1/contributions/oracle-config.md +++ b/site/content/docs/v1.3.1/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.3.1/custom-plugins.md b/site/content/docs/v1.3.1/custom-plugins.md index 894a187fa..34d66907f 100644 --- a/site/content/docs/v1.3.1/custom-plugins.md +++ b/site/content/docs/v1.3.1/custom-plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -89,6 +89,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.1/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.3.1/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.3.1/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.3.1/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.3.1/customize-installation.md b/site/content/docs/v1.3.1/customize-installation.md index 9928c0944..f7ef89f05 100644 --- a/site/content/docs/v1.3.1/customize-installation.md +++ b/site/content/docs/v1.3.1/customize-installation.md @@ -241,10 +241,10 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 diff --git a/site/content/docs/v1.3.1/faq.md b/site/content/docs/v1.3.1/faq.md index e65fa2eec..d32bc93a4 100644 --- a/site/content/docs/v1.3.1/faq.md +++ b/site/content/docs/v1.3.1/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.3.1/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/v1.3.1/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.3.1/hooks.md b/site/content/docs/v1.3.1/hooks.md index 18c16c1e9..63d6ccc69 100644 --- a/site/content/docs/v1.3.1/hooks.md +++ b/site/content/docs/v1.3.1/hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.1/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.3.1/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.3.1/image-tagging.md b/site/content/docs/v1.3.1/image-tagging.md index fbfb15617..75aa07d5e 100644 --- a/site/content/docs/v1.3.1/image-tagging.md +++ b/site/content/docs/v1.3.1/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.3.1/locations.md b/site/content/docs/v1.3.1/locations.md index b5d8ca3fc..22fffaa94 100644 --- a/site/content/docs/v1.3.1/locations.md +++ b/site/content/docs/v1.3.1/locations.md @@ -163,5 +163,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.3.1/overview-plugins.md b/site/content/docs/v1.3.1/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.3.1/overview-plugins.md +++ b/site/content/docs/v1.3.1/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.3.1/release-instructions.md b/site/content/docs/v1.3.1/release-instructions.md index 1a433ea19..87b48757d 100644 --- a/site/content/docs/v1.3.1/release-instructions.md +++ b/site/content/docs/v1.3.1/release-instructions.md @@ -67,7 +67,7 @@ This process is the same for both pre-release and GA, except for the fact that t make release ``` -1. Navigate to the draft GitHub release, at https://github.com/vmware-tanzu/velero/releases. +1. Navigate to the draft GitHub release, at https://github.com/velero-io/velero/releases. 1. If this is a patch release (e.g. `v1.2.1`), note that the full `CHANGELOG-1.2.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. 1. Do a quick review for formatting. **Note:** the `goreleaser` process should detect if it's a pre-release version, and check that box in the GitHub release appropriately, but it's always worth double-checking. 1. Publish the release. diff --git a/site/content/docs/v1.3.1/restic.md b/site/content/docs/v1.3.1/restic.md index 3aaf9e026..180e68c3c 100644 --- a/site/content/docs/v1.3.1/restic.md +++ b/site/content/docs/v1.3.1/restic.md @@ -429,7 +429,7 @@ The [velero-volume-controller][10] written by duyanghao helps to solve this prob [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.3.1/start-contributing.md b/site/content/docs/v1.3.1/start-contributing.md index 8691cf418..0d8ae111f 100644 --- a/site/content/docs/v1.3.1/start-contributing.md +++ b/site/content/docs/v1.3.1/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ### Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page. @@ -20,5 +20,5 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.3.1/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.1/CONTRIBUTING.md +[1]: https://github.com/velero-io/velero/blob/v1.3.1/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.3.1/CONTRIBUTING.md diff --git a/site/content/docs/v1.3.1/supported-providers.md b/site/content/docs/v1.3.1/supported-providers.md index 1c445d064..c7ea3e9ba 100644 --- a/site/content/docs/v1.3.1/supported-providers.md +++ b/site/content/docs/v1.3.1/supported-providers.md @@ -52,13 +52,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: https://aws.amazon.com -[8]: https://github.com/vmware-tanzu/velero-plugin-for-aws +[8]: https://github.com/velero-io/velero-plugin-for-aws [9]: https://azure.com -[10]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure +[10]: https://github.com/velero-io/velero-plugin-for-microsoft-azure [11]: https://cloud.google.com -[12]: https://github.com/vmware-tanzu/velero-plugin-for-gcp +[12]: https://github.com/velero-io/velero-plugin-for-gcp [15]: https://www.digitalocean.com/ [16]: https://github.com/StackPointCloud/ark-plugin-digitalocean [17]: https://openebs.io/ @@ -73,13 +73,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [26]: https://slack.hpedev.io/ [27]: https://github.com/hpe-storage/velero-plugin/issues [28]: https://kubernetes.slack.com/messages/velero -[29]: https://github.com/vmware-tanzu/velero/issues +[29]: https://github.com/velero-io/velero/issues [30]: restic.md [31]: https://portworx.com/ [32]: https://docs.portworx.com/scheduler/kubernetes/ark.html [33]: https://portworx.slack.com/messages/px-k8s [34]: https://github.com/portworx/ark-plugin/issues -[35]: https://github.com/vmware-tanzu/velero-plugin-for-aws#setup -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup -[37]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup +[35]: https://github.com/velero-io/velero-plugin-for-aws#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup +[37]: https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.3.1/troubleshooting.md b/site/content/docs/v1.3.1/troubleshooting.md index 81fda31f0..3dd3cee41 100644 --- a/site/content/docs/v1.3.1/troubleshooting.md +++ b/site/content/docs/v1.3.1/troubleshooting.md @@ -117,7 +117,7 @@ Now, visiting http://localhost:8085/metrics on a browser should show the metrics [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.3.1/upgrade-to-1.3.md b/site/content/docs/v1.3.1/upgrade-to-1.3.md index bc7b5adf7..d79d619e4 100644 --- a/site/content/docs/v1.3.1/upgrade-to-1.3.md +++ b/site/content/docs/v1.3.1/upgrade-to-1.3.md @@ -63,5 +63,5 @@ If you're not yet running at least Velero v1.2, see the following: [0]: basic-install.md#install-the-cli [1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ [2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ -[3]: https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 -[4]: https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0 +[3]: https://github.com/velero-io/velero/releases/tag/v1.2.0 +[4]: https://github.com/velero-io/velero/releases/tag/v1.3.0 diff --git a/site/content/docs/v1.3.1/website-guidelines.md b/site/content/docs/v1.3.1/website-guidelines.md index 0edc930ea..82950607e 100644 --- a/site/content/docs/v1.3.1/website-guidelines.md +++ b/site/content/docs/v1.3.1/website-guidelines.md @@ -21,7 +21,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo bundle exec jekyll serve --livereload --future ``` -For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.3.1/site/README-JEKYLL.md). +For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/velero-io/velero/blob/v1.3.1/site/README-JEKYLL.md). ## Adding a blog post diff --git a/site/content/docs/v1.3.1/zenhub.md b/site/content/docs/v1.3.1/zenhub.md index a723fb184..ccce123d0 100644 --- a/site/content/docs/v1.3.1/zenhub.md +++ b/site/content/docs/v1.3.1/zenhub.md @@ -15,4 +15,4 @@ If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub fo ## Using ZenHub -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/velero-io/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.3.2/_index.md b/site/content/docs/v1.3.2/_index.md index 3b19bce04..54e7b89b3 100644 --- a/site/content/docs/v1.3.2/_index.md +++ b/site/content/docs/v1.3.2/_index.md @@ -37,11 +37,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://travis-ci.org/vmware-tanzu/velero.svg?branch=main -[2]: https://travis-ci.org/vmware-tanzu/velero +[1]: https://travis-ci.org/velero-io/velero.svg?branch=main +[2]: https://travis-ci.org/velero-io/velero -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.3.2/basic-install.md b/site/content/docs/v1.3.2/basic-install.md index 7fdb5af3d..971ae29c9 100644 --- a/site/content/docs/v1.3.2/basic-install.md +++ b/site/content/docs/v1.3.2/basic-install.md @@ -60,7 +60,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.3.2/build-from-source.md b/site/content/docs/v1.3.2/build-from-source.md index 6fbadc119..c0615269b 100644 --- a/site/content/docs/v1.3.2/build-from-source.md +++ b/site/content/docs/v1.3.2/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -158,4 +158,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.3.2/code-standards.md b/site/content/docs/v1.3.2/code-standards.md index acbeae251..0619a1810 100644 --- a/site/content/docs/v1.3.2/code-standards.md +++ b/site/content/docs/v1.3.2/code-standards.md @@ -47,15 +47,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.3.2/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.3.2/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.3.2/contributions/ibm-config.md b/site/content/docs/v1.3.2/contributions/ibm-config.md index 299492bc0..0fa756650 100644 --- a/site/content/docs/v1.3.2/contributions/ibm-config.md +++ b/site/content/docs/v1.3.2/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.3.2/contributions/minio.md b/site/content/docs/v1.3.2/contributions/minio.md index 4245c8e07..8491dbc87 100644 --- a/site/content/docs/v1.3.2/contributions/minio.md +++ b/site/content/docs/v1.3.2/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ### Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -280,5 +280,5 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron diff --git a/site/content/docs/v1.3.2/contributions/oracle-config.md b/site/content/docs/v1.3.2/contributions/oracle-config.md index 2944cc566..58fd5981d 100644 --- a/site/content/docs/v1.3.2/contributions/oracle-config.md +++ b/site/content/docs/v1.3.2/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.3.2/custom-plugins.md b/site/content/docs/v1.3.2/custom-plugins.md index 9a5b9fe61..7857e7bfb 100644 --- a/site/content/docs/v1.3.2/custom-plugins.md +++ b/site/content/docs/v1.3.2/custom-plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -89,6 +89,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.2/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.3.2/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.3.2/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.3.2/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.3.2/customize-installation.md b/site/content/docs/v1.3.2/customize-installation.md index 9928c0944..f7ef89f05 100644 --- a/site/content/docs/v1.3.2/customize-installation.md +++ b/site/content/docs/v1.3.2/customize-installation.md @@ -241,10 +241,10 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 diff --git a/site/content/docs/v1.3.2/faq.md b/site/content/docs/v1.3.2/faq.md index f49b04a90..f2d1a15b9 100644 --- a/site/content/docs/v1.3.2/faq.md +++ b/site/content/docs/v1.3.2/faq.md @@ -25,7 +25,7 @@ Examples of cases where Velero is useful: Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences -in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.3.2/pkg/restore/pod_action.go) +in [pod_action.go](https://github.com/velero-io/velero/blob/v1.3.2/pkg/restore/pod_action.go) ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups? diff --git a/site/content/docs/v1.3.2/hooks.md b/site/content/docs/v1.3.2/hooks.md index 2e688dee0..df0c80d8b 100644 --- a/site/content/docs/v1.3.2/hooks.md +++ b/site/content/docs/v1.3.2/hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.2/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.3.2/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.3.2/image-tagging.md b/site/content/docs/v1.3.2/image-tagging.md index fbfb15617..75aa07d5e 100644 --- a/site/content/docs/v1.3.2/image-tagging.md +++ b/site/content/docs/v1.3.2/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.3.2/locations.md b/site/content/docs/v1.3.2/locations.md index b5d8ca3fc..22fffaa94 100644 --- a/site/content/docs/v1.3.2/locations.md +++ b/site/content/docs/v1.3.2/locations.md @@ -163,5 +163,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.3.2/overview-plugins.md b/site/content/docs/v1.3.2/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.3.2/overview-plugins.md +++ b/site/content/docs/v1.3.2/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.3.2/release-instructions.md b/site/content/docs/v1.3.2/release-instructions.md index 1a433ea19..87b48757d 100644 --- a/site/content/docs/v1.3.2/release-instructions.md +++ b/site/content/docs/v1.3.2/release-instructions.md @@ -67,7 +67,7 @@ This process is the same for both pre-release and GA, except for the fact that t make release ``` -1. Navigate to the draft GitHub release, at https://github.com/vmware-tanzu/velero/releases. +1. Navigate to the draft GitHub release, at https://github.com/velero-io/velero/releases. 1. If this is a patch release (e.g. `v1.2.1`), note that the full `CHANGELOG-1.2.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. 1. Do a quick review for formatting. **Note:** the `goreleaser` process should detect if it's a pre-release version, and check that box in the GitHub release appropriately, but it's always worth double-checking. 1. Publish the release. diff --git a/site/content/docs/v1.3.2/restic.md b/site/content/docs/v1.3.2/restic.md index 3aaf9e026..180e68c3c 100644 --- a/site/content/docs/v1.3.2/restic.md +++ b/site/content/docs/v1.3.2/restic.md @@ -429,7 +429,7 @@ The [velero-volume-controller][10] written by duyanghao helps to solve this prob [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.3.2/start-contributing.md b/site/content/docs/v1.3.2/start-contributing.md index d7050efbf..41b3d9452 100644 --- a/site/content/docs/v1.3.2/start-contributing.md +++ b/site/content/docs/v1.3.2/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ### Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page. @@ -20,5 +20,5 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.3.2/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.3.2/CONTRIBUTING.md +[1]: https://github.com/velero-io/velero/blob/v1.3.2/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.3.2/CONTRIBUTING.md diff --git a/site/content/docs/v1.3.2/supported-providers.md b/site/content/docs/v1.3.2/supported-providers.md index eee292ae1..71ab72c14 100644 --- a/site/content/docs/v1.3.2/supported-providers.md +++ b/site/content/docs/v1.3.2/supported-providers.md @@ -53,13 +53,13 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: https://aws.amazon.com -[8]: https://github.com/vmware-tanzu/velero-plugin-for-aws +[8]: https://github.com/velero-io/velero-plugin-for-aws [9]: https://azure.com -[10]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure +[10]: https://github.com/velero-io/velero-plugin-for-microsoft-azure [11]: https://cloud.google.com -[12]: https://github.com/vmware-tanzu/velero-plugin-for-gcp +[12]: https://github.com/velero-io/velero-plugin-for-gcp [15]: https://www.digitalocean.com/ [16]: https://github.com/StackPointCloud/ark-plugin-digitalocean [17]: https://openebs.io/ @@ -74,15 +74,15 @@ In the case you want to take volume snapshots but didn't find a plugin for your [26]: https://slack.hpedev.io/ [27]: https://github.com/hpe-storage/velero-plugin/issues [28]: https://kubernetes.slack.com/messages/velero -[29]: https://github.com/vmware-tanzu/velero/issues +[29]: https://github.com/velero-io/velero/issues [30]: restic.md [31]: https://portworx.com/ [32]: https://docs.portworx.com/scheduler/kubernetes/ark.html [33]: https://portworx.slack.com/messages/px-k8s [34]: https://github.com/portworx/ark-plugin/issues -[35]: https://github.com/vmware-tanzu/velero-plugin-for-aws#setup -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup -[37]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup +[35]: https://github.com/velero-io/velero-plugin-for-aws#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup +[37]: https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup [38]: https://www.cloudian.com/ -[39]: https://github.com/vmware-tanzu/velero-plugin-for-vsphere -[40]: https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/new +[39]: https://github.com/velero-io/velero-plugin-for-vsphere +[40]: https://github.com/velero-io/velero-plugin-for-vsphere/issues/new diff --git a/site/content/docs/v1.3.2/troubleshooting.md b/site/content/docs/v1.3.2/troubleshooting.md index 81fda31f0..3dd3cee41 100644 --- a/site/content/docs/v1.3.2/troubleshooting.md +++ b/site/content/docs/v1.3.2/troubleshooting.md @@ -117,7 +117,7 @@ Now, visiting http://localhost:8085/metrics on a browser should show the metrics [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.3.2/upgrade-to-1.3.md b/site/content/docs/v1.3.2/upgrade-to-1.3.md index 8745a1b3d..f5f96686a 100644 --- a/site/content/docs/v1.3.2/upgrade-to-1.3.md +++ b/site/content/docs/v1.3.2/upgrade-to-1.3.md @@ -63,6 +63,6 @@ If you're not yet running at least Velero v1.2, see the following: [0]: basic-install.md#install-the-cli [1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ [2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ -[3]: https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 -[4]: https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0 -[5]: https://github.com/vmware-tanzu/velero/releases/tag/v1.3.1 +[3]: https://github.com/velero-io/velero/releases/tag/v1.2.0 +[4]: https://github.com/velero-io/velero/releases/tag/v1.3.0 +[5]: https://github.com/velero-io/velero/releases/tag/v1.3.1 diff --git a/site/content/docs/v1.3.2/website-guidelines.md b/site/content/docs/v1.3.2/website-guidelines.md index 84ebd4e47..d76b3d47d 100644 --- a/site/content/docs/v1.3.2/website-guidelines.md +++ b/site/content/docs/v1.3.2/website-guidelines.md @@ -21,7 +21,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo bundle exec jekyll serve --livereload --future ``` -For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.3.2/site/README-JEKYLL.md). +For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/velero-io/velero/blob/v1.3.2/site/README-JEKYLL.md). ## Adding a blog post diff --git a/site/content/docs/v1.3.2/zenhub.md b/site/content/docs/v1.3.2/zenhub.md index a723fb184..ccce123d0 100644 --- a/site/content/docs/v1.3.2/zenhub.md +++ b/site/content/docs/v1.3.2/zenhub.md @@ -15,4 +15,4 @@ If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub fo ## Using ZenHub -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/velero-io/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.4/_index.md b/site/content/docs/v1.4/_index.md index 8acf9f3a3..03f2b5f53 100644 --- a/site/content/docs/v1.4/_index.md +++ b/site/content/docs/v1.4/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.4/basic-install.md b/site/content/docs/v1.4/basic-install.md index 912beb225..acd83a85f 100644 --- a/site/content/docs/v1.4/basic-install.md +++ b/site/content/docs/v1.4/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.10-v1.21, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.10-v1.21, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.4/build-from-source.md b/site/content/docs/v1.4/build-from-source.md index 6fbadc119..c0615269b 100644 --- a/site/content/docs/v1.4/build-from-source.md +++ b/site/content/docs/v1.4/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -158,4 +158,4 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases diff --git a/site/content/docs/v1.4/code-standards.md b/site/content/docs/v1.4/code-standards.md index 9c3543cae..dbe1c70b9 100644 --- a/site/content/docs/v1.4/code-standards.md +++ b/site/content/docs/v1.4/code-standards.md @@ -55,15 +55,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.4.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.4/contributions/ibm-config.md b/site/content/docs/v1.4/contributions/ibm-config.md index 299492bc0..0fa756650 100644 --- a/site/content/docs/v1.4/contributions/ibm-config.md +++ b/site/content/docs/v1.4/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.4/contributions/minio.md b/site/content/docs/v1.4/contributions/minio.md index f4b6195f6..ae4934878 100644 --- a/site/content/docs/v1.4/contributions/minio.md +++ b/site/content/docs/v1.4/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -281,6 +281,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.4/contributions/oracle-config.md b/site/content/docs/v1.4/contributions/oracle-config.md index 234740307..717db5a6f 100644 --- a/site/content/docs/v1.4/contributions/oracle-config.md +++ b/site/content/docs/v1.4/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` *We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!* diff --git a/site/content/docs/v1.4/custom-plugins.md b/site/content/docs/v1.4/custom-plugins.md index 6bbf5863d..4aecb039c 100644 --- a/site/content/docs/v1.4/custom-plugins.md +++ b/site/content/docs/v1.4/custom-plugins.md @@ -25,7 +25,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru - example-with-dash.io/azure ``` -You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) a name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -89,6 +89,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.4.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.4.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.4/customize-installation.md b/site/content/docs/v1.4/customize-installation.md index 976e9ffe3..ee586e876 100644 --- a/site/content/docs/v1.4/customize-installation.md +++ b/site/content/docs/v1.4/customize-installation.md @@ -331,13 +331,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.4.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.4/hooks.md b/site/content/docs/v1.4/hooks.md index a648ac204..f769ee2d4 100644 --- a/site/content/docs/v1.4/hooks.md +++ b/site/content/docs/v1.4/hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.4.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.4/image-tagging.md b/site/content/docs/v1.4/image-tagging.md index fbfb15617..75aa07d5e 100644 --- a/site/content/docs/v1.4/image-tagging.md +++ b/site/content/docs/v1.4/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, e.g. `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.4/locations.md b/site/content/docs/v1.4/locations.md index aed2f6521..3641d5417 100644 --- a/site/content/docs/v1.4/locations.md +++ b/site/content/docs/v1.4/locations.md @@ -163,5 +163,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.4/overview-plugins.md b/site/content/docs/v1.4/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.4/overview-plugins.md +++ b/site/content/docs/v1.4/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.4/release-instructions.md b/site/content/docs/v1.4/release-instructions.md index 441918cee..d45093a89 100644 --- a/site/content/docs/v1.4/release-instructions.md +++ b/site/content/docs/v1.4/release-instructions.md @@ -28,7 +28,7 @@ You also need to update `site/index.html` to have "Latest Release Information" c 1. Run `NEW_DOCS_VERSION=v VELERO_VERSION=v make gen-docs` (e.g. `NEW_DOCS_VERSION=v1.2 VELERO_VERSION=v1.2.0 make gen-docs` or `NEW_DOCS_VERSION=v1.2-pre VELERO_VERSION=v1.2.0-beta.1 make gen-docs`). - Note that: - **NEW_DOCS_VERSION** defines the version that the docs will be tagged with (i.e. what's in the URL, what shows up in the version dropdown on the site). This should be formatted as either `v1.4` (for a GA release), or `v1.4-pre` (for an alpha/beta/RC). - - **VELERO_VERSION** defines the tag of Velero that any `https://github.com/vmware-tanzu/velero/...` links in the docs should redirect to. + - **VELERO_VERSION** defines the tag of Velero that any `https://github.com/velero-io/velero/...` links in the docs should redirect to. 1. Follow the additional instructions at `site/README-JEKYLL.md` to complete the docs generation process. 1. Do a review of the diffs, and/or run `make serve-docs` and review the site. 1. Submit a PR containing the changelog and the version-tagged docs. @@ -70,7 +70,7 @@ This process is the same for both pre-release and GA, except for the fact that t make release ``` -1. Navigate to the draft GitHub release, at https://github.com/vmware-tanzu/velero/releases. +1. Navigate to the draft GitHub release, at https://github.com/velero-io/velero/releases. 1. If this is a patch release (e.g. `v1.2.1`), note that the full `CHANGELOG-1.2.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. 1. Do a quick review for formatting. **Note:** the `goreleaser` process should detect if it's a pre-release version, and check that box in the GitHub release appropriately, but it's always worth double-checking. 1. Publish the release. diff --git a/site/content/docs/v1.4/restic.md b/site/content/docs/v1.4/restic.md index f5d7c39c4..cf5b97c36 100644 --- a/site/content/docs/v1.4/restic.md +++ b/site/content/docs/v1.4/restic.md @@ -431,7 +431,7 @@ The [velero-volume-controller][10] written by duyanghao helps to solve this prob [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.4/start-contributing.md b/site/content/docs/v1.4/start-contributing.md index c7dd803ef..bfb766d67 100644 --- a/site/content/docs/v1.4/start-contributing.md +++ b/site/content/docs/v1.4/start-contributing.md @@ -10,7 +10,7 @@ layout: docs ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -22,7 +22,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.4.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.4.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.4/supported-providers.md b/site/content/docs/v1.4/supported-providers.md index 6574fbf3a..9904b4bf5 100644 --- a/site/content/docs/v1.4/supported-providers.md +++ b/site/content/docs/v1.4/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | |-----------------------------------|---------------------|------------------------------|-----------------------------------------|-------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | -| [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | +| [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | | [Container Storage Interface (CSI)](https://github.com/vmware-tanzu/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Community supported providers {{< table caption="Community supported providers" >}} @@ -61,8 +61,8 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.4/troubleshooting.md b/site/content/docs/v1.4/troubleshooting.md index dd8e18919..59bc2f2af 100644 --- a/site/content/docs/v1.4/troubleshooting.md +++ b/site/content/docs/v1.4/troubleshooting.md @@ -105,7 +105,7 @@ Now, visiting http://localhost:8085/metrics on a browser should show the metrics [1]: debugging-restores.md [2]: debugging-install.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.4/upgrade-to-1.4.md b/site/content/docs/v1.4/upgrade-to-1.4.md index a173d67ad..ec071dbb3 100644 --- a/site/content/docs/v1.4/upgrade-to-1.4.md +++ b/site/content/docs/v1.4/upgrade-to-1.4.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.3, see the following: - [Upgrading to v1.2][2] - [Upgrading to v1.3][3] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions @@ -77,8 +77,8 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw [1]: https://velero.io/docs/v1.1.0/upgrade-to-1.1/ [2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ [3]: https://velero.io/docs/v1.3.2/upgrade-to-1.3/ -[4]: https://github.com/vmware-tanzu/velero/releases/tag/v1.3.2 -[5]: https://github.com/vmware-tanzu/velero/issues/2077 -[6]: https://github.com/vmware-tanzu/velero/issues/2311 -[7]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0 -[8]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2 +[4]: https://github.com/velero-io/velero/releases/tag/v1.3.2 +[5]: https://github.com/velero-io/velero/issues/2077 +[6]: https://github.com/velero-io/velero/issues/2311 +[7]: https://github.com/velero-io/velero/releases/tag/v1.4.0 +[8]: https://github.com/velero-io/velero/releases/tag/v1.4.2 diff --git a/site/content/docs/v1.4/website-guidelines.md b/site/content/docs/v1.4/website-guidelines.md index b9329505f..6d88c0178 100644 --- a/site/content/docs/v1.4/website-guidelines.md +++ b/site/content/docs/v1.4/website-guidelines.md @@ -21,7 +21,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo bundle exec jekyll serve --livereload --future ``` -For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.4.0/site/README-JEKYLL.md). +For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/velero-io/velero/blob/v1.4.0/site/README-JEKYLL.md). ## Adding a blog post diff --git a/site/content/docs/v1.4/zenhub.md b/site/content/docs/v1.4/zenhub.md index a723fb184..ccce123d0 100644 --- a/site/content/docs/v1.4/zenhub.md +++ b/site/content/docs/v1.4/zenhub.md @@ -15,4 +15,4 @@ If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub fo ## Using ZenHub -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/velero-io/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.5/_index.md b/site/content/docs/v1.5/_index.md index a3435ca24..842b8fa4d 100644 --- a/site/content/docs/v1.5/_index.md +++ b/site/content/docs/v1.5/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.5/backup-hooks.md b/site/content/docs/v1.5/backup-hooks.md index 3568ff29d..bfb0aaa03 100644 --- a/site/content/docs/v1.5/backup-hooks.md +++ b/site/content/docs/v1.5/backup-hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.5.1/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.5.1/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.5/basic-install.md b/site/content/docs/v1.5/basic-install.md index ffc374d56..812cf29ed 100644 --- a/site/content/docs/v1.5/basic-install.md +++ b/site/content/docs/v1.5/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.12-v1.21, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatabilty-matrix). +- Access to a Kubernetes cluster, v1.12-v1.21, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatabilty-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.5/build-from-source.md b/site/content/docs/v1.5/build-from-source.md index df9f738cf..f8896882a 100644 --- a/site/content/docs/v1.5/build-from-source.md +++ b/site/content/docs/v1.5/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.5/code-standards.md b/site/content/docs/v1.5/code-standards.md index a2e3e0804..b32488496 100644 --- a/site/content/docs/v1.5/code-standards.md +++ b/site/content/docs/v1.5/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.5.1/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.5.1/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.5/contributions/ibm-config.md b/site/content/docs/v1.5/contributions/ibm-config.md index 2622eedfc..14823cc03 100644 --- a/site/content/docs/v1.5/contributions/ibm-config.md +++ b/site/content/docs/v1.5/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.5/contributions/minio.md b/site/content/docs/v1.5/contributions/minio.md index 79654b7f1..db7571b70 100644 --- a/site/content/docs/v1.5/contributions/minio.md +++ b/site/content/docs/v1.5/contributions/minio.md @@ -22,9 +22,9 @@ If you encounter issues with installing or configuring, see [Debugging Installat ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -281,6 +281,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.5/contributions/oracle-config.md b/site/content/docs/v1.5/contributions/oracle-config.md index 0e1317aca..57440f083 100644 --- a/site/content/docs/v1.5/contributions/oracle-config.md +++ b/site/content/docs/v1.5/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.5/custom-plugins.md b/site/content/docs/v1.5/custom-plugins.md index 989aeec41..02b12e037 100644 --- a/site/content/docs/v1.5/custom-plugins.md +++ b/site/content/docs/v1.5/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -112,6 +112,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.5.1/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.5.1/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.5.1/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.5.1/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.5/customize-installation.md b/site/content/docs/v1.5/customize-installation.md index 9438e869b..c359129a1 100644 --- a/site/content/docs/v1.5/customize-installation.md +++ b/site/content/docs/v1.5/customize-installation.md @@ -339,13 +339,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.5.1/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.5.1/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.5/examples.md b/site/content/docs/v1.5/examples.md index 58a35fd5d..ea7213b33 100644 --- a/site/content/docs/v1.5/examples.md +++ b/site/content/docs/v1.5/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.5/image-tagging.md b/site/content/docs/v1.5/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.5/image-tagging.md +++ b/site/content/docs/v1.5/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.5/locations.md b/site/content/docs/v1.5/locations.md index ec478a587..617172ceb 100644 --- a/site/content/docs/v1.5/locations.md +++ b/site/content/docs/v1.5/locations.md @@ -165,5 +165,5 @@ velero backup create full-cluster-backup [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md diff --git a/site/content/docs/v1.5/maintainers.md b/site/content/docs/v1.5/maintainers.md index 86fe29081..3115edb2b 100644 --- a/site/content/docs/v1.5/maintainers.md +++ b/site/content/docs/v1.5/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.5.1/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.5.1/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.5.1/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.5.1/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/main/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/main/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/main/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/main/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release Maintainers are expected to create releases for the project. We have parts of the process automated, and full [instructions](release-instructions). @@ -31,4 +31,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.5.1/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.5.1/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.5/overview-plugins.md b/site/content/docs/v1.5/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.5/overview-plugins.md +++ b/site/content/docs/v1.5/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.5/release-instructions.md b/site/content/docs/v1.5/release-instructions.md index 5c0a29f18..410893e0d 100644 --- a/site/content/docs/v1.5/release-instructions.md +++ b/site/content/docs/v1.5/release-instructions.md @@ -47,7 +47,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -71,11 +71,11 @@ For each major or minor release, create and publish a blog post to let folks kno 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.0.0-rc.1 GITHUB_TOKEN=REDACTED ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.4.1`), note that the full `CHANGELOG-1.4.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. diff --git a/site/content/docs/v1.5/restic.md b/site/content/docs/v1.5/restic.md index 8265e0003..0a8a8afdd 100644 --- a/site/content/docs/v1.5/restic.md +++ b/site/content/docs/v1.5/restic.md @@ -518,7 +518,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.5/start-contributing.md b/site/content/docs/v1.5/start-contributing.md index a421e1dfd..c9536ec12 100644 --- a/site/content/docs/v1.5/start-contributing.md +++ b/site/content/docs/v1.5/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/main/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/main/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/main/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/main/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/main/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.5/supported-providers.md b/site/content/docs/v1.5/supported-providers.md index c1c20a06a..466551c77 100644 --- a/site/content/docs/v1.5/supported-providers.md +++ b/site/content/docs/v1.5/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | |-----------------------------------|---------------------|------------------------------|-----------------------------------------|-------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | -| [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | +| [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | | [Container Storage Interface (CSI)](https://github.com/vmware-tanzu/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Community supported providers {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.5/tilt.md b/site/content/docs/v1.5/tilt.md index 6b33c18a0..461d672c2 100644 --- a/site/content/docs/v1.5/tilt.md +++ b/site/content/docs/v1.5/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.12-v1.21 (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.5/troubleshooting.md b/site/content/docs/v1.5/troubleshooting.md index 1328e151d..4f20f2b5b 100644 --- a/site/content/docs/v1.5/troubleshooting.md +++ b/site/content/docs/v1.5/troubleshooting.md @@ -171,7 +171,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: restic.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.5/upgrade-to-1.5.md b/site/content/docs/v1.5/upgrade-to-1.5.md index 58c54ac9f..980fbfa56 100644 --- a/site/content/docs/v1.5/upgrade-to-1.5.md +++ b/site/content/docs/v1.5/upgrade-to-1.5.md @@ -14,7 +14,7 @@ If you're not yet running at least Velero v1.4, see the following: - [Upgrading to v1.3][3] - [Upgrading to v1.4][4] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions @@ -77,8 +77,8 @@ Before upgrading, check the [Velero compatibility matrix](https://github.com/vmw [2]: https://velero.io/docs/v1.2.0/upgrade-to-1.2/ [3]: https://velero.io/docs/v1.3.2/upgrade-to-1.3/ [4]: https://velero.io/docs/v1.4/upgrade-to-1.4/ -[5]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2 -[6]: https://github.com/vmware-tanzu/velero/issues/2077 -[7]: https://github.com/vmware-tanzu/velero/issues/2311 -[8]: https://github.com/vmware-tanzu/velero/releases/tag/v1.5.1 -[9]: https://github.com/vmware-tanzu/velero/releases/tag/v1.5.2 +[5]: https://github.com/velero-io/velero/releases/tag/v1.4.2 +[6]: https://github.com/velero-io/velero/issues/2077 +[7]: https://github.com/velero-io/velero/issues/2311 +[8]: https://github.com/velero-io/velero/releases/tag/v1.5.1 +[9]: https://github.com/velero-io/velero/releases/tag/v1.5.2 diff --git a/site/content/docs/v1.6/_index.md b/site/content/docs/v1.6/_index.md index 08c1f9fe2..c69404ab7 100644 --- a/site/content/docs/v1.6/_index.md +++ b/site/content/docs/v1.6/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.6/backup-hooks.md b/site/content/docs/v1.6/backup-hooks.md index 7218e03bc..6f661cf60 100644 --- a/site/content/docs/v1.6/backup-hooks.md +++ b/site/content/docs/v1.6/backup-hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.6.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.6/basic-install.md b/site/content/docs/v1.6/basic-install.md index 494ffd94e..0d3bfda94 100644 --- a/site/content/docs/v1.6/basic-install.md +++ b/site/content/docs/v1.6/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.12 or later, with DNS and container networking enabled. Note that Velero versions 1.6.0-1.6.2, only support Kubernetes versions v1.12-1.21. If you are installing on a newer version of Kubernetes, its recommended that you install a newer version of Velero. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatabilty-matrix). +- Access to a Kubernetes cluster, v1.12 or later, with DNS and container networking enabled. Note that Velero versions 1.6.0-1.6.2, only support Kubernetes versions v1.12-1.21. If you are installing on a newer version of Kubernetes, its recommended that you install a newer version of Velero. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatabilty-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.6/build-from-source.md b/site/content/docs/v1.6/build-from-source.md index df9f738cf..f8896882a 100644 --- a/site/content/docs/v1.6/build-from-source.md +++ b/site/content/docs/v1.6/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.6/code-standards.md b/site/content/docs/v1.6/code-standards.md index 99db78ad7..a7b2cd650 100644 --- a/site/content/docs/v1.6/code-standards.md +++ b/site/content/docs/v1.6/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.6.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.6/contributions/ibm-config.md b/site/content/docs/v1.6/contributions/ibm-config.md index 2622eedfc..14823cc03 100644 --- a/site/content/docs/v1.6/contributions/ibm-config.md +++ b/site/content/docs/v1.6/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.6/contributions/minio.md b/site/content/docs/v1.6/contributions/minio.md index df605d138..818881a88 100644 --- a/site/content/docs/v1.6/contributions/minio.md +++ b/site/content/docs/v1.6/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -290,6 +290,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.6/contributions/oracle-config.md b/site/content/docs/v1.6/contributions/oracle-config.md index d9b6fd7c9..ab78ce57c 100644 --- a/site/content/docs/v1.6/contributions/oracle-config.md +++ b/site/content/docs/v1.6/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.6/custom-plugins.md b/site/content/docs/v1.6/custom-plugins.md index 167584eb0..d7a70a2bc 100644 --- a/site/content/docs/v1.6/custom-plugins.md +++ b/site/content/docs/v1.6/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -112,6 +112,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.6.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.6.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.6/customize-installation.md b/site/content/docs/v1.6/customize-installation.md index 655adfcf8..be82861b8 100644 --- a/site/content/docs/v1.6/customize-installation.md +++ b/site/content/docs/v1.6/customize-installation.md @@ -356,13 +356,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.6.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.6/examples.md b/site/content/docs/v1.6/examples.md index 58a35fd5d..ea7213b33 100644 --- a/site/content/docs/v1.6/examples.md +++ b/site/content/docs/v1.6/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.6/image-tagging.md b/site/content/docs/v1.6/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.6/image-tagging.md +++ b/site/content/docs/v1.6/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.6/locations.md b/site/content/docs/v1.6/locations.md index 2f54077dd..17acb8dc9 100644 --- a/site/content/docs/v1.6/locations.md +++ b/site/content/docs/v1.6/locations.md @@ -250,8 +250,8 @@ velero backup-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.6/maintainers.md b/site/content/docs/v1.6/maintainers.md index 5e7071f55..85e017fb6 100644 --- a/site/content/docs/v1.6/maintainers.md +++ b/site/content/docs/v1.6/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.6.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.6.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.6/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.6/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.6.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.6.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.6.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.6/overview-plugins.md b/site/content/docs/v1.6/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.6/overview-plugins.md +++ b/site/content/docs/v1.6/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.6/plugin-release-instructions.md b/site/content/docs/v1.6/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.6/plugin-release-instructions.md +++ b/site/content/docs/v1.6/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.6/release-instructions.md b/site/content/docs/v1.6/release-instructions.md index 991ded976..883b3f762 100644 --- a/site/content/docs/v1.6/release-instructions.md +++ b/site/content/docs/v1.6/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.6.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.6.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -49,7 +49,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -73,11 +73,11 @@ For each major or minor release, create and publish a blog post to let folks kno 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.0.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.4.1`), note that the full `CHANGELOG-1.4.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -132,4 +132,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.6/restic.md b/site/content/docs/v1.6/restic.md index a15e08bf2..1feab8700 100644 --- a/site/content/docs/v1.6/restic.md +++ b/site/content/docs/v1.6/restic.md @@ -518,7 +518,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.6/start-contributing.md b/site/content/docs/v1.6/start-contributing.md index 772e85fb1..f226bc3f0 100644 --- a/site/content/docs/v1.6/start-contributing.md +++ b/site/content/docs/v1.6/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.6.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.6.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.6.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.6.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.6/supported-providers.md b/site/content/docs/v1.6/supported-providers.md index 5e75dc1e2..35b237fbe 100644 --- a/site/content/docs/v1.6/supported-providers.md +++ b/site/content/docs/v1.6/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | |-----------------------------------|---------------------|------------------------------|-----------------------------------------|-------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Community supported providers {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.6/tilt.md b/site/content/docs/v1.6/tilt.md index 42f68cfe4..18a0817e1 100644 --- a/site/content/docs/v1.6/tilt.md +++ b/site/content/docs/v1.6/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.12 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.6/troubleshooting.md b/site/content/docs/v1.6/troubleshooting.md index 7b035006f..bffc25fa0 100644 --- a/site/content/docs/v1.6/troubleshooting.md +++ b/site/content/docs/v1.6/troubleshooting.md @@ -207,7 +207,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: restic.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.6/upgrade-to-1.6.md b/site/content/docs/v1.6/upgrade-to-1.6.md index 84da0fccc..20ff3cfe9 100644 --- a/site/content/docs/v1.6/upgrade-to-1.6.md +++ b/site/content/docs/v1.6/upgrade-to-1.6.md @@ -15,7 +15,7 @@ If you're not yet running at least Velero v1.5, see the following: - [Upgrading to v1.4][4] - [Upgrading to v1.5][5] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions @@ -85,7 +85,7 @@ After upgrading, if there is a previously created backup storage location with t [3]: https://velero.io/docs/v1.3.2/upgrade-to-1.3/ [4]: https://velero.io/docs/v1.4/upgrade-to-1.4/ [5]: https://velero.io/docs/v1.5/upgrade-to-1.5 -[6]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2 -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[6]: https://github.com/velero-io/velero/releases/tag/v1.4.2 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: https://velero.io/docs/v1.6/locations diff --git a/site/content/docs/v1.7/_index.md b/site/content/docs/v1.7/_index.md index 2fdbc8f9a..8d7ff0e11 100644 --- a/site/content/docs/v1.7/_index.md +++ b/site/content/docs/v1.7/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.7/backup-hooks.md b/site/content/docs/v1.7/backup-hooks.md index 57176fa74..1117a37d9 100644 --- a/site/content/docs/v1.7/backup-hooks.md +++ b/site/content/docs/v1.7/backup-hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.7.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.7/basic-install.md b/site/content/docs/v1.7/basic-install.md index c74398745..b21bc80b4 100644 --- a/site/content/docs/v1.7/basic-install.md +++ b/site/content/docs/v1.7/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.12 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.12 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.7/build-from-source.md b/site/content/docs/v1.7/build-from-source.md index df9f738cf..f8896882a 100644 --- a/site/content/docs/v1.7/build-from-source.md +++ b/site/content/docs/v1.7/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.7/code-standards.md b/site/content/docs/v1.7/code-standards.md index 978107101..40797d822 100644 --- a/site/content/docs/v1.7/code-standards.md +++ b/site/content/docs/v1.7/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.7.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.7.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.7/contributions/ibm-config.md b/site/content/docs/v1.7/contributions/ibm-config.md index 4aaf823a2..f7f5eb0ae 100644 --- a/site/content/docs/v1.7/contributions/ibm-config.md +++ b/site/content/docs/v1.7/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.7/contributions/minio.md b/site/content/docs/v1.7/contributions/minio.md index 3c683473b..287480ef7 100644 --- a/site/content/docs/v1.7/contributions/minio.md +++ b/site/content/docs/v1.7/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-restic` to enable restic support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.7/contributions/oracle-config.md b/site/content/docs/v1.7/contributions/oracle-config.md index 8e2bae095..1e8907d33 100644 --- a/site/content/docs/v1.7/contributions/oracle-config.md +++ b/site/content/docs/v1.7/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.7/custom-plugins.md b/site/content/docs/v1.7/custom-plugins.md index 38bbb246e..d0b9798a5 100644 --- a/site/content/docs/v1.7/custom-plugins.md +++ b/site/content/docs/v1.7/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -112,6 +112,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.7.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.7.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.7/customize-installation.md b/site/content/docs/v1.7/customize-installation.md index 57dadb38c..313c0588a 100644 --- a/site/content/docs/v1.7/customize-installation.md +++ b/site/content/docs/v1.7/customize-installation.md @@ -356,13 +356,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.7.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.7/examples.md b/site/content/docs/v1.7/examples.md index 58a35fd5d..ea7213b33 100644 --- a/site/content/docs/v1.7/examples.md +++ b/site/content/docs/v1.7/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.7/image-tagging.md b/site/content/docs/v1.7/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.7/image-tagging.md +++ b/site/content/docs/v1.7/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.7/locations.md b/site/content/docs/v1.7/locations.md index 2f54077dd..17acb8dc9 100644 --- a/site/content/docs/v1.7/locations.md +++ b/site/content/docs/v1.7/locations.md @@ -250,8 +250,8 @@ velero backup-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.7/maintainers.md b/site/content/docs/v1.7/maintainers.md index 5c7c1f3d6..30f0306b0 100644 --- a/site/content/docs/v1.7/maintainers.md +++ b/site/content/docs/v1.7/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.7.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.7.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.7.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.7.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.7/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.7/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.7.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.7.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.7.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.7.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.7/overview-plugins.md b/site/content/docs/v1.7/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.7/overview-plugins.md +++ b/site/content/docs/v1.7/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.7/plugin-release-instructions.md b/site/content/docs/v1.7/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.7/plugin-release-instructions.md +++ b/site/content/docs/v1.7/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.7/release-instructions.md b/site/content/docs/v1.7/release-instructions.md index de601c585..909504f79 100644 --- a/site/content/docs/v1.7/release-instructions.md +++ b/site/content/docs/v1.7/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.7.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.7.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -75,7 +75,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -99,11 +99,11 @@ For each major or minor release, create and publish a blog post to let folks kno 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.0.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.4.1`), note that the full `CHANGELOG-1.4.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -158,4 +158,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.7/restic.md b/site/content/docs/v1.7/restic.md index 6fa1543db..b51e88cbb 100644 --- a/site/content/docs/v1.7/restic.md +++ b/site/content/docs/v1.7/restic.md @@ -518,7 +518,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.7/start-contributing.md b/site/content/docs/v1.7/start-contributing.md index a9f15f0fc..371ce5582 100644 --- a/site/content/docs/v1.7/start-contributing.md +++ b/site/content/docs/v1.7/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.7.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.7.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.7.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.7.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.7.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.7/supported-providers.md b/site/content/docs/v1.7/supported-providers.md index 7cbda31f7..3acb2752f 100644 --- a/site/content/docs/v1.7/supported-providers.md +++ b/site/content/docs/v1.7/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | |-----------------------------------|---------------------|------------------------------|-----------------------------------------|-------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Community supported providers {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.7/tilt.md b/site/content/docs/v1.7/tilt.md index 42f68cfe4..18a0817e1 100644 --- a/site/content/docs/v1.7/tilt.md +++ b/site/content/docs/v1.7/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.12 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.7/troubleshooting.md b/site/content/docs/v1.7/troubleshooting.md index 7b035006f..bffc25fa0 100644 --- a/site/content/docs/v1.7/troubleshooting.md +++ b/site/content/docs/v1.7/troubleshooting.md @@ -207,7 +207,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: restic.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.7/upgrade-to-1.7.md b/site/content/docs/v1.7/upgrade-to-1.7.md index 2e3a37907..2f1d44403 100644 --- a/site/content/docs/v1.7/upgrade-to-1.7.md +++ b/site/content/docs/v1.7/upgrade-to-1.7.md @@ -16,7 +16,7 @@ If you're not yet running at least Velero v1.6, see the following: - [Upgrading to v1.5][5] - [Upgrading to v1.6][6] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions @@ -93,5 +93,5 @@ After upgrading, if there is a previously created backup storage location with t [5]: https://velero.io/docs/v1.5/upgrade-to-1.5 [6]: https://velero.io/docs/v1.6/upgrade-to-1.6 [9]: https://velero.io/docs/v1.7/locations -[10]: https://github.com/vmware-tanzu/velero/issues/2077 -[11]: https://github.com/vmware-tanzu/velero/issues/2311 +[10]: https://github.com/velero-io/velero/issues/2077 +[11]: https://github.com/velero-io/velero/issues/2311 diff --git a/site/content/docs/v1.8/_index.md b/site/content/docs/v1.8/_index.md index d4a88da6a..11d0fe336 100644 --- a/site/content/docs/v1.8/_index.md +++ b/site/content/docs/v1.8/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.8/backup-hooks.md b/site/content/docs/v1.8/backup-hooks.md index de6a58c53..50b3c416b 100644 --- a/site/content/docs/v1.8/backup-hooks.md +++ b/site/content/docs/v1.8/backup-hooks.md @@ -88,5 +88,5 @@ To use multiple commands, wrap your target command in a shell and separate them [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.8.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.8/basic-install.md b/site/content/docs/v1.8/basic-install.md index 07c4ef687..c03e0f058 100644 --- a/site/content/docs/v1.8/basic-install.md +++ b/site/content/docs/v1.8/basic-install.md @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.8/build-from-source.md b/site/content/docs/v1.8/build-from-source.md index df9f738cf..f8896882a 100644 --- a/site/content/docs/v1.8/build-from-source.md +++ b/site/content/docs/v1.8/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.8/code-standards.md b/site/content/docs/v1.8/code-standards.md index 22a2261d5..c22fec066 100644 --- a/site/content/docs/v1.8/code-standards.md +++ b/site/content/docs/v1.8/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.8.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.8.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.8/contributions/ibm-config.md b/site/content/docs/v1.8/contributions/ibm-config.md index 4aaf823a2..f7f5eb0ae 100644 --- a/site/content/docs/v1.8/contributions/ibm-config.md +++ b/site/content/docs/v1.8/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.8/contributions/minio.md b/site/content/docs/v1.8/contributions/minio.md index 3c683473b..287480ef7 100644 --- a/site/content/docs/v1.8/contributions/minio.md +++ b/site/content/docs/v1.8/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-restic` to enable restic support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.8/contributions/oracle-config.md b/site/content/docs/v1.8/contributions/oracle-config.md index b348091ca..8c8b4c2be 100644 --- a/site/content/docs/v1.8/contributions/oracle-config.md +++ b/site/content/docs/v1.8/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.8/custom-plugins.md b/site/content/docs/v1.8/custom-plugins.md index e84ee777f..e584c1dd7 100644 --- a/site/content/docs/v1.8/custom-plugins.md +++ b/site/content/docs/v1.8/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -116,6 +116,6 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/pkg/plugin/logger.go -[3]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/pkg/restore/restic_restore_action.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.8.0/pkg/plugin/logger.go +[3]: https://github.com/velero-io/velero/blob/v1.8.0/pkg/restore/restic_restore_action.go diff --git a/site/content/docs/v1.8/customize-installation.md b/site/content/docs/v1.8/customize-installation.md index 3b25817df..4314fe569 100644 --- a/site/content/docs/v1.8/customize-installation.md +++ b/site/content/docs/v1.8/customize-installation.md @@ -354,11 +354,11 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.8.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.8/examples.md b/site/content/docs/v1.8/examples.md index 58a35fd5d..ea7213b33 100644 --- a/site/content/docs/v1.8/examples.md +++ b/site/content/docs/v1.8/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.8/image-tagging.md b/site/content/docs/v1.8/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.8/image-tagging.md +++ b/site/content/docs/v1.8/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.8/locations.md b/site/content/docs/v1.8/locations.md index 2f54077dd..17acb8dc9 100644 --- a/site/content/docs/v1.8/locations.md +++ b/site/content/docs/v1.8/locations.md @@ -250,8 +250,8 @@ velero backup-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.8/maintainers.md b/site/content/docs/v1.8/maintainers.md index 01faab1af..bc83e2bc7 100644 --- a/site/content/docs/v1.8/maintainers.md +++ b/site/content/docs/v1.8/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.8.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.8.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.8.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.8.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.8.0/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.8.0/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.8.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.8.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.8.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.8.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.8/overview-plugins.md b/site/content/docs/v1.8/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.8/overview-plugins.md +++ b/site/content/docs/v1.8/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.8/plugin-release-instructions.md b/site/content/docs/v1.8/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.8/plugin-release-instructions.md +++ b/site/content/docs/v1.8/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.8/release-instructions.md b/site/content/docs/v1.8/release-instructions.md index 43e2e632a..75454cc40 100644 --- a/site/content/docs/v1.8/release-instructions.md +++ b/site/content/docs/v1.8/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.8.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.8.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -75,7 +75,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -86,7 +86,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -105,11 +105,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.0.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.4.1`), note that the full `CHANGELOG-1.4.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.2.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -164,4 +164,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.8/restic.md b/site/content/docs/v1.8/restic.md index a15e08bf2..1feab8700 100644 --- a/site/content/docs/v1.8/restic.md +++ b/site/content/docs/v1.8/restic.md @@ -518,7 +518,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.8/start-contributing.md b/site/content/docs/v1.8/start-contributing.md index c7a72b1f5..26daf5f01 100644 --- a/site/content/docs/v1.8/start-contributing.md +++ b/site/content/docs/v1.8/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.8.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.8.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.8.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.8.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.8.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.8/supported-providers.md b/site/content/docs/v1.8/supported-providers.md index 5e75dc1e2..35b237fbe 100644 --- a/site/content/docs/v1.8/supported-providers.md +++ b/site/content/docs/v1.8/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | |-----------------------------------|---------------------|------------------------------|-----------------------------------------|-------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | Google Cloud Storage| Google Compute Engine Disks | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Community supported providers {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.8/tilt.md b/site/content/docs/v1.8/tilt.md index 42f68cfe4..18a0817e1 100644 --- a/site/content/docs/v1.8/tilt.md +++ b/site/content/docs/v1.8/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.12 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.8/troubleshooting.md b/site/content/docs/v1.8/troubleshooting.md index cdfd25305..249f26823 100644 --- a/site/content/docs/v1.8/troubleshooting.md +++ b/site/content/docs/v1.8/troubleshooting.md @@ -208,7 +208,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: restic.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.8/upgrade-to-1.8.md b/site/content/docs/v1.8/upgrade-to-1.8.md index 3a1e80cf5..a1ebe8b23 100644 --- a/site/content/docs/v1.8/upgrade-to-1.8.md +++ b/site/content/docs/v1.8/upgrade-to-1.8.md @@ -17,7 +17,7 @@ If you're not yet running at least Velero v1.6, see the following: - [Upgrading to v1.6][6] - [Upgrading to v1.7][7] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatabilty-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/docs/v1.9/_index.md b/site/content/docs/v1.9/_index.md index 376b5196e..bc1be8b70 100644 --- a/site/content/docs/v1.9/_index.md +++ b/site/content/docs/v1.9/_index.md @@ -39,11 +39,11 @@ If you are ready to jump in and test, add code, or help with documentation, foll See [the list of releases][6] to find out about feature changes. -[1]: https://github.com/vmware-tanzu/velero/workflows/Main%20CI/badge.svg -[2]: https://github.com/vmware-tanzu/velero/actions?query=workflow%3A"Main+CI" +[1]: https://github.com/velero-io/velero/workflows/Main%20CI/badge.svg +[2]: https://github.com/velero-io/velero/actions?query=workflow%3A"Main+CI" -[4]: https://github.com/vmware-tanzu/velero/issues -[6]: https://github.com/vmware-tanzu/velero/releases +[4]: https://github.com/velero-io/velero/issues +[6]: https://github.com/velero-io/velero/releases [9]: https://kubernetes.io/docs/setup/ [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos diff --git a/site/content/docs/v1.9/backup-hooks.md b/site/content/docs/v1.9/backup-hooks.md index e2c5b1eb4..90a957173 100644 --- a/site/content/docs/v1.9/backup-hooks.md +++ b/site/content/docs/v1.9/backup-hooks.md @@ -107,5 +107,5 @@ Note that the container must support the shell command you use. [1]: api-types/backup.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/examples/nginx-app/with-pv.yaml +[2]: https://github.com/velero-io/velero/blob/v1.9.0/examples/nginx-app/with-pv.yaml [3]: cloud-common.md diff --git a/site/content/docs/v1.9/backup-reference.md b/site/content/docs/v1.9/backup-reference.md index b0eddab29..02c02a404 100644 --- a/site/content/docs/v1.9/backup-reference.md +++ b/site/content/docs/v1.9/backup-reference.md @@ -72,7 +72,7 @@ By this way, schedule is the owner of it created backups. This is useful for som Please do notice there is also side effect that may not be expected. Because schedule is the owner, when the schedule is deleted, the related backups CR (Just backup CR is deleted. Backup data still exists in object store and snapshots) will be deleted by k8s GC controller, too, but Velero controller will sync these backups from object store's metadata into k8s. Then k8s GC controller and Velero controller will fight over whether these backups should exist all through. -If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/vmware-tanzu/velero/issues/4093). +If there is possibility the schedule will be disable to not create backup anymore, and the created backups are still useful. Please do not enable this option. For detail, please reference to [Backups created by a schedule with useOwnerReferenceInBackup set do not get synced properly](https://github.com/velero-io/velero/issues/4093). ## Kubernetes API Pagination diff --git a/site/content/docs/v1.9/basic-install.md b/site/content/docs/v1.9/basic-install.md index db54dcc55..f6dc81ebf 100644 --- a/site/content/docs/v1.9/basic-install.md +++ b/site/content/docs/v1.9/basic-install.md @@ -8,7 +8,7 @@ Refer [this document](customize-installation.md) to customize your installation. ## Prerequisites -- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +- Access to a Kubernetes cluster, v1.16 or later, with DNS and container networking enabled. For more information on supported Kubernetes versions, see the Velero [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). - `kubectl` installed locally Velero uses object storage to store backups and associated artifacts. It also optionally integrates with supported block storage systems to snapshot your persistent volumes. Before beginning the installation process, you should identify the object storage provider and optional block storage provider(s) you'll be using from the list of [compatible providers][0]. @@ -66,7 +66,7 @@ _Note: if your object storage provider is different than your volume snapshot pr Please refer to [this part of the documentation][5]. [0]: supported-providers.md -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: on-premises.md [3]: overview-plugins.md [4]: customize-installation.md#install-an-additional-volume-snapshot-provider diff --git a/site/content/docs/v1.9/build-from-source.md b/site/content/docs/v1.9/build-from-source.md index df9f738cf..f8896882a 100644 --- a/site/content/docs/v1.9/build-from-source.md +++ b/site/content/docs/v1.9/build-from-source.md @@ -17,7 +17,7 @@ layout: docs ```bash mkdir $HOME/go export GOPATH=$HOME/go -go get github.com/vmware-tanzu/velero +go get github.com/velero-io/velero ``` Where `go` is your [import path][4] for Go. @@ -26,7 +26,7 @@ For Go development, it is recommended to add the Go import path (`$HOME/go` in t ### Option 2) Release archive -Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/vmware-tanzu/velero`. +Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/velero-io/velero`. Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below. @@ -194,7 +194,7 @@ kubectl -n velero delete pods -l deploy=velero [4]: https://blog.golang.org/organizing-go-code [5]: https://golang.org/doc/install -[22]: https://github.com/vmware-tanzu/velero/releases +[22]: https://github.com/velero-io/velero/releases [23]: https://docs.docker.com/buildx/working-with-buildx/ [24]: https://github.com/docker/buildx [25]: https://github.com/moby/moby/pull/38738 diff --git a/site/content/docs/v1.9/code-standards.md b/site/content/docs/v1.9/code-standards.md index ed82aaf15..130203e96 100644 --- a/site/content/docs/v1.9/code-standards.md +++ b/site/content/docs/v1.9/code-standards.md @@ -62,15 +62,15 @@ Example: corev1client "k8s.io/client-go/kubernetes/typed/core/v1" corev1listers "k8s.io/client-go/listers/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov1client "github.com/vmware-tanzu/velero/pkg/generated/clientset/versioned/typed/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1client "github.com/velero-io/velero/pkg/generated/clientset/versioned/typed/velero/v1" ) ## Mocks We use a package to generate mocks for our interfaces. -Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.9.0/pkg/restic/mocks/restorer.go +Example: if you want to change this mock: https://github.com/velero-io/velero/blob/v1.9.0/pkg/restic/mocks/restorer.go Run: diff --git a/site/content/docs/v1.9/contributions/ibm-config.md b/site/content/docs/v1.9/contributions/ibm-config.md index b551bc1a7..ecd522606 100644 --- a/site/content/docs/v1.9/contributions/ibm-config.md +++ b/site/content/docs/v1.9/contributions/ibm-config.md @@ -14,9 +14,9 @@ To set up IBM Cloud Object Storage (COS) as Velero's destination, you: ## Download Velero -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ diff --git a/site/content/docs/v1.9/contributions/minio.md b/site/content/docs/v1.9/contributions/minio.md index 3c683473b..287480ef7 100644 --- a/site/content/docs/v1.9/contributions/minio.md +++ b/site/content/docs/v1.9/contributions/minio.md @@ -34,9 +34,9 @@ brew install velero ### Option 2: GitHub release -1. Download the [latest official release's](https://github.com/vmware-tanzu/velero/releases) tarball for your client platform. +1. Download the [latest official release's](https://github.com/velero-io/velero/releases) tarball for your client platform. - _We strongly recommend that you use an [official release](https://github.com/vmware-tanzu/velero/releases) of + _We strongly recommend that you use an [official release](https://github.com/velero-io/velero/releases) of Velero. The tarballs for each release contain the `velero` command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable!_ @@ -81,7 +81,7 @@ These instructions start the Velero server and a Minio instance that is accessib --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000 ``` - This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/vmware-tanzu/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. + This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no `VolumeSnapshotLocation` is created (`--use-volume-snapshots=false`). You may need to update AWS plugin version to one that is [compatible](https://github.com/velero-io/velero-plugin-for-aws#compatibility) with the version of Velero you are installing. Additionally, you can specify `--use-restic` to enable restic support, and `--wait` to wait for the deployment to be ready. @@ -291,6 +291,6 @@ In this case: [3]: ../customize-installation.md [17]: ../restic.md [18]: ../debugging-restores.md -[26]: https://github.com/vmware-tanzu/velero/releases +[26]: https://github.com/velero-io/velero/releases [30]: https://godoc.org/github.com/robfig/cron [32]: ../self-signed-certificates.md diff --git a/site/content/docs/v1.9/contributions/oracle-config.md b/site/content/docs/v1.9/contributions/oracle-config.md index 558e6232a..c74f36f78 100644 --- a/site/content/docs/v1.9/contributions/oracle-config.md +++ b/site/content/docs/v1.9/contributions/oracle-config.md @@ -17,10 +17,10 @@ layout: docs ## Download Velero -1. Download the [latest release](https://github.com/vmware-tanzu/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: +1. Download the [latest release](https://github.com/velero-io/velero/releases/) of Velero to your development environment. This includes the `velero` CLI utility and example Kubernetes manifest files. For example: ``` - wget https://github.com/vmware-tanzu/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz + wget https://github.com/velero-io/velero/releases/download/v1.0.0/velero-v1.0.0-linux-amd64.tar.gz ``` **NOTE:** Its strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. The code in the main branch of the Velero repository is under active development and is not guaranteed to be stable! diff --git a/site/content/docs/v1.9/csi.md b/site/content/docs/v1.9/csi.md index c66077603..aa41bee7b 100644 --- a/site/content/docs/v1.9/csi.md +++ b/site/content/docs/v1.9/csi.md @@ -68,7 +68,7 @@ When the Velero backup expires, the VolumeSnapshot objects will be deleted and t For more details on how each plugin works, see the [CSI plugin repo][2]'s documentation. -**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws), [Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/vmware-tanzu/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. +**Note:** The AWS, Microsoft Azure, and Google Cloud Platform (GCP) Velero plugins version 1.4 and later are able to snapshot and restore persistent volumes provisioned by a CSI driver via the APIs of the cloud provider, without having to install Velero CSI plugins. See the [AWS](https://github.com/velero-io/velero-plugin-for-aws), [Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure), and [Google Cloud Platform (GCP)](https://github.com/velero-io/velero-plugin-for-gcp) Velero plugin repo for more information on supported CSI drivers. [1]: customize-installation.md#enable-server-side-features [2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ diff --git a/site/content/docs/v1.9/custom-plugins.md b/site/content/docs/v1.9/custom-plugins.md index 403f60d4a..219b82cfd 100644 --- a/site/content/docs/v1.9/custom-plugins.md +++ b/site/content/docs/v1.9/custom-plugins.md @@ -47,7 +47,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the - example-with-dash.io/azure ``` -You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: +You will need to give your plugin(s) the full name when registering them by calling the appropriate `RegisterX` function: ## Plugin Kinds @@ -111,5 +111,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime. -[1]: https://github.com/vmware-tanzu/velero-plugin-example -[2]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/pkg/plugin/logger.go +[1]: https://github.com/velero-io/velero-plugin-example +[2]: https://github.com/velero-io/velero/blob/v1.9.0/pkg/plugin/logger.go diff --git a/site/content/docs/v1.9/customize-installation.md b/site/content/docs/v1.9/customize-installation.md index 9cf00f054..4a8858f9c 100644 --- a/site/content/docs/v1.9/customize-installation.md +++ b/site/content/docs/v1.9/customize-installation.md @@ -378,13 +378,13 @@ If you get an error like `complete:13: command not found: compdef`, then add the compinit ``` -[1]: https://github.com/vmware-tanzu/velero/releases/latest +[1]: https://github.com/velero-io/velero/releases/latest [2]: namespace.md [3]: restic.md [4]: on-premises.md [6]: velero-install.md#usage -[7]: https://github.com/vmware-tanzu/velero/issues/2077 -[8]: https://github.com/vmware-tanzu/velero/issues/2311 +[7]: https://github.com/velero-io/velero/issues/2077 +[8]: https://github.com/velero-io/velero/issues/2311 [9]: self-signed-certificates.md [10]: csi.md -[11]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/pkg/apis/velero/v1/constants.go +[11]: https://github.com/velero-io/velero/blob/v1.9.0/pkg/apis/velero/v1/constants.go diff --git a/site/content/docs/v1.9/examples.md b/site/content/docs/v1.9/examples.md index 58a35fd5d..ea7213b33 100644 --- a/site/content/docs/v1.9/examples.md +++ b/site/content/docs/v1.9/examples.md @@ -5,7 +5,7 @@ layout: docs After you set up the Velero server, you can clone the examples used in the following sections by running the following: ``` -git clone https://github.com/vmware-tanzu/velero.git +git clone https://github.com/velero-io/velero.git cd velero ``` diff --git a/site/content/docs/v1.9/image-tagging.md b/site/content/docs/v1.9/image-tagging.md index 64e9310b5..df2898e27 100644 --- a/site/content/docs/v1.9/image-tagging.md +++ b/site/content/docs/v1.9/image-tagging.md @@ -9,7 +9,7 @@ This document describes Velero's image tagging policy. `velero/velero:` -Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/vmware-tanzu/velero` repository has a matching image, `velero/velero:v1.0.0`. +Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/velero-io/velero` repository has a matching image, `velero/velero:v1.0.0`. ### Latest diff --git a/site/content/docs/v1.9/locations.md b/site/content/docs/v1.9/locations.md index d5dbc710a..36ca15c29 100644 --- a/site/content/docs/v1.9/locations.md +++ b/site/content/docs/v1.9/locations.md @@ -252,8 +252,8 @@ velero backup-location set \ [1]: api-types/backupstoragelocation.md [2]: api-types/volumesnapshotlocation.md -[3]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md -[4]: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md +[3]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md +[4]: https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md [5]: /plugins [6]: overview-plugins.md [7]: https://kubernetes.io/docs/concepts/configuration/secret/ diff --git a/site/content/docs/v1.9/maintainers.md b/site/content/docs/v1.9/maintainers.md index c100601a3..a016657a1 100644 --- a/site/content/docs/v1.9/maintainers.md +++ b/site/content/docs/v1.9/maintainers.md @@ -4,7 +4,7 @@ layout: docs toc: "true" --- -There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.9.0/GOVERNANCE.md#code-repositories). +There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/velero-io/velero/blob/v1.9.0/GOVERNANCE.md#code-repositories). Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section. @@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta - As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them) - Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work. - There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc). -- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.9.0/GOVERNANCE.md#lazy-consensus) policy for the project. +- Be familiar with the [lazy consensus](https://github.com/velero-io/velero/blob/v1.9.0/GOVERNANCE.md#lazy-consensus) policy for the project. Some tips for doing reviews: - There are some [code standards and general guidelines](https://velero.io/docs/v1.9/code-standards) we aim for - We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.9/style-guide/) -- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.9.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder. +- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/velero-io/velero/blob/v1.9.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/velero-io/velero/tree/main/design/implemented) folder. ## Creating a release @@ -34,4 +34,4 @@ Maintainers are expected to participate in the community support rotation. We ha Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page. ## How do I become a maintainer? -The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.9.0/GOVERNANCE.md#maintainers) is decided. +The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/velero-io/velero/blob/v1.9.0/GOVERNANCE.md#maintainers) is decided. diff --git a/site/content/docs/v1.9/migration-case.md b/site/content/docs/v1.9/migration-case.md index 163b3fba9..635d7d893 100644 --- a/site/content/docs/v1.9/migration-case.md +++ b/site/content/docs/v1.9/migration-case.md @@ -19,7 +19,7 @@ Before migrating you should consider the following, ## Migration Scenario -This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws). +This scenario steps through the migration of resources from Cluster 1 to Cluster 2. In this scenario, both clusters are using the same cloud provider, AWS, and Velero's [AWS plugin](https://github.com/velero-io/velero-plugin-for-aws). 1. On Cluster 1, make sure Velero is installed and points to an object storage location using the `--bucket` flag. diff --git a/site/content/docs/v1.9/overview-plugins.md b/site/content/docs/v1.9/overview-plugins.md index 037601d51..a1da43b6a 100644 --- a/site/content/docs/v1.9/overview-plugins.md +++ b/site/content/docs/v1.9/overview-plugins.md @@ -23,7 +23,7 @@ After you publish your plugin on your own repository, open a PR that adds a link You can also add the [`velero-plugin` GitHub Topic][4] to your repo, and it will be shown under the aggregated list of repositories automatically. -[1]: https://github.com/vmware-tanzu/velero-plugin-example/ +[1]: https://github.com/velero-io/velero-plugin-example/ [2]: custom-plugins.md [3]: supported-providers.md [4]: https://github.com/topics/velero-plugin diff --git a/site/content/docs/v1.9/plugin-release-instructions.md b/site/content/docs/v1.9/plugin-release-instructions.md index 4323d8c9a..46494cac9 100644 --- a/site/content/docs/v1.9/plugin-release-instructions.md +++ b/site/content/docs/v1.9/plugin-release-instructions.md @@ -26,5 +26,5 @@ Plugins the Velero core team is responsible include all those listed in [the Vel 1. If all e2e tests pass, go to the GitHub release page of the plugin (`https://github.com/vmware-tanzu//releases`) and manually create a release for the new tag. 1. Copy and paste the content of the new changelog file into the release description field. -[1]: https://github.com/vmware-tanzu/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 -[2]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[1]: https://github.com/velero-io/velero/blob/c8dfd648bbe85db0184ea53296de4220895497e6/test/e2e/velero_utils.go#L27 +[2]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.9/release-instructions.md b/site/content/docs/v1.9/release-instructions.md index 94d77f4d5..1a43ea47f 100644 --- a/site/content/docs/v1.9/release-instructions.md +++ b/site/content/docs/v1.9/release-instructions.md @@ -7,9 +7,9 @@ This page covers the steps to perform when releasing a new version of Velero. ## General notes - Please read the documented variables in each script to understand what they are for and how to properly format their values. -- You will need to have an upstream remote configured to use to the [vmware-tanzu/velero](https://github.com/vmware-tanzu/velero) repository. +- You will need to have an upstream remote configured to use to the [velero-io/velero](https://github.com/velero-io/velero) repository. You can check this using `git remote -v`. - The release script ([`tag-release.sh`](https://github.com/vmware-tanzu/velero/blob/v1.9.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. + The release script ([`tag-release.sh`](https://github.com/velero-io/velero/blob/v1.9.0/hack/release-tools/tag-release.sh)) will use `upstream` as the default remote name if it is not specified using the environment variable `REMOTE`. - GA release: major and minor releases only. Example: 1.0 (major), 1.5 (minor). - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release. @@ -75,7 +75,7 @@ For each major or minor release, create and publish a blog post to let folks kno - Remove the pre-release docs table of contents mapping entry from `site/data/toc-mapping.yml`. - Remove all references to the pre-release docs from `site/config.yml`. 1. Create the "Upgrade to $major.minor" page if it does not already exist ([example](https://velero.io/docs/v1.5/upgrade-to-1.5/)). - If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/vmware-tanzu/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). + If it already exists, update any usage of the previous version string within this file to use the new version string instead ([example](https://github.com/velero-io/velero/pull/2941/files#diff-d594f8fd0901fed79c39aab4b348193d)). This needs to be done in both the versioned and the `main` folders. 1. Review and submit PR - Follow the additional instructions at `site/README-HUGO.md` to complete the docs generation process. @@ -86,7 +86,7 @@ For each major or minor release, create and publish a blog post to let folks kno The image of velero is built based on [Distroless docker image](https://github.com/GoogleContainerTools/distroless). For the reproducibility of the release, before the release candidate is tagged, we need to make sure the in the Dockerfile on the release branch, the base image is referenced by digest, such as -https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 +https://github.com/velero-io/velero/blob/release-1.7/Dockerfile#L53-L54 ## Velero release ### Notes @@ -106,11 +106,11 @@ https://github.com/vmware-tanzu/velero/blob/release-1.7/Dockerfile#L53-L54 1. Create a tagged release and push it to GitHub - Run `VELERO_VERSION=v1.9.0-rc.1 REMOTE= GITHUB_TOKEN=REDACTED ON_RELEASE_BRANCH=TRUE ./hack/release-tools/tag-release.sh publish`. 1. Publish the release - - Navigate to the draft GitHub release at https://github.com/vmware-tanzu/velero/releases and edit the release. + - Navigate to the draft GitHub release at https://github.com/velero-io/velero/releases and edit the release. - If this is a patch release (e.g. `v1.9.1`), note that the full `CHANGELOG-1.9.md` contents will be included in the body of the GitHub release. You need to delete the previous releases' content (e.g. `v1.9.0`'s changelog) so that only the latest patch release's changelog shows. - Do a quick review for formatting. - **Note:** the `goreleaser` process should have detected if it's a pre-release version and, if so, checked the box at the bottom of the GitHub release page appropriately, but it's always worth double-checking. - - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/vmware-tanzu/velero/actions + - Verify that GitHub has built and pushed all the images (it takes a while): https://github.com/velero-io/velero/actions - Verify that the images are on Docker Hub: https://hub.docker.com/r/velero/velero/tags - Verify that the assets were published to the GitHub release - Publish the release. @@ -174,4 +174,4 @@ What to include: [1]: https://velero.io/blog [2]: website-guidelines.md -[3]: https://github.com/vmware-tanzu/velero/tree/main/test/e2e +[3]: https://github.com/velero-io/velero/tree/main/test/e2e diff --git a/site/content/docs/v1.9/restic.md b/site/content/docs/v1.9/restic.md index c1cd8aeb3..12e31e85c 100644 --- a/site/content/docs/v1.9/restic.md +++ b/site/content/docs/v1.9/restic.md @@ -539,7 +539,7 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch [1]: https://github.com/restic/restic [2]: customize-installation.md#enable-restic-integration -[3]: https://github.com/vmware-tanzu/velero/releases/ +[3]: https://github.com/velero-io/velero/releases/ [4]: https://kubernetes.io/docs/concepts/storage/volumes/#local [5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology [6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation diff --git a/site/content/docs/v1.9/self-signed-certificates.md b/site/content/docs/v1.9/self-signed-certificates.md index 2aab5c1b9..9120bd89d 100644 --- a/site/content/docs/v1.9/self-signed-certificates.md +++ b/site/content/docs/v1.9/self-signed-certificates.md @@ -52,7 +52,7 @@ You will need to change this setting on the server to make it work. **Note:** The `--insecure-skip-tls-verify` flag is insecure and susceptible to man-in-the-middle attacks and meant to help your testing and developing scenarios in an on-premise environment. Using this flag in production is not recommended. -Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws) or [Restic](restic.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, +Velero provides a way for you to skip TLS verification on the object store when using the [AWS provider plugin](https://github.com/velero-io/velero-plugin-for-aws) or [Restic](restic.md) by passing the `--insecure-skip-tls-verify` flag with the following Velero commands, * velero backup describe * velero backup download diff --git a/site/content/docs/v1.9/start-contributing.md b/site/content/docs/v1.9/start-contributing.md index 2199550b8..fa911d9e1 100644 --- a/site/content/docs/v1.9/start-contributing.md +++ b/site/content/docs/v1.9/start-contributing.md @@ -16,7 +16,7 @@ To make a design pull request, you can copy the template found in the `design/_t ## Finding your way around -You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. +You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of in progress new designs here: https://github.com/velero-io/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input. You can also vote on issues using :+1: and :-1:, as explained in our [Feature enhancement request][3] and [Bug issue][4] templates. This will help us quantify importance and prioritize issues. @@ -28,7 +28,7 @@ Please browse our list of resources, including a playlist of past online communi If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`. -[1]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/CODE_OF_CONDUCT.md -[2]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/CONTRIBUTING.md -[3]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md -[4]: https://github.com/vmware-tanzu/velero/blob/v1.9.0/.github/ISSUE_TEMPLATE/bug_report.md +[1]: https://github.com/velero-io/velero/blob/v1.9.0/CODE_OF_CONDUCT.md +[2]: https://github.com/velero-io/velero/blob/v1.9.0/CONTRIBUTING.md +[3]: https://github.com/velero-io/velero/blob/v1.9.0/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +[4]: https://github.com/velero-io/velero/blob/v1.9.0/.github/ISSUE_TEMPLATE/bug_report.md diff --git a/site/content/docs/v1.9/support-process.md b/site/content/docs/v1.9/support-process.md index 30c6a8844..dd7343755 100644 --- a/site/content/docs/v1.9/support-process.md +++ b/site/content/docs/v1.9/support-process.md @@ -6,7 +6,7 @@ layout: docs Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue. -For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/vmware-tanzu/velero/blob/v1.9.0/README.md#velero-compatibility-matrix). +For more information about Velero testing and supported Kubernetes versions, see Velero's [compatibility matrix](https://github.com/velero-io/velero/blob/v1.9.0/README.md#velero-compatibility-matrix). ## Weekly Rotation diff --git a/site/content/docs/v1.9/supported-providers.md b/site/content/docs/v1.9/supported-providers.md index 834c895f6..c8ebc0edc 100644 --- a/site/content/docs/v1.9/supported-providers.md +++ b/site/content/docs/v1.9/supported-providers.md @@ -11,14 +11,14 @@ Velero supports a variety of storage providers for different backup and snapshot | Provider | Object Store | Volume Snapshotter | Plugin Provider Repo | Setup Instructions | Parameters | |-----------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | -| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | -| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | -| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | AWS S3 | AWS EBS | [Velero plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws) | [AWS Plugin Setup](https://github.com/velero-io/velero-plugin-for-aws#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-aws/blob/main/volumesnapshotlocation.md) | +| [Google Cloud Platform (GCP)](https://cloud.google.com) | [Google Cloud Storage](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md) | [Google Compute Engine Disks](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | [Velero plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp) | [GCP Plugin Setup](https://github.com/velero-io/velero-plugin-for-gcp#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-gcp/blob/main/volumesnapshotlocation.md) | +| [Microsoft Azure](https://azure.com) | Azure Blob Storage | Azure Managed Disks | [Velero plugin for Microsoft Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure) | [Azure Plugin Setup](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup) | [BackupStorageLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md)
[VolumeSnapshotLocation](https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/volumesnapshotlocation.md) | +| [VMware vSphere](https://www.vmware.com/ca/products/vsphere.html) | 🚫 | vSphere Volumes | [VMware vSphere](https://github.com/velero-io/velero-plugin-for-vsphere) | [vSphere Plugin Setup](https://github.com/velero-io/velero-plugin-for-vsphere#velero-plugin-for-vsphere-installation-and-configuration-details) | 🚫 | | [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | {{< /table >}} -Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/vmware-tanzu/velero/issues) +Contact: [#Velero Slack](https://kubernetes.slack.com/messages/velero), [GitHub Issues](https://github.com/velero-io/velero/issues) ## Provider plugins maintained by the Velero community {{< table caption="Community supported providers" >}} @@ -62,9 +62,9 @@ In the case you want to take volume snapshots but didn't find a plugin for your [3]: contributions/minio.md [4]: https://github.com/StackPointCloud/ark-plugin-digitalocean [5]: http://www.noobaa.com/ -[6]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/backupstoragelocation.md +[6]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/backupstoragelocation.md [7]: contributions/tencent-config.md [25]: https://github.com/hpe-storage/velero-plugin [30]: restic.md -[36]: https://github.com/vmware-tanzu/velero-plugin-for-gcp#setup +[36]: https://github.com/velero-io/velero-plugin-for-gcp#setup [38]: https://www.cloudian.com/ diff --git a/site/content/docs/v1.9/tilt.md b/site/content/docs/v1.9/tilt.md index 3f2a8d90e..688041227 100644 --- a/site/content/docs/v1.9/tilt.md +++ b/site/content/docs/v1.9/tilt.md @@ -21,7 +21,7 @@ files in this directory are gitignored so you may configure your setup according 1. [Docker](https://docs.docker.com/install/) v19.03 or newer 1. A Kubernetes cluster v1.16 or greater (does not have to be Kind) 1. [Tilt](https://docs.tilt.dev/install.html) v0.12.0 or newer -1. Clone the [Velero project](https://github.com/vmware-tanzu/velero) repository +1. Clone the [Velero project](https://github.com/velero-io/velero) repository locally 1. Access to an S3 object storage 1. Clone any [provider plugin(s)](https://velero.io/plugins/) you want to make changes to and deploy (optional, must be configured to be deployed by the Velero Tilt's setup, [more info below](#provider-plugins)) @@ -115,7 +115,7 @@ Below are some ways to configure a backup storage location for Velero. Follow the provider documentation to provision the storage. We have a [list of all known object storage providers](supported-providers/) with corresponding plugins for Velero. #### Using MinIO as an object storage -Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/vmware-tanzu/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: +Note: to use MinIO as an object storage, you will need to use the [`AWS` plugin](https://github.com/velero-io/velero-plugin-for-aws), and configure the storage location with the `spec.provider` set to `aws` and the `spec.config.region` set to `minio`. Example: ``` spec: config: @@ -141,7 +141,7 @@ necessary to expose MinIO outside the cluster. 1) As a standalone MinIO instance running locally in a Docker container - See [these instructions](https://github.com/vmware-tanzu/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. + See [these instructions](https://github.com/velero-io/velero/discussions/3381) to run MinIO locally on your computer, as a standalone as opposed to running it on a Pod. Please see our [locations documentation](locations/) to learn more how backup locations work. diff --git a/site/content/docs/v1.9/troubleshooting.md b/site/content/docs/v1.9/troubleshooting.md index cdfd25305..249f26823 100644 --- a/site/content/docs/v1.9/troubleshooting.md +++ b/site/content/docs/v1.9/troubleshooting.md @@ -208,7 +208,7 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre [1]: debugging-restores.md [2]: debugging-install.md [3]: restic.md -[4]: https://github.com/vmware-tanzu/velero/issues +[4]: https://github.com/velero-io/velero/issues [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html [6]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero [7]: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml#L44 diff --git a/site/content/docs/v1.9/upgrade-to-1.9.md b/site/content/docs/v1.9/upgrade-to-1.9.md index cfec63277..5f04d9308 100644 --- a/site/content/docs/v1.9/upgrade-to-1.9.md +++ b/site/content/docs/v1.9/upgrade-to-1.9.md @@ -18,7 +18,7 @@ If you're not yet running at least Velero v1.6, see the following: - [Upgrading to v1.7][7] - [Upgrading to v1.8][8] -Before upgrading, check the [Velero compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. +Before upgrading, check the [Velero compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix) to make sure your version of Kubernetes is supported by the new version of Velero. ## Instructions diff --git a/site/content/plugins/_index.md b/site/content/plugins/_index.md index 399dd9709..2731e7a6d 100644 --- a/site/content/plugins/_index.md +++ b/site/content/plugins/_index.md @@ -11,4 +11,4 @@ Read more about how to use and create plugins [in our docs][1], a detailed list [1]: https://velero.io/docs [2]: https://velero.io/docs/supported-providers/ -[3]: https://github.com/vmware-tanzu/velero-plugin-example +[3]: https://github.com/velero-io/velero-plugin-example diff --git a/site/content/plugins/list/01-amazon-web-services.md b/site/content/plugins/list/01-amazon-web-services.md index e12023166..c8fa736cd 100644 --- a/site/content/plugins/list/01-amazon-web-services.md +++ b/site/content/plugins/list/01-amazon-web-services.md @@ -1,6 +1,6 @@ --- title: Amazon Web Services (AWS) -link: https://github.com/vmware-tanzu/velero-plugin-for-aws +link: https://github.com/velero-io/velero-plugin-for-aws objectStorage: true volumesnapshotter: true supportedByVeleroTeam: true diff --git a/site/content/plugins/list/01-google-cloud-platform.md b/site/content/plugins/list/01-google-cloud-platform.md index 2be85d0cc..0dbae84c6 100644 --- a/site/content/plugins/list/01-google-cloud-platform.md +++ b/site/content/plugins/list/01-google-cloud-platform.md @@ -1,6 +1,6 @@ --- title: Google Cloud Platform (GCP) -link: https://github.com/vmware-tanzu/velero-plugin-for-gcp +link: https://github.com/velero-io/velero-plugin-for-gcp objectStorage: true volumesnapshotter: true supportedByVeleroTeam: true diff --git a/site/content/plugins/list/01-microsoft-azure.md b/site/content/plugins/list/01-microsoft-azure.md index 7f7e8c9ee..4ecfe6a83 100644 --- a/site/content/plugins/list/01-microsoft-azure.md +++ b/site/content/plugins/list/01-microsoft-azure.md @@ -1,6 +1,6 @@ --- title: Microsoft Azure -link: https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure +link: https://github.com/velero-io/velero-plugin-for-microsoft-azure objectStorage: true volumesnapshotter: true supportedByVeleroTeam: true diff --git a/site/content/plugins/list/01-vsphere.md b/site/content/plugins/list/01-vsphere.md index 96c870a4f..5327af788 100644 --- a/site/content/plugins/list/01-vsphere.md +++ b/site/content/plugins/list/01-vsphere.md @@ -1,6 +1,6 @@ --- title: VMware vSphere -link: https://github.com/vmware-tanzu/velero-plugin-for-vsphere +link: https://github.com/velero-io/velero-plugin-for-vsphere objectStorage: false volumesnapshotter: true localStorage: true diff --git a/site/content/posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md b/site/content/posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md index 35df9c518..481d8fe33 100644 --- a/site/content/posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md +++ b/site/content/posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md @@ -29,6 +29,6 @@ Since Velero was initially released in August 2017, we’ve had nearly 70 contri * Google Group ([projectvelero](groups.google.com/forum/#!forum/projectvelero)) -We are continuing to work towards Velero 1.0 and would love your help working on the items in our roadmap. If you’re interested in contributing, we have a number of GitHub issues labeled as [Good First Issue](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) and [Help Wanted](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22), including items related to Prometheus metrics, the CLI UX, improved documentation, and more. We are more than happy to work with new and existing contributors alike. +We are continuing to work towards Velero 1.0 and would love your help working on the items in our roadmap. If you’re interested in contributing, we have a number of GitHub issues labeled as [Good First Issue](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) and [Help Wanted](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22), including items related to Prometheus metrics, the CLI UX, improved documentation, and more. We are more than happy to work with new and existing contributors alike. _Previously posted at: _ diff --git a/site/content/posts/2019-05-20-velero-1.0-has-arrived.md b/site/content/posts/2019-05-20-velero-1.0-has-arrived.md index 4c43d592b..4852f610f 100644 --- a/site/content/posts/2019-05-20-velero-1.0-has-arrived.md +++ b/site/content/posts/2019-05-20-velero-1.0-has-arrived.md @@ -59,9 +59,9 @@ Though technically not a breaking change, we have changed the way we are handing ## Join the Movement – Contribute! -Velero is better because of our contributors and maintainers. It is because of them that we can bring great software to the community. Please join us during our [online community meetings twice a month](https://github.com/vmware-tanzu/velero-community) and catch up with past meetings on YouTube at the [VMware Cloud Native Apps channel](https://www.youtube.com/channel/UCdkGV51Nu0unDNT58bHt9bg/featured) and the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). +Velero is better because of our contributors and maintainers. It is because of them that we can bring great software to the community. Please join us during our [online community meetings twice a month](https://github.com/velero-io/velero-community) and catch up with past meetings on YouTube at the [VMware Cloud Native Apps channel](https://www.youtube.com/channel/UCdkGV51Nu0unDNT58bHt9bg/featured) and the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). -You can always find the latest project information at [https://velero.io](https://velero.io). Look for issues on GitHub marked [“Good first issue”](https://github.com/vmware-tanzu/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [“Help wanted”](https://github.com/vmware-tanzu/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +You can always find the latest project information at [https://velero.io](https://velero.io). Look for issues on GitHub marked [“Good first issue”](https://github.com/velero-io/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [“Help wanted”](https://github.com/velero-io/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. You can find us on [Kubernetes Slack at the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT). Follow us on Twitter at [@ProjectVelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2019-08-22-announcing-velero-1.1.md b/site/content/posts/2019-08-22-announcing-velero-1.1.md index 3db6156af..1694f9a04 100644 --- a/site/content/posts/2019-08-22-announcing-velero-1.1.md +++ b/site/content/posts/2019-08-22-announcing-velero-1.1.md @@ -60,11 +60,11 @@ Finally, thanks to testing by [Dylan Murray](https://github.com/dymurray) and [S ## Help Us Build the Future -For Velero 1.2, the current plan is to begin implementing CSI snapshot support at a beta level. If accepted, this approach would align Velero with the larger community, and in the future, it would allow Velero to snapshot far more volume providers. We have posted a [design document](https://github.com/vmware-tanzu/velero/pull/1661) for community review, so please be sure to take a look if this interests you. +For Velero 1.2, the current plan is to begin implementing CSI snapshot support at a beta level. If accepted, this approach would align Velero with the larger community, and in the future, it would allow Velero to snapshot far more volume providers. We have posted a [design document](https://github.com/velero-io/velero/pull/1661) for community review, so please be sure to take a look if this interests you. We are also working on volume cloning, so that a persistent volume could be snapshotted and then duplicated for use within another namespace in the cluster. -The team has also been discussing different approaches to concurrent backup jobs. This is a longer term goal, that will not be included in 1.2. Comments on the [design document](https://github.com/vmware-tanzu/velero/pull/1653) would be really helpful. +The team has also been discussing different approaches to concurrent backup jobs. This is a longer term goal, that will not be included in 1.2. Comments on the [design document](https://github.com/velero-io/velero/pull/1653) would be really helpful. ## Take the Survey @@ -72,8 +72,8 @@ Finally, we’re running [a survey](https://velero.io/survey) for our users. Let ## Join the Movement – Contribute! -Velero is better because of our contributors and maintainers. It is because of them that we can bring great software to the community. Please join us during our [online community meetings every first Tuesday](https://github.com/vmware-tanzu/velero-community) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). +Velero is better because of our contributors and maintainers. It is because of them that we can bring great software to the community. Please join us during our [online community meetings every first Tuesday](https://github.com/velero-io/velero-community) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). -You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [“Good first issue”](https://github.com/vmware-tanzu/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [“Help wanted”](https://github.com/vmware-tanzu/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [“Good first issue”](https://github.com/velero-io/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [“Help wanted”](https://github.com/velero-io/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. You can find us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT), and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2019-10-01-announcing-gh-move.md b/site/content/posts/2019-10-01-announcing-gh-move.md index 0a754d563..76c46ec27 100644 --- a/site/content/posts/2019-10-01-announcing-gh-move.md +++ b/site/content/posts/2019-10-01-announcing-gh-move.md @@ -16,7 +16,7 @@ We are now part of a brand new GitHub organization: [VMware Tanzu][1]. VMware Ta ## The new Velero -The new Velero repository can now be found at [github.com/vmware-tanzu/velero](https://github.com/vmware-tanzu/velero). Past issues, pull requests, commits, contributors, etc., have all been moved to this repo. +The new Velero repository can now be found at [github.com/velero-io/velero](https://github.com/velero-io/velero). Past issues, pull requests, commits, contributors, etc., have all been moved to this repo. The next Velero release, version 1.2, will be built out of this new repository and is slated to come out at the end of October. The main [set of changes][5] for version 1.2 is the restructuring around how we will be handling all Object Store and Volume Snapshotter plugins. Previously, Velero included both types of plugins for AWS, Microsoft Azure, and Google Cloud Platform (GCP) in-tree. Beginning with Velero 1.2, these plugins will be moved out of tree and installed like any other plugin. @@ -43,4 +43,4 @@ As always, we welcome feedback and participation in the development of Velero. A [2]: https://blogs.vmware.com/cloudnative/2019/10/01/open-source-in-vmware-tanzu/ [3]: ../docs/main/supported-providers [4]: https://velero.io/docs/main/ -[5]: https://github.com/vmware-tanzu/velero/issues#workspaces/velero-5c59c15e39d47b774b5864e3/board?milestones=v1.2%232019-10-31&filterLogic=any&repos=99143276&showPipelineDescriptions=false +[5]: https://github.com/velero-io/velero/issues#workspaces/velero-5c59c15e39d47b774b5864e3/board?milestones=v1.2%232019-10-31&filterLogic=any&repos=99143276&showPipelineDescriptions=false diff --git a/site/content/posts/2019-11-07-Velero-1.2-Sets-Sail.md b/site/content/posts/2019-11-07-Velero-1.2-Sets-Sail.md index 5b8aa15f2..eca0c1f3b 100644 --- a/site/content/posts/2019-11-07-Velero-1.2-Sets-Sail.md +++ b/site/content/posts/2019-11-07-Velero-1.2-Sets-Sail.md @@ -46,7 +46,7 @@ In Kubernetes 1.16, custom resource definitions (CRDs) reached general availabil ## And More -There are too many new features and improvements to cover in this short blog post. For full details on all of the changes, see the [full changelog](https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.2.md). +There are too many new features and improvements to cover in this short blog post. For full details on all of the changes, see the [full changelog](https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.2.md). ## Community Contributors @@ -77,6 +77,6 @@ Check out these talks related to Velero: Velero is better because of our contributors and maintainers. It is because of you that we can bring great software to the community. Please join us during our [online community meetings every Tuesday](https://velero.io/community/) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). -You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/vmware-tanzu/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/vmware-tanzu/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/velero-io/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/velero-io/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. You can chat with us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT) and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2020-03-02-Velero-1.3-Voyage-Continues.md b/site/content/posts/2020-03-02-Velero-1.3-Voyage-Continues.md index b3b4802f8..5fcd9ff05 100644 --- a/site/content/posts/2020-03-02-Velero-1.3-Voyage-Continues.md +++ b/site/content/posts/2020-03-02-Velero-1.3-Voyage-Continues.md @@ -38,12 +38,12 @@ For more information on manifest lists, see [Docker’s documentation](https://d We fixed a large number of bugs and made some smaller usability improvements in this release. Here are a few highlights: -- Support private registries with custom ports for the restic restore helper image ([PR #1999](https://github.com/vmware-tanzu/velero/pull/1999), [@cognoz](https://github.com/cognoz)) -- Use AWS profile from BackupStorageLocation when invoking restic ([PR #2096](https://github.com/vmware-tanzu/velero/pull/2096), [@dinesh](https://github.com/dinesh)) -- Allow restores from schedules in other clusters ([PR #2218](https://github.com/vmware-tanzu/velero/pull/2218), [@cpanato](https://github.com/cpanato)) -- Fix memory leak & race condition in restore code ([PR #2201](https://github.com/vmware-tanzu/velero/pull/2201), [@skriss](https://github.com/skriss)) +- Support private registries with custom ports for the restic restore helper image ([PR #1999](https://github.com/velero-io/velero/pull/1999), [@cognoz](https://github.com/cognoz)) +- Use AWS profile from BackupStorageLocation when invoking restic ([PR #2096](https://github.com/velero-io/velero/pull/2096), [@dinesh](https://github.com/dinesh)) +- Allow restores from schedules in other clusters ([PR #2218](https://github.com/velero-io/velero/pull/2218), [@cpanato](https://github.com/cpanato)) +- Fix memory leak & race condition in restore code ([PR #2201](https://github.com/velero-io/velero/pull/2201), [@skriss](https://github.com/skriss)) -For a full list of all changes in this release, see [the changelog](https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.3.md). +For a full list of all changes in this release, see [the changelog](https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.3.md). ## An Update on CSI Snapshot Support @@ -57,6 +57,6 @@ Our priorities have not changed, and we’re continuing to work hard on adding C Velero is better because of our contributors and maintainers. It is because of you that we can bring great software to the community. Please join us during our [online community meetings every Tuesday](https://velero.io/community/) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). -You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/vmware-tanzu/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/vmware-tanzu/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/velero-io/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/velero-io/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. You can chat with us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT) and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2020-05-26-Velero-1.4-Community-Wave.md b/site/content/posts/2020-05-26-Velero-1.4-Community-Wave.md index c0c6c8190..78b3c12ce 100644 --- a/site/content/posts/2020-05-26-Velero-1.4-Community-Wave.md +++ b/site/content/posts/2020-05-26-Velero-1.4-Community-Wave.md @@ -76,7 +76,7 @@ Since its inception, Velero has backed up and restored the Kubernetes API server In order to remedy this, [Rafael Brito](https://github.com/brito-rafa) from VMware has tackled the issue and reworked Velero’s backup logic and format. Velero v1.4.0 introduces a backwards-compatible change to the backup tarball format, in addition to a new change to the API discovery behavior that will back up all versions of each resource, rather than just the preferred version. -We’re currently experimenting with being able to restore different versions, as well as revisiting assumptions in the backup code that are now changed by this feature. If you’d like to try it out in the meantime, you can enable it with the `EnableAPIGroupVersions` feature flag. Be sure to provide feedback on [the issue](https://github.com/vmware-tanzu/velero/issues/2551) if you interested, as well. +We’re currently experimenting with being able to restore different versions, as well as revisiting assumptions in the backup code that are now changed by this feature. If you’d like to try it out in the meantime, you can enable it with the `EnableAPIGroupVersions` feature flag. Be sure to provide feedback on [the issue](https://github.com/velero-io/velero/issues/2551) if you interested, as well. ## Added support for custom certificates @@ -105,6 +105,6 @@ Thanks again to all of our contributors who asked questions, filed issues, and w If you’d like to get involved, please join us during our [online community meetings every Tuesday](https://velero.io/community/) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). -You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/vmware-tanzu/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/vmware-tanzu/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +You can always find the latest project information at [velero.io](https://velero.io). Look for issues on GitHub marked [Good first issue](https://github.com/velero-io/velero/issues?q=is:open+is:issue+label:%22Good+first+issue%22) or [Help wanted](https://github.com/velero-io/velero/issues?utf8=✓&q=is:open+is:issue+label:%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. You can chat with us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT) and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2020-05-27-CSI-integration.md b/site/content/posts/2020-05-27-CSI-integration.md index b21e275b6..f5e308a42 100644 --- a/site/content/posts/2020-05-27-CSI-integration.md +++ b/site/content/posts/2020-05-27-CSI-integration.md @@ -7,7 +7,7 @@ image: /img/posts/csi-announce-blog.jpg tags: ['Velero Team', 'Ashish Amarnath'] --- -In the recent [1.4 release of Velero](https://github.com/vmware-tanzu/velero/releases), we announced a new feature of supporting CSI snapshotting using the [Kubernetes CSI Snapshot Beta APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). +In the recent [1.4 release of Velero](https://github.com/velero-io/velero/releases), we announced a new feature of supporting CSI snapshotting using the [Kubernetes CSI Snapshot Beta APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). With this capability of CSI volume snapshotting, Velero can now support any volume provider that has a CSI driver with snapshotting capability, without requiring a Velero-specific volume snapshotter plugin to be available. This post has the necessary instructions for you to start using this feature. @@ -43,7 +43,7 @@ This script will deploy the following CSI components, CRDs, and necessary RBAC: The CSI volume snapshot capability is currently, as of Velero 1.4, a beta feature behind the `EnableCSI` feature flag and is not enabled by default. -Following instructions from our [docs website](https://velero.io/docs/csi/), install Velero with the [velero-plugin-for-csi](https://github.com/vmware-tanzu/velero-plugin-for-csi) and using the Azure Blob Store as our BackupStorageLocation. Please refer to our [velero-plugin-for-microsoft-azure documentation](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure) for instructions on setting up the BackupStorageLocation. Please note that the BackupStorageLocation should be set up before installing Velero. +Following instructions from our [docs website](https://velero.io/docs/csi/), install Velero with the [velero-plugin-for-csi](https://github.com/vmware-tanzu/velero-plugin-for-csi) and using the Azure Blob Store as our BackupStorageLocation. Please refer to our [velero-plugin-for-microsoft-azure documentation](https://github.com/velero-io/velero-plugin-for-microsoft-azure) for instructions on setting up the BackupStorageLocation. Please note that the BackupStorageLocation should be set up before installing Velero. Install Velero by running the below command diff --git a/site/content/posts/2020-09-16-Velero-1.5-For-And-By-Community.md b/site/content/posts/2020-09-16-Velero-1.5-For-And-By-Community.md index aa19bd536..76ff2a565 100644 --- a/site/content/posts/2020-09-16-Velero-1.5-For-And-By-Community.md +++ b/site/content/posts/2020-09-16-Velero-1.5-For-And-By-Community.md @@ -21,7 +21,7 @@ Before diving into the features in this release, we would like to state explicit 1. All of our repositories, including the Velero and plugins repositories, now use `main` as their default branch. 1. The development images pushed to [Velero docker hub](https://hub.docker.com/u/velero) on every PR merge now have the `main` tag. For example, the latest development image for `velero` is `velero/velero:main`. -If we have missed addressing insensitive verbiage anywhere, please let us know on the [#velero slack channel](https://kubernetes.slack.com/archives/C6VCGP4MT) or by [creating issues on github](https://github.com/vmware-tanzu/velero/issues/new/choose) and we will address it immediately. +If we have missed addressing insensitive verbiage anywhere, please let us know on the [#velero slack channel](https://kubernetes.slack.com/archives/C6VCGP4MT) or by [creating issues on github](https://github.com/velero-io/velero/issues/new/choose) and we will address it immediately. ## Release Highlights @@ -42,7 +42,7 @@ You can enable this feature on a per backup basis or as a default setting for al Plugins in Velero are independent binaries that you can use to customize Velero’s behavior. In this release, we introduce a new plugin type, DeleteItemAction plugin, that offers yet another extension point to customize Velero’s functionality. This is in addition to the already existing ObjectStore plugin, VolumeSnapshotter plugin, BackupItemAction, and RestoreItemAction plugin types. -The [velero-plugin-for-csi](https://github.com/vmware-tanzu/velero-plugin-for-csi) introduced a new pattern for backing up and restoring volume snapshots using BackupItemAction and RestoreItemAction plugins. To allow the community to adopt a similar pattern for their custom resources, Velero had to provide an extension point to clean up both in-cluster and external resources, created by their BackupItemAction plugins. This is now possible with DeleteItemAction plugins. The interface for this new plugin type is similar to that of BackupItemAction and RestoreItemAction plugins. You can read more about the design for this plugin in the [design documents of our repository on github](https://github.com/vmware-tanzu/velero/blob/main/design/delete-item-action.md). +The [velero-plugin-for-csi](https://github.com/vmware-tanzu/velero-plugin-for-csi) introduced a new pattern for backing up and restoring volume snapshots using BackupItemAction and RestoreItemAction plugins. To allow the community to adopt a similar pattern for their custom resources, Velero had to provide an extension point to clean up both in-cluster and external resources, created by their BackupItemAction plugins. This is now possible with DeleteItemAction plugins. The interface for this new plugin type is similar to that of BackupItemAction and RestoreItemAction plugins. You can read more about the design for this plugin in the [design documents of our repository on github](https://github.com/velero-io/velero/blob/main/design/delete-item-action.md). ### Code Modernization @@ -58,14 +58,14 @@ Driven wholly by the Velero community, we have a design for the missing Restore 1. InitContainer Restore Hooks: These will add init containers into restored pods to perform any necessary setup before the application containers of the restored pod can start. 1. Exec Restore Hooks: These can be used to execute custom commands or scripts in containers of a restored Kubernetes pod. -You can find more details about the design in the [design document for this feature](https://github.com/vmware-tanzu/velero/blob/main/design/restore-hooks.md). +You can find more details about the design in the [design document for this feature](https://github.com/velero-io/velero/blob/main/design/restore-hooks.md). ### Ordered backup of resources -Velero can specify a custom order in which resources can be backed up. Thanks to our community member [@phuongatemc](https://github.com/phuongatemc) for driving this functionality from design to implementation. This is going to serve as a building block to support backup and restore of certain stateful applications. Here is the [design document](https://github.com/vmware-tanzu/velero/blob/main/design/backup-resources-order.md) for the enhancement. +Velero can specify a custom order in which resources can be backed up. Thanks to our community member [@phuongatemc](https://github.com/phuongatemc) for driving this functionality from design to implementation. This is going to serve as a building block to support backup and restore of certain stateful applications. Here is the [design document](https://github.com/velero-io/velero/blob/main/design/backup-resources-order.md) for the enhancement. -These were just some highlights of the release. You can always find more information about the release in the [release change log](https://github.com/vmware-tanzu/velero/blob/v1.5.1/changelogs/CHANGELOG-1.5.md). +These were just some highlights of the release. You can always find more information about the release in the [release change log](https://github.com/velero-io/velero/blob/v1.5.1/changelogs/CHANGELOG-1.5.md). See the [1.5 upgrade instructions](https://velero.io/docs/v1.5/upgrade-to-1.5/) to start planning your upgrade today. ## Join the Community and Make Velero Better diff --git a/site/content/posts/2021-04-13-Velero-1.6-Bring-All-Your-Credentials.md b/site/content/posts/2021-04-13-Velero-1.6-Bring-All-Your-Credentials.md index 7cc2fbcb0..aa3875ccc 100644 --- a/site/content/posts/2021-04-13-Velero-1.6-Bring-All-Your-Credentials.md +++ b/site/content/posts/2021-04-13-Velero-1.6-Bring-All-Your-Credentials.md @@ -60,11 +60,11 @@ For more information about the improvements provided with this upgrade, please s ### Increased Stability with End-to-end Testing As the Velero project continues to grow, it is important that our community of users can continue to trust and rely on Velero to support them in their disaster recovery and migration needs. -During this release cycle, we decided to focus on increased stability by adding a new suite of [end-to-end tests](https://github.com/vmware-tanzu/velero/tree/main/test/e2e). +During this release cycle, we decided to focus on increased stability by adding a new suite of [end-to-end tests](https://github.com/velero-io/velero/tree/main/test/e2e). Although Velero features have always been thoroughly tested, these new tests execute Velero workflows from the perspective of the user interacting with a Velero installation using the CLI. This new test framework has enabled us to create tests that can be easily run across multiple Kubernetes providers, ensuring that we prevent regressions quickly and early in the development of new features. -We plan to expand on this work in our upcoming releases, including [adding more test cases](https://github.com/vmware-tanzu/velero/issues/3531) and running these tests as [part of our CI process](https://github.com/vmware-tanzu/velero/issues/3574). +We plan to expand on this work in our upcoming releases, including [adding more test cases](https://github.com/velero-io/velero/issues/3531) and running these tests as [part of our CI process](https://github.com/velero-io/velero/issues/3574). ### Growing the Velero Team @@ -77,7 +77,7 @@ Feel free to reach out to her with any product thoughts or feedback. Welcome, Eleanor! The Velero project welcomes contributors of all kinds. -If you are interested in contributing more, or finding out what is involved in becoming a maintainer, please see our documentation on [project governance](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md). +If you are interested in contributing more, or finding out what is involved in becoming a maintainer, please see our documentation on [project governance](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md). ### Improving Developer Experience @@ -92,7 +92,7 @@ If you would like to try it out, please see our [documentation](https://velero.i We have more exciting additions and improvements to Velero earmarked for future releases. For v1.7, we are looking forward to adding the ability to install Velero with [Carvel](https://carvel.dev/), supporting plugin versioning, bringing the CSI snapshotting to GA, having a diagnostics tool, and other improvements. -See our [project roadmap](https://github.com/vmware-tanzu/velero/blob/main/ROADMAP.md#170-roadmap) for the complete list. +See our [project roadmap](https://github.com/velero-io/velero/blob/main/ROADMAP.md#170-roadmap) for the complete list. ### Join the Community and Make Velero Better @@ -102,8 +102,8 @@ It is because of you that we can bring great software to the community. Please join us during our online [community meetings every Tuesday](https://hackmd.io/Jq6F5zqZR7S80CeDWUklkA?view) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). You can always find the latest project information at [velero.io](https://velero.io). -Look for issues on GitHub marked ["Good first issue"](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) or ["Help wanted"](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +Look for issues on GitHub marked ["Good first issue"](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) or ["Help wanted"](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. -For opportunities to help and be helped, visit our [Community Support Q&A on GitHub](https://github.com/vmware-tanzu/velero/discussions/categories/community-support-q-a). +For opportunities to help and be helped, visit our [Community Support Q&A on GitHub](https://github.com/velero-io/velero/discussions/categories/community-support-q-a). You can chat with us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT) and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/content/posts/2023-04-26-Velero-1.11.md b/site/content/posts/2023-04-26-Velero-1.11.md index f39a161af..bb1910857 100644 --- a/site/content/posts/2023-04-26-Velero-1.11.md +++ b/site/content/posts/2023-04-26-Velero-1.11.md @@ -10,13 +10,13 @@ tags: ['Velero Team', 'Orlin Vasilev', 'Velero Release'] --- We haven't posted for while, but this deserves your attention! -Last week during KubeCon Europe in Amsterdam we released [Velero v1.11](https://github.com/vmware-tanzu/velero/releases/tag/v1.11.0), which brings significant improvements in its functionality, flexibility, and performance. In this blog post, we will discuss the new features and changes that come with Velero v1.11 and how they can benefit users. +Last week during KubeCon Europe in Amsterdam we released [Velero v1.11](https://github.com/velero-io/velero/releases/tag/v1.11.0), which brings significant improvements in its functionality, flexibility, and performance. In this blog post, we will discuss the new features and changes that come with Velero v1.11 and how they can benefit users. The theme of the v1.11 release is most definitely more flexibility, not only with the features added, but also in terms of the Velero contribution, development, and quality assurance processes. In case you missed it we have new Product Manager - [Pradeep Kumar Chaturvedi](https://github.com/pradeepkchaturvedi) and few new contributors from companies like DELL and Microsoft. -### Full list of changes can be found [here](https://github.com/vmware-tanzu/velero/releases/tag/v1.11.0) +### Full list of changes can be found [here](https://github.com/velero-io/velero/releases/tag/v1.11.0) ## Release Highlights @@ -24,17 +24,17 @@ In case you missed it we have new Product Manager - [Pradeep Kumar Chaturvedi](h This feature implements the BackupItemAction v2. BIA v2 has two new methods: Progress() and Cancel() and modifies the Execute() return value. The API change is needed to facilitate long-running BackupItemAction plugin actions that may not be complete when the Execute() method returns. This will allow long-running BackupItemAction plugin actions to continue in the background while the Velero moves to the following plugin or the next item. -[https://github.com/vmware-tanzu/velero/pull/5442](https://github.com/vmware-tanzu/velero/pull/5442) +[https://github.com/velero-io/velero/pull/5442](https://github.com/velero-io/velero/pull/5442) ### RestoreItemAction v2 This feature implemented the RestoreItemAction v2. RIA v2 has three new methods: Progress(), Cancel(), and AreAdditionalItemsReady(), and it modifies RestoreItemActionExecuteOutput() structure in the RIA return value. The Progress() and Cancel() methods are needed to facilitate long-running RestoreItemAction plugin actions that may not be complete when the Execute() method returns. This will allow long-running RestoreItemAction plugin actions to continue in the background while the Velero moves to the following plugin or the next item. The AreAdditionalItemsReady() method is needed to allow plugins to tell Velero to wait until the returned additional items have been restored and are ready for use in the cluster before restoring the current item. -[https://github.com/vmware-tanzu/velero/pull/5569](https://github.com/vmware-tanzu/velero/pull/5569) +[https://github.com/velero-io/velero/pull/5569](https://github.com/velero-io/velero/pull/5569) ### Plugin Progress Monitoring -This is intended as a replacement for the previously-approved Upload Progress Monitoring design ([Upload Progress Monitoring](https://github.com/vmware-tanzu/velero/blob/main/design/upload-progress.md)) to expand the supported use cases beyond snapshot upload to include what was previously called Async Backup/Restore Item Actions. +This is intended as a replacement for the previously-approved Upload Progress Monitoring design ([Upload Progress Monitoring](https://github.com/velero-io/velero/blob/main/design/upload-progress.md)) to expand the supported use cases beyond snapshot upload to include what was previously called Async Backup/Restore Item Actions. ### Flexible resource policy that can filter volumes to skip in the backup This feature provides a flexible policy to filter volumes in the backup without requiring patching any labels or annotations to the pods or volumes. This policy is configured as k8s ConfigMap and maintained by the users themselves, and it can be extended to more scenarios in the future. By now, the policy rules out volumes from backup depending on the CSI driver, NFS setting, volume size, and StorageClass setting. Please refer to [Resource policies rules](https://velero.io/docs/v1.11/resource-filtering/#resource-policies) for the policy's ConifgMap format. It is not guaranteed to work on unofficial third-party plugins as it may not follow the existing backup workflow code logic of Velero. @@ -84,8 +84,8 @@ If you would like to try it out, please see our [documentation](https://velero.i ### Looking Forward We have more exciting additions and improvements to Velero earmarked for future releases. -For v1.12, we would like to have your input again [here](https://github.com/vmware-tanzu/velero/discussions/6217) -See our [1.12 RoadMap](https://github.com/vmware-tanzu/velero/wiki/1.12-Roadmap) for the complete list. +For v1.12, we would like to have your input again [here](https://github.com/velero-io/velero/discussions/6217) +See our [1.12 RoadMap](https://github.com/velero-io/velero/wiki/1.12-Roadmap) for the complete list. ### Join the Community and Make Velero Better @@ -95,9 +95,9 @@ It is because of you that we can bring great software to the community. Please join us during our online [community meetings every Tuesday](https://hackmd.io/Jq6F5zqZR7S80CeDWUklkA?view) and catch up with past meetings on YouTube on the [Velero Community Meetings playlist](https://www.youtube.com/watch?v=nc48ocI-6go&list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM). You can always find the latest project information at [velero.io](https://velero.io). -Look for issues on GitHub marked ["Good first issue"](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) or ["Help wanted"](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. +Look for issues on GitHub marked ["Good first issue"](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22) or ["Help wanted"](https://github.com/velero-io/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+) if you want to roll up your sleeves and write some code with us. -For opportunities to help and be helped, visit our [Community Support Q&A on GitHub](https://github.com/vmware-tanzu/velero/discussions/categories/community-support-q-a). +For opportunities to help and be helped, visit our [Community Support Q&A on GitHub](https://github.com/velero-io/velero/discussions/categories/community-support-q-a). You can chat with us on [Kubernetes Slack in the #velero channel](https://kubernetes.slack.com/messages/C6VCGP4MT) and follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero). diff --git a/site/layouts/404.html b/site/layouts/404.html index 267af61c0..85a19a7ba 100644 --- a/site/layouts/404.html +++ b/site/layouts/404.html @@ -20,7 +20,7 @@
  • Resources
    • -

    If you can't find what you are looking for, try asking a question in our slack channel or filing an issue.

    +

    If you can't find what you are looking for, try asking a question in our slack channel or filing an issue.

    {{ end }}