From d987388698aad886cd997a3866a3b5f05831d162 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 22 May 2026 07:26:59 +0000 Subject: [PATCH 1/6] Initial plan From 0b7eaaf4e6bb6bf7719b27443f8da0ae4a3ef2f8 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 22 May 2026 07:38:02 +0000 Subject: [PATCH 2/6] chore: replace vmware-tanzu/velero org references Agent-Logs-Url: https://github.com/velero-io/velero/sessions/e8c22e84-a488-4645-a0e1-aea5a2926503 Co-authored-by: kaovilai <11228024+kaovilai@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/config.yml | 2 +- .../feature-enhancement-request.md | 2 +- .gitignore | 2 +- .golangci.yaml | 2 +- .goreleaser.yml | 2 +- ADOPTERS.md | 4 +- CHANGELOG.md | 52 +++++++-------- Dockerfile | 4 +- Dockerfile-Windows | 4 +- GOVERNANCE.md | 22 +++---- MAINTAINERS.md | 2 +- Makefile | 10 +-- ROADMAP.md | 2 +- SECURITY.md | 6 +- changelogs/CHANGELOG-0.10.md | 4 +- changelogs/CHANGELOG-0.9.md | 2 +- changelogs/CHANGELOG-1.10.md | 12 ++-- changelogs/CHANGELOG-1.11.md | 6 +- changelogs/CHANGELOG-1.12.md | 8 +-- changelogs/CHANGELOG-1.13.md | 8 +-- changelogs/CHANGELOG-1.14.md | 2 +- changelogs/CHANGELOG-1.15.md | 16 ++--- changelogs/CHANGELOG-1.16.md | 34 +++++----- changelogs/CHANGELOG-1.17.md | 16 ++--- changelogs/CHANGELOG-1.18.md | 8 +-- changelogs/CHANGELOG-1.2.md | 2 +- changelogs/CHANGELOG-1.3.md | 14 ++-- changelogs/CHANGELOG-1.4.md | 4 +- changelogs/CHANGELOG-1.5.md | 4 +- changelogs/CHANGELOG-1.6.md | 2 +- changelogs/CHANGELOG-1.7.md | 4 +- changelogs/CHANGELOG-1.8.md | 4 +- changelogs/CHANGELOG-1.9.md | 4 +- cmd/velero/velero.go | 4 +- ...-bsl-delete-associated-resources_design.md | 4 +- ...-VolumePolicies-to-support-more-actions.md | 20 +++--- .../clean_artifacts_in_csi_flow.md | 2 +- .../cluster-scope-resource-filter.md | 4 +- design/Implemented/custom-ca-support.md | 10 +-- .../existing-resource-policy_design.md | 10 +-- .../general-progress-monitoring.md | 12 ++-- .../include-exclude-in-resource-policy.md | 2 +- .../json-substitution-action-design.md | 2 +- ...atch-and-strategic-in-resource-modifier.md | 4 +- design/Implemented/move-gh-org.md | 4 +- ...ultiple-csi-volumesnapshotclass-support.md | 2 +- .../multiple-label-selectors_design.md | 6 +- ...ugin-backup-and-restore-progress-design.md | 6 +- design/Implemented/plugin-versioning.md | 14 ++-- design/Implemented/pv-cloning.md | 4 +- design/Implemented/pv_backup_info.md | 8 +-- design/Implemented/pv_restore_info.md | 4 +- .../repo_maintenance_job_config.md | 6 +- design/Implemented/resource-status-restore.md | 2 +- .../restore-finalizing-phase_design.md | 2 +- ...ore-with-EnableAPIGroupVersions-feature.md | 10 +-- .../retry-patching-configuration_design.md | 8 +-- ...schedule-skip-immediately-config_design.md | 2 +- design/Implemented/secrets.md | 16 ++--- ...orting-volumeattributes-resource-policy.md | 4 +- design/Implemented/velero-debug.md | 2 +- .../Implemented/vgdp-affinity-enhancement.md | 2 +- .../vgdp-micro-service-for-fs-backup.md | 10 +-- design/Implemented/volume-group-snapshot.md | 4 +- .../volume-snapshot-data-movement.md | 2 +- .../Implemented/wait-for-additional-items.md | 6 +- .../wildcard-namespace-support-design.md | 2 +- design/cli-install-changes.md | 6 +- .../new-prepost-backuprestore-plugin-hooks.md | 18 +++--- design/restore-progress.md | 2 +- go.mod | 2 +- hack/issue-template-gen/main.go | 2 +- hack/release-tools/brew-update.sh | 2 +- hack/release-tools/gen-docs.sh | 4 +- hack/update-1fmt.sh | 2 +- hack/update-2proto.sh | 2 +- internal/credentials/file_store.go | 4 +- internal/credentials/file_store_test.go | 4 +- internal/credentials/secret_store.go | 2 +- .../csi/volumesnapshotcontent_action.go | 8 +-- .../csi/volumesnapshotcontent_action_test.go | 10 +-- internal/delete/delete_item_action_handler.go | 12 ++-- .../delete/delete_item_action_handler_test.go | 12 ++-- internal/hook/item_hook_handler.go | 16 ++--- internal/hook/item_hook_handler_test.go | 12 ++-- internal/hook/wait_exec_hook_handler.go | 8 +-- internal/hook/wait_exec_hook_handler_test.go | 8 +-- .../resourcemodifiers/resource_modifiers.go | 2 +- .../resourcepolicies/resource_policies.go | 2 +- .../restartabletest/restartable_delegate.go | 4 +- internal/storage/storagelocation.go | 2 +- internal/storage/storagelocation_test.go | 8 +-- internal/velero/images.go | 2 +- internal/velero/images_test.go | 2 +- internal/velero/serverstatusrequest.go | 6 +- internal/volume/snapshotlocation.go | 4 +- internal/volume/utils.go | 2 +- internal/volume/volumes_information.go | 12 ++-- internal/volume/volumes_information_test.go | 16 ++--- internal/volumehelper/volume_policy_helper.go | 14 ++-- .../volumehelper/volume_policy_helper_test.go | 12 ++-- pkg/apis/velero/v1/pod_volume_backup_types.go | 2 +- pkg/apis/velero/v1/pod_volume_restore_type.go | 2 +- .../velero/v2alpha1/data_download_types.go | 2 +- pkg/apis/velero/v2alpha1/data_upload_types.go | 2 +- pkg/archive/extractor.go | 2 +- pkg/archive/extractor_test.go | 4 +- pkg/archive/filesystem.go | 4 +- pkg/archive/filesystem_test.go | 4 +- pkg/archive/parser.go | 4 +- pkg/archive/parser_test.go | 2 +- pkg/backup/actions/backup_pv_action.go | 6 +- pkg/backup/actions/backup_pv_action_test.go | 10 +-- pkg/backup/actions/csi/pvc_action.go | 30 ++++----- pkg/backup/actions/csi/pvc_action_test.go | 18 +++--- .../actions/csi/volumesnapshot_action.go | 20 +++--- .../actions/csi/volumesnapshot_action_test.go | 12 ++-- .../actions/csi/volumesnapshotclass_action.go | 10 +-- .../csi/volumesnapshotclass_action_test.go | 8 +-- .../csi/volumesnapshotcontent_action.go | 10 +-- .../csi/volumesnapshotcontent_action_test.go | 10 +-- pkg/backup/actions/pod_action.go | 6 +- pkg/backup/actions/pod_action_test.go | 6 +- .../actions/remap_crd_version_action.go | 6 +- .../actions/remap_crd_version_action_test.go | 8 +-- pkg/backup/actions/service_account_action.go | 8 +-- .../actions/service_account_action_test.go | 8 +-- pkg/backup/backup.go | 46 ++++++------- pkg/backup/backup_test.go | 42 ++++++------ pkg/backup/delete_helpers.go | 4 +- pkg/backup/item_backupper.go | 34 +++++----- pkg/backup/item_backupper_test.go | 6 +- pkg/backup/item_collector.go | 12 ++-- pkg/backup/item_collector_test.go | 10 +-- pkg/backup/itemblock.go | 2 +- pkg/backup/request.go | 14 ++-- pkg/backup/snapshots.go | 8 +-- pkg/backup/volume_snapshotter_cache.go | 4 +- pkg/builder/backup_builder.go | 8 +-- .../backup_storage_location_builder.go | 2 +- pkg/builder/container_builder.go | 2 +- pkg/builder/container_builder_test.go | 4 +- pkg/builder/data_download_builder.go | 4 +- pkg/builder/data_upload_builder.go | 4 +- pkg/builder/delete_backup_request_builder.go | 2 +- pkg/builder/download_request_builder.go | 2 +- pkg/builder/item_operation_builder.go | 4 +- pkg/builder/pod_volume_backup_builder.go | 2 +- pkg/builder/pod_volume_restore_builder.go | 2 +- pkg/builder/restore_builder.go | 2 +- pkg/builder/schedule_builder.go | 2 +- pkg/builder/server_status_request_builder.go | 2 +- pkg/builder/testcr_builder.go | 2 +- .../volume_snapshot_location_builder.go | 2 +- pkg/cbtservice/mocks/Service.go | 2 +- pkg/client/client.go | 2 +- pkg/client/factory.go | 4 +- pkg/cmd/cli/backup/backup.go | 2 +- pkg/cmd/cli/backup/backup_test.go | 2 +- pkg/cmd/cli/backup/create.go | 16 ++--- pkg/cmd/cli/backup/create_test.go | 12 ++-- pkg/cmd/cli/backup/delete.go | 14 ++-- pkg/cmd/cli/backup/delete_test.go | 12 ++-- pkg/cmd/cli/backup/describe.go | 10 +-- pkg/cmd/cli/backup/describe_test.go | 12 ++-- pkg/cmd/cli/backup/download.go | 10 +-- pkg/cmd/cli/backup/download_test.go | 10 +-- pkg/cmd/cli/backup/get.go | 8 +-- pkg/cmd/cli/backup/get_test.go | 10 +-- pkg/cmd/cli/backup/logs.go | 10 +-- pkg/cmd/cli/backup/logs_test.go | 12 ++-- pkg/cmd/cli/backuplocation/backup_location.go | 2 +- .../backuplocation/backup_location_test.go | 2 +- pkg/cmd/cli/backuplocation/create.go | 14 ++-- pkg/cmd/cli/backuplocation/create_test.go | 6 +- pkg/cmd/cli/backuplocation/delete.go | 10 +-- pkg/cmd/cli/backuplocation/delete_test.go | 12 ++-- pkg/cmd/cli/backuplocation/get.go | 8 +-- pkg/cmd/cli/backuplocation/get_test.go | 8 +-- pkg/cmd/cli/backuplocation/set.go | 14 ++-- pkg/cmd/cli/backuplocation/set_test.go | 12 ++-- pkg/cmd/cli/bug/bug.go | 10 +-- pkg/cmd/cli/client/client.go | 2 +- pkg/cmd/cli/client/config/get.go | 4 +- pkg/cmd/cli/client/config/set.go | 4 +- pkg/cmd/cli/create/create.go | 12 ++-- pkg/cmd/cli/datamover/backup.go | 26 ++++---- pkg/cmd/cli/datamover/backup_test.go | 8 +-- pkg/cmd/cli/datamover/data_mover.go | 2 +- pkg/cmd/cli/datamover/restore.go | 26 ++++---- pkg/cmd/cli/datamover/restore_test.go | 4 +- pkg/cmd/cli/debug/debug.go | 6 +- pkg/cmd/cli/delete/delete.go | 10 +-- pkg/cmd/cli/delete_options.go | 4 +- pkg/cmd/cli/describe/describe.go | 8 +-- pkg/cmd/cli/get/get.go | 14 ++-- pkg/cmd/cli/install/install.go | 20 +++--- pkg/cmd/cli/install/install_test.go | 4 +- pkg/cmd/cli/nodeagent/node_agent.go | 2 +- pkg/cmd/cli/nodeagent/server.go | 34 +++++----- pkg/cmd/cli/nodeagent/server_test.go | 10 +-- pkg/cmd/cli/plugin/add.go | 10 +-- pkg/cmd/cli/plugin/get.go | 8 +-- pkg/cmd/cli/plugin/helpers.go | 4 +- pkg/cmd/cli/plugin/plugin.go | 2 +- pkg/cmd/cli/plugin/remove.go | 4 +- pkg/cmd/cli/podvolume/backup.go | 24 +++---- pkg/cmd/cli/podvolume/backup_test.go | 8 +-- pkg/cmd/cli/podvolume/podvolume.go | 2 +- pkg/cmd/cli/podvolume/restore.go | 24 +++---- pkg/cmd/cli/podvolume/restore_test.go | 4 +- pkg/cmd/cli/repo/get.go | 8 +-- pkg/cmd/cli/repo/repo.go | 2 +- pkg/cmd/cli/repomantenance/maintenance.go | 18 +++--- pkg/cmd/cli/restore/create.go | 18 +++--- pkg/cmd/cli/restore/create_test.go | 10 +-- pkg/cmd/cli/restore/delete.go | 10 +-- pkg/cmd/cli/restore/delete_test.go | 12 ++-- pkg/cmd/cli/restore/describe.go | 10 +-- pkg/cmd/cli/restore/describe_test.go | 12 ++-- pkg/cmd/cli/restore/get.go | 8 +-- pkg/cmd/cli/restore/get_test.go | 10 +-- pkg/cmd/cli/restore/logs.go | 10 +-- pkg/cmd/cli/restore/logs_test.go | 12 ++-- pkg/cmd/cli/restore/restore.go | 2 +- pkg/cmd/cli/restore/restore_test.go | 2 +- pkg/cmd/cli/schedule/create.go | 12 ++-- pkg/cmd/cli/schedule/delete.go | 10 +-- pkg/cmd/cli/schedule/describe.go | 8 +-- pkg/cmd/cli/schedule/get.go | 8 +-- pkg/cmd/cli/schedule/pause.go | 8 +-- pkg/cmd/cli/schedule/schedule.go | 2 +- pkg/cmd/cli/schedule/skip_options.go | 2 +- pkg/cmd/cli/schedule/unpause.go | 6 +- pkg/cmd/cli/select_option.go | 2 +- pkg/cmd/cli/select_option_test.go | 2 +- pkg/cmd/cli/serverstatus/server_status.go | 6 +- pkg/cmd/cli/snapshotlocation/create.go | 12 ++-- pkg/cmd/cli/snapshotlocation/get.go | 8 +-- pkg/cmd/cli/snapshotlocation/set.go | 12 ++-- .../cli/snapshotlocation/snapshot_location.go | 2 +- pkg/cmd/cli/uninstall/uninstall.go | 18 +++--- pkg/cmd/cli/version/version.go | 8 +-- pkg/cmd/cli/version/version_test.go | 8 +-- pkg/cmd/server/config/config.go | 16 ++--- pkg/cmd/server/plugin/plugin.go | 30 ++++----- pkg/cmd/server/server.go | 64 +++++++++---------- pkg/cmd/server/server_test.go | 18 +++--- pkg/cmd/util/cacert/bsl_cacert.go | 2 +- pkg/cmd/util/cacert/bsl_cacert_test.go | 6 +- .../util/downloadrequest/downloadrequest.go | 4 +- .../downloadrequest/downloadrequest_test.go | 8 +-- pkg/cmd/util/output/backup_describer.go | 16 ++--- pkg/cmd/util/output/backup_describer_test.go | 10 +-- pkg/cmd/util/output/backup_printer.go | 2 +- pkg/cmd/util/output/backup_printer_test.go | 2 +- pkg/cmd/util/output/backup_repo_printer.go | 2 +- .../output/backup_storage_location_printer.go | 4 +- .../output/backup_structured_describer.go | 10 +-- .../backup_structured_describer_test.go | 8 +-- pkg/cmd/util/output/output.go | 6 +- pkg/cmd/util/output/output_test.go | 2 +- pkg/cmd/util/output/plugin_printer.go | 2 +- pkg/cmd/util/output/restore_describer.go | 14 ++-- pkg/cmd/util/output/restore_describer_test.go | 12 ++-- pkg/cmd/util/output/restore_printer.go | 2 +- pkg/cmd/util/output/schedule_describe_test.go | 4 +- pkg/cmd/util/output/schedule_describer.go | 2 +- pkg/cmd/util/output/schedule_printer.go | 2 +- .../volume_snapshot_location_printer.go | 2 +- pkg/cmd/velero/velero.go | 54 ++++++++-------- pkg/controller/backup_controller.go | 44 ++++++------- pkg/controller/backup_controller_test.go | 36 +++++------ pkg/controller/backup_deletion_controller.go | 42 ++++++------ .../backup_deletion_controller_test.go | 36 +++++------ pkg/controller/backup_finalizer_controller.go | 22 +++---- .../backup_finalizer_controller_test.go | 20 +++--- .../backup_operations_controller.go | 22 +++---- .../backup_operations_controller_test.go | 26 ++++---- pkg/controller/backup_queue_controller.go | 8 +-- .../backup_queue_controller_test.go | 6 +- .../backup_repository_controller.go | 16 ++--- .../backup_repository_controller_test.go | 22 +++---- .../backup_storage_location_controller.go | 14 ++-- ...backup_storage_location_controller_test.go | 16 ++--- pkg/controller/backup_sync_controller.go | 14 ++-- pkg/controller/backup_sync_controller_test.go | 14 ++-- pkg/controller/data_download_controller.go | 28 ++++---- .../data_download_controller_test.go | 24 +++---- pkg/controller/data_upload_controller.go | 26 ++++---- pkg/controller/data_upload_controller_test.go | 24 +++---- pkg/controller/download_request_controller.go | 12 ++-- .../download_request_controller_test.go | 12 ++-- pkg/controller/gc_controller.go | 14 ++-- pkg/controller/gc_controller_test.go | 6 +- .../pod_volume_backup_controller.go | 20 +++--- .../pod_volume_backup_controller_test.go | 20 +++--- .../pod_volume_restore_controller.go | 24 +++---- .../pod_volume_restore_controller_test.go | 24 +++---- pkg/controller/restore_controller.go | 44 ++++++------- pkg/controller/restore_controller_test.go | 28 ++++---- .../restore_finalizer_controller.go | 24 +++---- .../restore_finalizer_controller_test.go | 28 ++++---- .../restore_operations_controller.go | 16 ++--- .../restore_operations_controller_test.go | 24 +++---- pkg/controller/schedule_controller.go | 10 +-- pkg/controller/schedule_controller_test.go | 10 +-- .../server_status_request_controller.go | 12 ++-- .../server_status_request_controller_test.go | 12 ++-- pkg/controller/suite_test.go | 8 +-- pkg/datamover/backup_micro_service.go | 14 ++-- pkg/datamover/backup_micro_service_test.go | 14 ++-- pkg/datamover/dataupload_delete_action.go | 10 +-- .../dataupload_delete_action_test.go | 10 +-- pkg/datamover/restore_micro_service.go | 14 ++-- pkg/datamover/restore_micro_service_test.go | 14 ++-- pkg/datapath/file_system.go | 16 ++--- pkg/datapath/file_system_test.go | 6 +- pkg/datapath/micro_service_watcher.go | 6 +- pkg/datapath/micro_service_watcher_test.go | 8 +-- pkg/datapath/mocks/asyncBR.go | 2 +- pkg/datapath/types.go | 2 +- pkg/discovery/helper.go | 6 +- pkg/discovery/helper_test.go | 8 +-- pkg/exposer/cache_volume.go | 4 +- pkg/exposer/csi_snapshot.go | 12 ++-- pkg/exposer/csi_snapshot_priority_test.go | 6 +- pkg/exposer/csi_snapshot_test.go | 12 ++-- pkg/exposer/generic_restore.go | 8 +-- pkg/exposer/generic_restore_priority_test.go | 6 +- pkg/exposer/generic_restore_test.go | 6 +- pkg/exposer/host_path.go | 10 +-- pkg/exposer/host_path_test.go | 14 ++-- pkg/exposer/image.go | 2 +- pkg/exposer/image_test.go | 2 +- pkg/exposer/mocks/GenericRestoreExposer.go | 2 +- pkg/exposer/mocks/PodVolumeExposer.go | 2 +- pkg/exposer/pod_volume.go | 8 +-- pkg/exposer/pod_volume_test.go | 10 +-- pkg/exposer/vgdp_counter.go | 4 +- pkg/exposer/vgdp_counter_test.go | 8 +-- pkg/install/daemonset.go | 4 +- pkg/install/deployment.go | 6 +- pkg/install/deployment_test.go | 2 +- pkg/install/import_test.go | 2 +- pkg/install/install.go | 4 +- pkg/install/install_test.go | 4 +- pkg/install/resources.go | 8 +-- pkg/itemblock/actions/pod_action.go | 6 +- pkg/itemblock/actions/pod_action_test.go | 6 +- pkg/itemblock/actions/pvc_action.go | 14 ++-- pkg/itemblock/actions/pvc_action_test.go | 12 ++-- .../actions/service_account_action.go | 8 +-- .../actions/service_account_action_test.go | 8 +-- pkg/itemoperation/backup_operation.go | 2 +- pkg/itemoperation/restore_operation.go | 2 +- pkg/itemoperationmap/backup_operation_map.go | 6 +- pkg/itemoperationmap/restore_operation_map.go | 6 +- pkg/kopia/kopia_log_test.go | 2 +- pkg/label/label.go | 2 +- pkg/nodeagent/node_agent.go | 4 +- pkg/nodeagent/node_agent_test.go | 6 +- pkg/persistence/mocks/backup_store.go | 10 +-- pkg/persistence/object_store.go | 14 ++-- pkg/persistence/object_store_test.go | 22 +++---- .../v1/restartable_backup_item_action.go | 10 +-- .../v1/restartable_backup_item_action_test.go | 12 ++-- .../v2/restartable_backup_item_action.go | 12 ++-- .../v2/restartable_backup_item_action_test.go | 12 ++-- .../v1/restartable_item_block_action.go | 10 +-- .../v1/restartable_item_block_action_test.go | 12 ++-- pkg/plugin/clientmgmt/manager.go | 30 ++++----- pkg/plugin/clientmgmt/manager_test.go | 22 +++---- .../clientmgmt/process/client_builder.go | 10 +-- .../clientmgmt/process/client_builder_test.go | 12 ++-- pkg/plugin/clientmgmt/process/process.go | 2 +- pkg/plugin/clientmgmt/process/process_test.go | 4 +- pkg/plugin/clientmgmt/process/registry.go | 6 +- .../clientmgmt/process/registry_test.go | 2 +- .../restartable_delete_item_action.go | 6 +- .../restartable_delete_item_action_test.go | 12 ++-- .../clientmgmt/restartable_object_store.go | 6 +- .../restartable_object_store_test.go | 8 +-- .../v1/restartable_restore_item_action.go | 8 +-- .../restartable_restore_item_action_test.go | 12 ++-- .../v2/restartable_restore_item_action.go | 12 ++-- .../restartable_restore_item_action_test.go | 12 ++-- .../v1/restartable_volume_snapshotter.go | 6 +- .../v1/restartable_volume_snapshotter_test.go | 8 +-- pkg/plugin/framework/action_resolver.go | 16 ++--- pkg/plugin/framework/action_resolver_test.go | 4 +- pkg/plugin/framework/backup_item_action.go | 4 +- .../framework/backup_item_action_client.go | 8 +-- .../framework/backup_item_action_server.go | 10 +-- .../framework/backup_item_action_test.go | 12 ++-- .../backupitemaction/v2/backup_item_action.go | 4 +- .../v2/backup_item_action_client.go | 8 +-- .../v2/backup_item_action_server.go | 12 ++-- .../v2/backup_item_action_test.go | 14 ++-- .../framework/common/client_dispenser_test.go | 2 +- pkg/plugin/framework/common/client_errors.go | 2 +- .../framework/common/plugin_base_test.go | 2 +- .../framework/common/plugin_config_test.go | 2 +- pkg/plugin/framework/common/server_errors.go | 4 +- pkg/plugin/framework/delete_item_action.go | 4 +- .../framework/delete_item_action_client.go | 6 +- .../framework/delete_item_action_server.go | 8 +-- pkg/plugin/framework/examples_test.go | 2 +- pkg/plugin/framework/import_test.go | 2 +- .../itemblockaction/v1/item_block_action.go | 4 +- .../v1/item_block_action_client.go | 8 +-- .../v1/item_block_action_server.go | 12 ++-- .../v1/item_block_action_test.go | 14 ++-- pkg/plugin/framework/logger.go | 2 +- pkg/plugin/framework/logger_test.go | 2 +- pkg/plugin/framework/object_store.go | 4 +- pkg/plugin/framework/object_store_client.go | 4 +- pkg/plugin/framework/object_store_server.go | 6 +- pkg/plugin/framework/plugin_lister.go | 4 +- pkg/plugin/framework/restore_item_action.go | 4 +- .../framework/restore_item_action_client.go | 8 +-- .../framework/restore_item_action_server.go | 10 +-- .../v2/restore_item_action.go | 4 +- .../v2/restore_item_action_client.go | 10 +-- .../v2/restore_item_action_server.go | 12 ++-- pkg/plugin/framework/server.go | 10 +-- pkg/plugin/framework/volume_snapshotter.go | 4 +- .../framework/volume_snapshotter_client.go | 4 +- .../framework/volume_snapshotter_server.go | 6 +- .../v2/BackupItemAction.pb.go | 2 +- .../itemblockaction/v1/ItemBlockAction.pb.go | 2 +- .../v2/RestoreItemAction.pb.go | 2 +- pkg/plugin/mocks/manager.go | 14 ++-- pkg/plugin/mocks/process_factory.go | 2 +- pkg/plugin/proto/BackupItemAction.proto | 2 +- pkg/plugin/proto/DeleteItemAction.proto | 2 +- pkg/plugin/proto/ObjectStore.proto | 2 +- pkg/plugin/proto/PluginLister.proto | 2 +- pkg/plugin/proto/RestoreItemAction.proto | 2 +- pkg/plugin/proto/Shared.proto | 2 +- pkg/plugin/proto/VolumeSnapshotter.proto | 2 +- .../v2/BackupItemAction.proto | 2 +- .../itemblockaction/v1/ItemBlockAction.proto | 2 +- .../v2/RestoreItemAction.proto | 2 +- .../volumehelper/volume_policy_helper.go | 12 ++-- .../volumehelper/volume_policy_helper_test.go | 8 +-- .../backupitemaction/v1/backup_item_action.go | 4 +- .../backupitemaction/v2/backup_item_action.go | 4 +- pkg/plugin/velero/delete_item_action.go | 2 +- .../itemblockaction/v1/item_block_action.go | 4 +- pkg/plugin/velero/mocks/DeleteItemAction.go | 2 +- .../backupitemaction/v1/BackupItemAction.go | 4 +- .../backupitemaction/v2/BackupItemAction.go | 4 +- .../itemblockaction/v1/ItemBlockAction.go | 4 +- .../restoreitemaction/v1/RestoreItemAction.go | 2 +- .../restoreitemaction/v2/RestoreItemAction.go | 4 +- .../velero/restore_item_action_shared.go | 2 +- .../v1/restore_item_action.go | 2 +- .../v2/restore_item_action.go | 4 +- pkg/podexec/pod_command_executor.go | 2 +- pkg/podexec/pod_command_executor_test.go | 4 +- pkg/podvolume/backup_micro_service.go | 12 ++-- pkg/podvolume/backup_micro_service_test.go | 12 ++-- pkg/podvolume/backupper.go | 26 ++++---- pkg/podvolume/backupper_factory.go | 4 +- pkg/podvolume/backupper_test.go | 10 +-- pkg/podvolume/mocks/restorer.go | 4 +- pkg/podvolume/restore_micro_service.go | 12 ++-- pkg/podvolume/restore_micro_service_test.go | 12 ++-- pkg/podvolume/restorer.go | 18 +++--- pkg/podvolume/restorer_factory.go | 4 +- pkg/podvolume/restorer_test.go | 10 +-- pkg/podvolume/snaphost_tracker_test.go | 2 +- pkg/podvolume/util.go | 12 ++-- pkg/podvolume/util_test.go | 4 +- pkg/repository/backup_repo_op.go | 4 +- pkg/repository/backup_repo_op_test.go | 4 +- pkg/repository/config/azure.go | 2 +- pkg/repository/config/azure_test.go | 2 +- pkg/repository/ensurer.go | 2 +- pkg/repository/ensurer_test.go | 4 +- pkg/repository/keys/keys.go | 2 +- pkg/repository/maintenance/maintenance.go | 16 ++--- .../maintenance/maintenance_test.go | 18 +++--- pkg/repository/manager/manager.go | 10 +-- pkg/repository/manager/manager_test.go | 2 +- pkg/repository/mocks/Manager.go | 2 +- pkg/repository/provider/provider.go | 2 +- pkg/repository/provider/unified_repo.go | 12 ++-- pkg/repository/provider/unified_repo_test.go | 12 ++-- .../udmrepo/kopialib/backend/azure.go | 6 +- .../backend/azure/azure_storage_wrapper.go | 6 +- .../udmrepo/kopialib/backend/azure_test.go | 4 +- .../udmrepo/kopialib/backend/common.go | 2 +- .../udmrepo/kopialib/backend/common_test.go | 2 +- .../udmrepo/kopialib/backend/file_system.go | 4 +- .../kopialib/backend/file_system_test.go | 4 +- .../udmrepo/kopialib/backend/gcs.go | 4 +- .../udmrepo/kopialib/backend/gcs_test.go | 4 +- pkg/repository/udmrepo/kopialib/backend/s3.go | 4 +- .../udmrepo/kopialib/backend/s3_test.go | 4 +- .../udmrepo/kopialib/backend/utils_test.go | 2 +- pkg/repository/udmrepo/kopialib/lib_repo.go | 6 +- .../udmrepo/kopialib/lib_repo_test.go | 6 +- pkg/repository/udmrepo/kopialib/repo_init.go | 6 +- .../udmrepo/kopialib/repo_init_test.go | 10 +-- pkg/repository/udmrepo/mocks/BackupRepo.go | 2 +- .../udmrepo/mocks/BackupRepoService.go | 2 +- pkg/repository/udmrepo/mocks/ObjectWriter.go | 2 +- pkg/repository/udmrepo/service/service.go | 4 +- pkg/restic/common.go | 8 +-- pkg/restic/common_test.go | 4 +- pkg/restic/exec_commands.go | 6 +- pkg/restic/exec_commands_test.go | 4 +- .../actions/add_pvc_from_pod_action.go | 4 +- .../actions/add_pvc_from_pod_action_test.go | 6 +- .../actions/admissionwebhook_config_action.go | 4 +- .../admissionwebhook_config_action_test.go | 4 +- pkg/restore/actions/apiservice_action.go | 2 +- pkg/restore/actions/apiservice_action_test.go | 4 +- .../actions/change_image_name_action.go | 4 +- .../actions/change_image_name_action_test.go | 4 +- .../actions/change_storageclass_action.go | 4 +- .../change_storageclass_action_test.go | 4 +- .../actions/clusterrolebinding_action.go | 2 +- .../actions/clusterrolebinding_action_test.go | 6 +- .../crd_v1_preserve_unknown_fields_action.go | 2 +- ..._v1_preserve_unknown_fields_action_test.go | 8 +-- pkg/restore/actions/csi/pvc_action.go | 22 +++---- pkg/restore/actions/csi/pvc_action_test.go | 20 +++--- .../actions/csi/volumesnapshot_action.go | 14 ++-- .../actions/csi/volumesnapshot_action_test.go | 12 ++-- .../actions/csi/volumesnapshotclass_action.go | 8 +-- .../csi/volumesnapshotclass_action_test.go | 10 +-- .../csi/volumesnapshotcontent_action.go | 14 ++-- .../csi/volumesnapshotcontent_action_test.go | 14 ++-- .../actions/dataupload_retrieve_action.go | 10 +-- .../dataupload_retrieve_action_test.go | 12 ++-- .../actions/init_restorehook_pod_action.go | 6 +- .../init_restorehook_pod_action_test.go | 10 +-- pkg/restore/actions/job_action.go | 2 +- pkg/restore/actions/job_action_test.go | 4 +- pkg/restore/actions/pod_action.go | 4 +- pkg/restore/actions/pod_action_test.go | 6 +- .../actions/pod_volume_restore_action.go | 22 +++---- .../actions/pod_volume_restore_action_test.go | 16 ++--- pkg/restore/actions/pvc_action.go | 8 +-- pkg/restore/actions/pvc_action_test.go | 8 +-- pkg/restore/actions/rolebinding_action.go | 2 +- .../actions/rolebinding_action_test.go | 6 +- pkg/restore/actions/secret_action.go | 4 +- pkg/restore/actions/secret_action_test.go | 4 +- pkg/restore/actions/service_account_action.go | 4 +- .../actions/service_account_action_test.go | 4 +- pkg/restore/actions/service_action.go | 4 +- pkg/restore/actions/service_action_test.go | 8 +-- pkg/restore/merge_service_account_test.go | 2 +- pkg/restore/prioritize_group_version.go | 6 +- pkg/restore/prioritize_group_version_test.go | 4 +- pkg/restore/pv_restorer.go | 8 +-- pkg/restore/pv_restorer_test.go | 12 ++-- pkg/restore/request.go | 10 +-- pkg/restore/restore.go | 56 ++++++++-------- pkg/restore/restore_test.go | 42 ++++++------ pkg/restore/restore_wildcard_test.go | 4 +- pkg/test/fake_controller_runtime_client.go | 4 +- pkg/test/fake_dynamic.go | 2 +- pkg/test/fake_file_system.go | 2 +- pkg/test/mock_pod_command_executor.go | 2 +- pkg/test/tar_writer.go | 2 +- pkg/types/node_agent.go | 2 +- pkg/types/repo_maintenance.go | 2 +- pkg/uploader/cbt/bitmap.go | 2 +- pkg/uploader/cbt/set.go | 4 +- pkg/uploader/cbt/set_test.go | 6 +- pkg/uploader/cbt/types/mocks/Bitmap.go | 2 +- pkg/uploader/kopia/progress.go | 2 +- pkg/uploader/kopia/progress_test.go | 2 +- pkg/uploader/kopia/shim.go | 2 +- pkg/uploader/kopia/shim_test.go | 4 +- pkg/uploader/kopia/snapshot.go | 8 +-- pkg/uploader/kopia/snapshot_test.go | 6 +- pkg/uploader/provider/block.go | 10 +-- pkg/uploader/provider/block_test.go | 12 ++-- pkg/uploader/provider/kopia.go | 14 ++-- pkg/uploader/provider/kopia_test.go | 18 +++--- pkg/uploader/provider/mocks/Provider.go | 4 +- pkg/uploader/provider/provider.go | 8 +-- pkg/uploader/provider/provider_test.go | 8 +-- pkg/uploader/util/uploader_config.go | 2 +- pkg/uploader/util/uploader_config_test.go | 2 +- pkg/util/actionhelpers/pod_helper.go | 4 +- pkg/util/actionhelpers/pvc_helper.go | 4 +- .../actionhelpers/service_account_helper.go | 6 +- pkg/util/azure/storage.go | 4 +- pkg/util/collections/includes_excludes.go | 14 ++-- .../collections/includes_excludes_test.go | 8 +-- pkg/util/csi/util.go | 4 +- pkg/util/csi/util_test.go | 2 +- pkg/util/csi/volume_snapshot.go | 8 +-- pkg/util/csi/volume_snapshot_test.go | 14 ++-- pkg/util/encode/encode.go | 4 +- pkg/util/kube/client.go | 2 +- pkg/util/kube/event_test.go | 2 +- pkg/util/kube/list_watch_test.go | 4 +- pkg/util/kube/node_test.go | 4 +- .../kube/periodical_enqueue_source_test.go | 4 +- pkg/util/kube/pod_test.go | 2 +- pkg/util/kube/predicate_test.go | 2 +- pkg/util/kube/priority_class_test.go | 2 +- pkg/util/kube/pvc_pv_test.go | 4 +- pkg/util/kube/resource_requirements.go | 2 +- pkg/util/kube/secrets_test.go | 4 +- pkg/util/kube/security_context_test.go | 2 +- pkg/util/kube/utils.go | 10 +-- pkg/util/kube/utils_test.go | 6 +- pkg/util/logging/dual_mode_logger_test.go | 2 +- pkg/util/logging/error_location_hook_test.go | 2 +- pkg/util/logging/format_flag.go | 2 +- pkg/util/logging/log_counter_hook.go | 2 +- pkg/util/logging/log_counter_hook_test.go | 2 +- pkg/util/logging/log_level_flag.go | 2 +- pkg/util/logging/log_location_hook.go | 6 +- pkg/util/logging/log_location_hook_test.go | 4 +- pkg/util/podvolume/pod_volume.go | 4 +- pkg/util/podvolume/pod_volume_test.go | 4 +- pkg/util/scheme.go | 4 +- pkg/util/velero/restore/util.go | 2 +- pkg/util/velero/restore/util_test.go | 2 +- pkg/util/velero/velero.go | 2 +- pkg/util/velero/velero_test.go | 6 +- restore-hooks_product-requirements.md | 10 +-- site/README-HUGO.md | 2 +- site/content/_index.md | 4 +- site/content/community/_index.md | 6 +- site/content/docs/main/_index.md | 8 +-- site/content/docs/main/backup-hooks.md | 2 +- site/content/docs/main/backup-reference.md | 2 +- site/content/docs/main/basic-install.md | 4 +- site/content/docs/main/build-from-source.md | 6 +- site/content/docs/main/code-standards.md | 6 +- .../docs/main/contributions/ibm-config.md | 4 +- site/content/docs/main/contributions/minio.md | 10 +-- .../docs/main/contributions/oracle-config.md | 4 +- .../docs/main/csi-snapshot-data-movement.md | 6 +- site/content/docs/main/csi.md | 4 +- site/content/docs/main/custom-plugins.md | 6 +- .../docs/main/customize-installation.md | 8 +-- .../docs/main/data-movement-node-selection.md | 2 +- ...ata-movement-pod-resource-configuration.md | 4 +- site/content/docs/main/examples.md | 2 +- site/content/docs/main/file-system-backup.md | 6 +- site/content/docs/main/image-tagging.md | 2 +- site/content/docs/main/locations.md | 4 +- site/content/docs/main/maintainers.md | 8 +-- site/content/docs/main/migration-case.md | 2 +- site/content/docs/main/overview-plugins.md | 2 +- .../docs/main/plugin-release-instructions.md | 4 +- .../content/docs/main/release-instructions.md | 14 ++-- .../docs/main/repository-maintenance.md | 4 +- site/content/docs/main/restore-reference.md | 2 +- .../docs/main/self-signed-certificates.md | 2 +- site/content/docs/main/start-contributing.md | 10 +-- site/content/docs/main/support-process.md | 2 +- .../node-agent-configmap.md | 4 +- site/content/docs/main/supported-providers.md | 14 ++-- site/content/docs/main/tilt.md | 6 +- site/content/docs/main/troubleshooting.md | 4 +- site/content/docs/main/upgrade-to-1.18.md | 2 +- site/content/docs/v1.0.0/_index.md | 12 ++-- site/content/docs/v1.0.0/aws-config.md | 4 +- site/content/docs/v1.0.0/azure-config.md | 4 +- site/content/docs/v1.0.0/build-from-source.md | 10 +-- site/content/docs/v1.0.0/faq.md | 2 +- site/content/docs/v1.0.0/gcp-config.md | 4 +- site/content/docs/v1.0.0/get-started.md | 6 +- site/content/docs/v1.0.0/hooks.md | 2 +- site/content/docs/v1.0.0/ibm-config.md | 4 +- site/content/docs/v1.0.0/image-tagging.md | 2 +- .../docs/v1.0.0/migrating-to-velero.md | 2 +- site/content/docs/v1.0.0/oracle-config.md | 4 +- site/content/docs/v1.0.0/plugins.md | 8 +-- site/content/docs/v1.0.0/restic.md | 2 +- site/content/docs/v1.0.0/support-matrix.md | 4 +- site/content/docs/v1.0.0/troubleshooting.md | 2 +- site/content/docs/v1.0.0/upgrade-to-1.0.md | 4 +- site/content/docs/v1.1.0/_index.md | 8 +-- site/content/docs/v1.1.0/aws-config.md | 4 +- site/content/docs/v1.1.0/azure-config.md | 4 +- site/content/docs/v1.1.0/build-from-source.md | 6 +- site/content/docs/v1.1.0/development.md | 2 +- site/content/docs/v1.1.0/faq.md | 2 +- site/content/docs/v1.1.0/gcp-config.md | 4 +- site/content/docs/v1.1.0/get-started.md | 6 +- site/content/docs/v1.1.0/hooks.md | 2 +- site/content/docs/v1.1.0/ibm-config.md | 4 +- site/content/docs/v1.1.0/image-tagging.md | 2 +- .../docs/v1.1.0/migrating-to-velero.md | 2 +- site/content/docs/v1.1.0/oracle-config.md | 4 +- site/content/docs/v1.1.0/plugins.md | 8 +-- site/content/docs/v1.1.0/restic.md | 2 +- .../content/docs/v1.1.0/start-contributing.md | 6 +- site/content/docs/v1.1.0/support-matrix.md | 4 +- site/content/docs/v1.1.0/troubleshooting.md | 2 +- site/content/docs/v1.1.0/upgrade-to-1.1.md | 2 +- site/content/docs/v1.10/_index.md | 8 +-- site/content/docs/v1.10/backup-hooks.md | 2 +- site/content/docs/v1.10/backup-reference.md | 2 +- site/content/docs/v1.10/basic-install.md | 4 +- site/content/docs/v1.10/build-from-source.md | 6 +- site/content/docs/v1.10/code-standards.md | 6 +- .../docs/v1.10/contributions/ibm-config.md | 4 +- .../content/docs/v1.10/contributions/minio.md | 8 +-- .../docs/v1.10/contributions/oracle-config.md | 4 +- site/content/docs/v1.10/csi.md | 6 +- site/content/docs/v1.10/custom-plugins.md | 6 +- .../docs/v1.10/customize-installation.md | 8 +-- site/content/docs/v1.10/examples.md | 2 +- site/content/docs/v1.10/file-system-backup.md | 4 +- site/content/docs/v1.10/image-tagging.md | 2 +- site/content/docs/v1.10/locations.md | 4 +- site/content/docs/v1.10/maintainers.md | 8 +-- site/content/docs/v1.10/migration-case.md | 2 +- site/content/docs/v1.10/overview-plugins.md | 2 +- .../docs/v1.10/plugin-release-instructions.md | 4 +- .../docs/v1.10/release-instructions.md | 14 ++-- .../docs/v1.10/self-signed-certificates.md | 2 +- site/content/docs/v1.10/start-contributing.md | 10 +-- site/content/docs/v1.10/support-process.md | 2 +- .../content/docs/v1.10/supported-providers.md | 16 ++--- site/content/docs/v1.10/tilt.md | 6 +- site/content/docs/v1.10/troubleshooting.md | 2 +- site/content/docs/v1.10/upgrade-to-1.10.md | 2 +- site/content/docs/v1.11/_index.md | 8 +-- site/content/docs/v1.11/backup-hooks.md | 2 +- site/content/docs/v1.11/backup-reference.md | 2 +- site/content/docs/v1.11/basic-install.md | 4 +- site/content/docs/v1.11/build-from-source.md | 6 +- site/content/docs/v1.11/code-standards.md | 6 +- .../docs/v1.11/contributions/ibm-config.md | 4 +- .../content/docs/v1.11/contributions/minio.md | 8 +-- .../docs/v1.11/contributions/oracle-config.md | 4 +- site/content/docs/v1.11/csi.md | 6 +- site/content/docs/v1.11/custom-plugins.md | 6 +- .../docs/v1.11/customize-installation.md | 8 +-- site/content/docs/v1.11/examples.md | 2 +- site/content/docs/v1.11/file-system-backup.md | 4 +- site/content/docs/v1.11/image-tagging.md | 2 +- site/content/docs/v1.11/locations.md | 4 +- site/content/docs/v1.11/maintainers.md | 8 +-- site/content/docs/v1.11/migration-case.md | 2 +- site/content/docs/v1.11/overview-plugins.md | 2 +- .../docs/v1.11/plugin-release-instructions.md | 4 +- .../docs/v1.11/release-instructions.md | 14 ++-- .../docs/v1.11/self-signed-certificates.md | 2 +- site/content/docs/v1.11/start-contributing.md | 10 +-- site/content/docs/v1.11/support-process.md | 2 +- .../content/docs/v1.11/supported-providers.md | 16 ++--- site/content/docs/v1.11/tilt.md | 6 +- site/content/docs/v1.11/troubleshooting.md | 2 +- site/content/docs/v1.11/upgrade-to-1.11.md | 2 +- site/content/docs/v1.12/_index.md | 8 +-- site/content/docs/v1.12/backup-hooks.md | 2 +- site/content/docs/v1.12/backup-reference.md | 2 +- site/content/docs/v1.12/basic-install.md | 4 +- site/content/docs/v1.12/build-from-source.md | 6 +- site/content/docs/v1.12/code-standards.md | 6 +- .../docs/v1.12/contributions/ibm-config.md | 4 +- .../content/docs/v1.12/contributions/minio.md | 8 +-- .../docs/v1.12/contributions/oracle-config.md | 4 +- .../docs/v1.12/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.12/csi.md | 6 +- site/content/docs/v1.12/custom-plugins.md | 6 +- .../docs/v1.12/customize-installation.md | 8 +-- site/content/docs/v1.12/examples.md | 2 +- site/content/docs/v1.12/file-system-backup.md | 4 +- site/content/docs/v1.12/image-tagging.md | 2 +- site/content/docs/v1.12/locations.md | 4 +- site/content/docs/v1.12/maintainers.md | 8 +-- site/content/docs/v1.12/migration-case.md | 2 +- site/content/docs/v1.12/overview-plugins.md | 2 +- .../docs/v1.12/plugin-release-instructions.md | 4 +- .../docs/v1.12/release-instructions.md | 14 ++-- .../docs/v1.12/self-signed-certificates.md | 2 +- site/content/docs/v1.12/start-contributing.md | 10 +-- site/content/docs/v1.12/support-process.md | 2 +- .../content/docs/v1.12/supported-providers.md | 16 ++--- site/content/docs/v1.12/tilt.md | 6 +- site/content/docs/v1.12/troubleshooting.md | 2 +- site/content/docs/v1.12/upgrade-to-1.12.md | 2 +- site/content/docs/v1.13/_index.md | 8 +-- site/content/docs/v1.13/backup-hooks.md | 2 +- site/content/docs/v1.13/backup-reference.md | 2 +- site/content/docs/v1.13/basic-install.md | 4 +- site/content/docs/v1.13/build-from-source.md | 6 +- site/content/docs/v1.13/code-standards.md | 6 +- .../docs/v1.13/contributions/ibm-config.md | 4 +- .../content/docs/v1.13/contributions/minio.md | 10 +-- .../docs/v1.13/contributions/oracle-config.md | 4 +- .../docs/v1.13/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.13/csi.md | 6 +- site/content/docs/v1.13/custom-plugins.md | 6 +- .../docs/v1.13/customize-installation.md | 8 +-- site/content/docs/v1.13/examples.md | 2 +- site/content/docs/v1.13/file-system-backup.md | 4 +- site/content/docs/v1.13/image-tagging.md | 2 +- site/content/docs/v1.13/locations.md | 4 +- site/content/docs/v1.13/maintainers.md | 8 +-- site/content/docs/v1.13/migration-case.md | 2 +- site/content/docs/v1.13/overview-plugins.md | 2 +- .../docs/v1.13/plugin-release-instructions.md | 4 +- .../docs/v1.13/release-instructions.md | 14 ++-- .../docs/v1.13/self-signed-certificates.md | 2 +- site/content/docs/v1.13/start-contributing.md | 10 +-- site/content/docs/v1.13/support-process.md | 2 +- .../content/docs/v1.13/supported-providers.md | 16 ++--- site/content/docs/v1.13/tilt.md | 6 +- site/content/docs/v1.13/troubleshooting.md | 2 +- site/content/docs/v1.13/upgrade-to-1.13.md | 2 +- site/content/docs/v1.14/_index.md | 8 +-- site/content/docs/v1.14/backup-hooks.md | 2 +- site/content/docs/v1.14/backup-reference.md | 2 +- site/content/docs/v1.14/basic-install.md | 4 +- site/content/docs/v1.14/build-from-source.md | 6 +- site/content/docs/v1.14/code-standards.md | 6 +- .../docs/v1.14/contributions/ibm-config.md | 4 +- .../content/docs/v1.14/contributions/minio.md | 10 +-- .../docs/v1.14/contributions/oracle-config.md | 4 +- .../docs/v1.14/csi-snapshot-data-movement.md | 4 +- site/content/docs/v1.14/csi.md | 4 +- site/content/docs/v1.14/custom-plugins.md | 6 +- .../docs/v1.14/customize-installation.md | 8 +-- site/content/docs/v1.14/examples.md | 2 +- site/content/docs/v1.14/file-system-backup.md | 4 +- site/content/docs/v1.14/image-tagging.md | 2 +- site/content/docs/v1.14/locations.md | 4 +- site/content/docs/v1.14/maintainers.md | 8 +-- site/content/docs/v1.14/migration-case.md | 2 +- site/content/docs/v1.14/overview-plugins.md | 2 +- .../docs/v1.14/plugin-release-instructions.md | 4 +- .../docs/v1.14/release-instructions.md | 14 ++-- .../docs/v1.14/self-signed-certificates.md | 2 +- site/content/docs/v1.14/start-contributing.md | 10 +-- site/content/docs/v1.14/support-process.md | 2 +- .../content/docs/v1.14/supported-providers.md | 14 ++-- site/content/docs/v1.14/tilt.md | 6 +- site/content/docs/v1.14/troubleshooting.md | 2 +- site/content/docs/v1.14/upgrade-to-1.14.md | 2 +- site/content/docs/v1.15/_index.md | 8 +-- site/content/docs/v1.15/backup-hooks.md | 2 +- site/content/docs/v1.15/backup-reference.md | 2 +- site/content/docs/v1.15/basic-install.md | 4 +- site/content/docs/v1.15/build-from-source.md | 6 +- site/content/docs/v1.15/code-standards.md | 6 +- .../docs/v1.15/contributions/ibm-config.md | 4 +- .../content/docs/v1.15/contributions/minio.md | 10 +-- .../docs/v1.15/contributions/oracle-config.md | 4 +- .../docs/v1.15/csi-snapshot-data-movement.md | 6 +- site/content/docs/v1.15/csi.md | 4 +- site/content/docs/v1.15/custom-plugins.md | 6 +- .../docs/v1.15/customize-installation.md | 8 +-- site/content/docs/v1.15/examples.md | 2 +- site/content/docs/v1.15/file-system-backup.md | 6 +- site/content/docs/v1.15/image-tagging.md | 2 +- site/content/docs/v1.15/locations.md | 4 +- site/content/docs/v1.15/maintainers.md | 8 +-- site/content/docs/v1.15/migration-case.md | 2 +- site/content/docs/v1.15/overview-plugins.md | 2 +- .../docs/v1.15/plugin-release-instructions.md | 4 +- .../docs/v1.15/release-instructions.md | 14 ++-- site/content/docs/v1.15/restore-reference.md | 2 +- .../docs/v1.15/self-signed-certificates.md | 2 +- site/content/docs/v1.15/start-contributing.md | 10 +-- site/content/docs/v1.15/support-process.md | 2 +- .../content/docs/v1.15/supported-providers.md | 14 ++-- site/content/docs/v1.15/tilt.md | 6 +- site/content/docs/v1.15/troubleshooting.md | 2 +- site/content/docs/v1.15/upgrade-to-1.15.md | 2 +- site/content/docs/v1.16/_index.md | 8 +-- site/content/docs/v1.16/backup-hooks.md | 2 +- site/content/docs/v1.16/backup-reference.md | 2 +- site/content/docs/v1.16/basic-install.md | 4 +- site/content/docs/v1.16/build-from-source.md | 6 +- site/content/docs/v1.16/code-standards.md | 6 +- .../docs/v1.16/contributions/ibm-config.md | 4 +- .../content/docs/v1.16/contributions/minio.md | 10 +-- .../docs/v1.16/contributions/oracle-config.md | 4 +- .../docs/v1.16/csi-snapshot-data-movement.md | 6 +- site/content/docs/v1.16/csi.md | 4 +- site/content/docs/v1.16/custom-plugins.md | 6 +- .../docs/v1.16/customize-installation.md | 8 +-- site/content/docs/v1.16/examples.md | 2 +- site/content/docs/v1.16/file-system-backup.md | 6 +- site/content/docs/v1.16/image-tagging.md | 2 +- site/content/docs/v1.16/locations.md | 4 +- site/content/docs/v1.16/maintainers.md | 8 +-- site/content/docs/v1.16/migration-case.md | 2 +- site/content/docs/v1.16/overview-plugins.md | 2 +- .../docs/v1.16/plugin-release-instructions.md | 4 +- .../docs/v1.16/release-instructions.md | 14 ++-- .../docs/v1.16/repository-maintenance.md | 4 +- site/content/docs/v1.16/restore-reference.md | 2 +- .../docs/v1.16/self-signed-certificates.md | 2 +- site/content/docs/v1.16/start-contributing.md | 10 +-- site/content/docs/v1.16/support-process.md | 2 +- .../content/docs/v1.16/supported-providers.md | 14 ++-- site/content/docs/v1.16/tilt.md | 6 +- site/content/docs/v1.16/troubleshooting.md | 2 +- site/content/docs/v1.16/upgrade-to-1.16.md | 2 +- site/content/docs/v1.17/_index.md | 8 +-- site/content/docs/v1.17/backup-hooks.md | 2 +- site/content/docs/v1.17/backup-reference.md | 2 +- site/content/docs/v1.17/basic-install.md | 4 +- site/content/docs/v1.17/build-from-source.md | 6 +- site/content/docs/v1.17/code-standards.md | 6 +- .../docs/v1.17/contributions/ibm-config.md | 4 +- .../content/docs/v1.17/contributions/minio.md | 10 +-- .../docs/v1.17/contributions/oracle-config.md | 4 +- .../docs/v1.17/csi-snapshot-data-movement.md | 6 +- site/content/docs/v1.17/csi.md | 4 +- site/content/docs/v1.17/custom-plugins.md | 6 +- .../docs/v1.17/customize-installation.md | 8 +-- .../v1.17/data-movement-node-selection.md | 2 +- site/content/docs/v1.17/examples.md | 2 +- site/content/docs/v1.17/file-system-backup.md | 6 +- site/content/docs/v1.17/image-tagging.md | 2 +- site/content/docs/v1.17/locations.md | 4 +- site/content/docs/v1.17/maintainers.md | 8 +-- site/content/docs/v1.17/migration-case.md | 2 +- site/content/docs/v1.17/overview-plugins.md | 2 +- .../docs/v1.17/plugin-release-instructions.md | 4 +- .../docs/v1.17/release-instructions.md | 14 ++-- .../docs/v1.17/repository-maintenance.md | 4 +- site/content/docs/v1.17/restore-reference.md | 4 +- .../docs/v1.17/self-signed-certificates.md | 2 +- site/content/docs/v1.17/start-contributing.md | 10 +-- site/content/docs/v1.17/support-process.md | 2 +- .../content/docs/v1.17/supported-providers.md | 14 ++-- site/content/docs/v1.17/tilt.md | 6 +- site/content/docs/v1.17/troubleshooting.md | 4 +- site/content/docs/v1.17/upgrade-to-1.17.md | 2 +- site/content/docs/v1.18/_index.md | 8 +-- site/content/docs/v1.18/backup-hooks.md | 2 +- site/content/docs/v1.18/backup-reference.md | 2 +- site/content/docs/v1.18/basic-install.md | 4 +- site/content/docs/v1.18/build-from-source.md | 6 +- site/content/docs/v1.18/code-standards.md | 6 +- .../docs/v1.18/contributions/ibm-config.md | 4 +- .../content/docs/v1.18/contributions/minio.md | 10 +-- .../docs/v1.18/contributions/oracle-config.md | 4 +- .../docs/v1.18/csi-snapshot-data-movement.md | 6 +- site/content/docs/v1.18/csi.md | 4 +- site/content/docs/v1.18/custom-plugins.md | 6 +- .../docs/v1.18/customize-installation.md | 8 +-- .../v1.18/data-movement-node-selection.md | 2 +- ...ata-movement-pod-resource-configuration.md | 4 +- site/content/docs/v1.18/examples.md | 2 +- site/content/docs/v1.18/file-system-backup.md | 6 +- site/content/docs/v1.18/image-tagging.md | 2 +- site/content/docs/v1.18/locations.md | 4 +- site/content/docs/v1.18/maintainers.md | 8 +-- site/content/docs/v1.18/migration-case.md | 2 +- site/content/docs/v1.18/overview-plugins.md | 2 +- .../docs/v1.18/plugin-release-instructions.md | 4 +- .../docs/v1.18/release-instructions.md | 14 ++-- .../docs/v1.18/repository-maintenance.md | 4 +- site/content/docs/v1.18/restore-reference.md | 2 +- .../docs/v1.18/self-signed-certificates.md | 2 +- site/content/docs/v1.18/start-contributing.md | 10 +-- site/content/docs/v1.18/support-process.md | 2 +- .../node-agent-configmap.md | 4 +- .../content/docs/v1.18/supported-providers.md | 14 ++-- site/content/docs/v1.18/tilt.md | 6 +- site/content/docs/v1.18/troubleshooting.md | 4 +- site/content/docs/v1.18/upgrade-to-1.18.md | 2 +- site/content/docs/v1.2.0/_index.md | 8 +-- site/content/docs/v1.2.0/basic-install.md | 2 +- site/content/docs/v1.2.0/build-from-source.md | 6 +- site/content/docs/v1.2.0/code-standards.md | 6 +- .../docs/v1.2.0/contributions/ibm-config.md | 4 +- .../docs/v1.2.0/contributions/minio.md | 6 +- .../v1.2.0/contributions/oracle-config.md | 4 +- site/content/docs/v1.2.0/custom-plugins.md | 8 +-- .../docs/v1.2.0/customize-installation.md | 4 +- site/content/docs/v1.2.0/faq.md | 2 +- site/content/docs/v1.2.0/hooks.md | 2 +- site/content/docs/v1.2.0/image-tagging.md | 2 +- site/content/docs/v1.2.0/locations.md | 4 +- site/content/docs/v1.2.0/overview-plugins.md | 2 +- site/content/docs/v1.2.0/restic.md | 2 +- .../content/docs/v1.2.0/start-contributing.md | 6 +- .../docs/v1.2.0/supported-providers.md | 16 ++--- site/content/docs/v1.2.0/troubleshooting.md | 2 +- site/content/docs/v1.2.0/upgrade-to-1.2.md | 4 +- .../content/docs/v1.2.0/website-guidelines.md | 2 +- site/content/docs/v1.2.0/zenhub.md | 2 +- site/content/docs/v1.3.0/_index.md | 8 +-- site/content/docs/v1.3.0/basic-install.md | 2 +- site/content/docs/v1.3.0/build-from-source.md | 6 +- site/content/docs/v1.3.0/code-standards.md | 6 +- .../docs/v1.3.0/contributions/ibm-config.md | 4 +- .../docs/v1.3.0/contributions/minio.md | 6 +- .../v1.3.0/contributions/oracle-config.md | 4 +- site/content/docs/v1.3.0/csi.md | 2 +- site/content/docs/v1.3.0/custom-plugins.md | 8 +-- .../docs/v1.3.0/customize-installation.md | 6 +- site/content/docs/v1.3.0/faq.md | 2 +- site/content/docs/v1.3.0/hooks.md | 2 +- site/content/docs/v1.3.0/image-tagging.md | 2 +- site/content/docs/v1.3.0/locations.md | 4 +- site/content/docs/v1.3.0/overview-plugins.md | 2 +- .../docs/v1.3.0/release-instructions.md | 2 +- site/content/docs/v1.3.0/restic.md | 2 +- .../content/docs/v1.3.0/start-contributing.md | 6 +- .../docs/v1.3.0/supported-providers.md | 16 ++--- site/content/docs/v1.3.0/troubleshooting.md | 2 +- site/content/docs/v1.3.0/upgrade-to-1.3.md | 2 +- .../content/docs/v1.3.0/website-guidelines.md | 2 +- site/content/docs/v1.3.0/zenhub.md | 2 +- site/content/docs/v1.3.1/_index.md | 8 +-- site/content/docs/v1.3.1/basic-install.md | 2 +- site/content/docs/v1.3.1/build-from-source.md | 6 +- site/content/docs/v1.3.1/code-standards.md | 6 +- .../docs/v1.3.1/contributions/ibm-config.md | 4 +- .../docs/v1.3.1/contributions/minio.md | 6 +- .../v1.3.1/contributions/oracle-config.md | 4 +- site/content/docs/v1.3.1/csi.md | 2 +- site/content/docs/v1.3.1/custom-plugins.md | 8 +-- .../docs/v1.3.1/customize-installation.md | 6 +- site/content/docs/v1.3.1/faq.md | 2 +- site/content/docs/v1.3.1/hooks.md | 2 +- site/content/docs/v1.3.1/image-tagging.md | 2 +- site/content/docs/v1.3.1/locations.md | 4 +- site/content/docs/v1.3.1/overview-plugins.md | 2 +- .../docs/v1.3.1/release-instructions.md | 2 +- site/content/docs/v1.3.1/restic.md | 2 +- .../content/docs/v1.3.1/start-contributing.md | 6 +- .../docs/v1.3.1/supported-providers.md | 16 ++--- site/content/docs/v1.3.1/troubleshooting.md | 2 +- site/content/docs/v1.3.1/upgrade-to-1.3.md | 4 +- .../content/docs/v1.3.1/website-guidelines.md | 2 +- site/content/docs/v1.3.1/zenhub.md | 2 +- site/content/docs/v1.3.2/_index.md | 8 +-- site/content/docs/v1.3.2/basic-install.md | 2 +- site/content/docs/v1.3.2/build-from-source.md | 6 +- site/content/docs/v1.3.2/code-standards.md | 6 +- .../docs/v1.3.2/contributions/ibm-config.md | 4 +- .../docs/v1.3.2/contributions/minio.md | 6 +- .../v1.3.2/contributions/oracle-config.md | 4 +- site/content/docs/v1.3.2/csi.md | 6 +- site/content/docs/v1.3.2/custom-plugins.md | 8 +-- .../docs/v1.3.2/customize-installation.md | 6 +- site/content/docs/v1.3.2/faq.md | 2 +- site/content/docs/v1.3.2/hooks.md | 2 +- site/content/docs/v1.3.2/image-tagging.md | 2 +- site/content/docs/v1.3.2/locations.md | 4 +- site/content/docs/v1.3.2/overview-plugins.md | 2 +- .../docs/v1.3.2/release-instructions.md | 2 +- site/content/docs/v1.3.2/restic.md | 2 +- .../content/docs/v1.3.2/start-contributing.md | 6 +- .../docs/v1.3.2/supported-providers.md | 20 +++--- site/content/docs/v1.3.2/troubleshooting.md | 2 +- site/content/docs/v1.3.2/upgrade-to-1.3.md | 6 +- .../content/docs/v1.3.2/website-guidelines.md | 2 +- site/content/docs/v1.3.2/zenhub.md | 2 +- site/content/docs/v1.4/_index.md | 8 +-- site/content/docs/v1.4/basic-install.md | 4 +- site/content/docs/v1.4/build-from-source.md | 6 +- site/content/docs/v1.4/code-standards.md | 6 +- .../docs/v1.4/contributions/ibm-config.md | 4 +- site/content/docs/v1.4/contributions/minio.md | 6 +- .../docs/v1.4/contributions/oracle-config.md | 4 +- site/content/docs/v1.4/csi.md | 4 +- site/content/docs/v1.4/custom-plugins.md | 8 +-- .../docs/v1.4/customize-installation.md | 8 +-- site/content/docs/v1.4/hooks.md | 2 +- site/content/docs/v1.4/image-tagging.md | 2 +- site/content/docs/v1.4/locations.md | 4 +- site/content/docs/v1.4/overview-plugins.md | 2 +- .../content/docs/v1.4/release-instructions.md | 4 +- site/content/docs/v1.4/restic.md | 2 +- site/content/docs/v1.4/start-contributing.md | 10 +-- site/content/docs/v1.4/supported-providers.md | 16 ++--- site/content/docs/v1.4/troubleshooting.md | 2 +- site/content/docs/v1.4/upgrade-to-1.4.md | 12 ++-- site/content/docs/v1.4/website-guidelines.md | 2 +- site/content/docs/v1.4/zenhub.md | 2 +- site/content/docs/v1.5/_index.md | 8 +-- site/content/docs/v1.5/backup-hooks.md | 2 +- site/content/docs/v1.5/basic-install.md | 4 +- site/content/docs/v1.5/build-from-source.md | 6 +- site/content/docs/v1.5/code-standards.md | 6 +- .../docs/v1.5/contributions/ibm-config.md | 4 +- site/content/docs/v1.5/contributions/minio.md | 6 +- .../docs/v1.5/contributions/oracle-config.md | 4 +- site/content/docs/v1.5/csi.md | 2 +- site/content/docs/v1.5/custom-plugins.md | 8 +-- .../docs/v1.5/customize-installation.md | 8 +-- site/content/docs/v1.5/examples.md | 2 +- site/content/docs/v1.5/image-tagging.md | 2 +- site/content/docs/v1.5/locations.md | 4 +- site/content/docs/v1.5/maintainers.md | 8 +-- site/content/docs/v1.5/overview-plugins.md | 2 +- .../content/docs/v1.5/release-instructions.md | 6 +- site/content/docs/v1.5/restic.md | 2 +- site/content/docs/v1.5/start-contributing.md | 10 +-- site/content/docs/v1.5/supported-providers.md | 16 ++--- site/content/docs/v1.5/tilt.md | 6 +- site/content/docs/v1.5/troubleshooting.md | 2 +- site/content/docs/v1.5/upgrade-to-1.5.md | 12 ++-- site/content/docs/v1.6/_index.md | 8 +-- site/content/docs/v1.6/backup-hooks.md | 2 +- site/content/docs/v1.6/basic-install.md | 4 +- site/content/docs/v1.6/build-from-source.md | 6 +- site/content/docs/v1.6/code-standards.md | 6 +- .../docs/v1.6/contributions/ibm-config.md | 4 +- site/content/docs/v1.6/contributions/minio.md | 6 +- .../docs/v1.6/contributions/oracle-config.md | 4 +- site/content/docs/v1.6/csi.md | 2 +- site/content/docs/v1.6/custom-plugins.md | 8 +-- .../docs/v1.6/customize-installation.md | 8 +-- site/content/docs/v1.6/examples.md | 2 +- site/content/docs/v1.6/image-tagging.md | 2 +- site/content/docs/v1.6/locations.md | 4 +- site/content/docs/v1.6/maintainers.md | 8 +-- site/content/docs/v1.6/overview-plugins.md | 2 +- .../docs/v1.6/plugin-release-instructions.md | 4 +- .../content/docs/v1.6/release-instructions.md | 12 ++-- site/content/docs/v1.6/restic.md | 2 +- site/content/docs/v1.6/start-contributing.md | 10 +-- site/content/docs/v1.6/supported-providers.md | 16 ++--- site/content/docs/v1.6/tilt.md | 6 +- site/content/docs/v1.6/troubleshooting.md | 2 +- site/content/docs/v1.6/upgrade-to-1.6.md | 8 +-- site/content/docs/v1.7/_index.md | 8 +-- site/content/docs/v1.7/backup-hooks.md | 2 +- site/content/docs/v1.7/basic-install.md | 4 +- site/content/docs/v1.7/build-from-source.md | 6 +- site/content/docs/v1.7/code-standards.md | 6 +- .../docs/v1.7/contributions/ibm-config.md | 4 +- site/content/docs/v1.7/contributions/minio.md | 8 +-- .../docs/v1.7/contributions/oracle-config.md | 4 +- site/content/docs/v1.7/csi.md | 2 +- site/content/docs/v1.7/custom-plugins.md | 8 +-- .../docs/v1.7/customize-installation.md | 8 +-- site/content/docs/v1.7/examples.md | 2 +- site/content/docs/v1.7/image-tagging.md | 2 +- site/content/docs/v1.7/locations.md | 4 +- site/content/docs/v1.7/maintainers.md | 8 +-- site/content/docs/v1.7/overview-plugins.md | 2 +- .../docs/v1.7/plugin-release-instructions.md | 4 +- .../content/docs/v1.7/release-instructions.md | 12 ++-- site/content/docs/v1.7/restic.md | 2 +- site/content/docs/v1.7/start-contributing.md | 10 +-- site/content/docs/v1.7/supported-providers.md | 16 ++--- site/content/docs/v1.7/tilt.md | 6 +- site/content/docs/v1.7/troubleshooting.md | 2 +- site/content/docs/v1.7/upgrade-to-1.7.md | 6 +- site/content/docs/v1.8/_index.md | 8 +-- site/content/docs/v1.8/backup-hooks.md | 2 +- site/content/docs/v1.8/basic-install.md | 2 +- site/content/docs/v1.8/build-from-source.md | 6 +- site/content/docs/v1.8/code-standards.md | 6 +- .../docs/v1.8/contributions/ibm-config.md | 4 +- site/content/docs/v1.8/contributions/minio.md | 8 +-- .../docs/v1.8/contributions/oracle-config.md | 4 +- site/content/docs/v1.8/csi.md | 2 +- site/content/docs/v1.8/custom-plugins.md | 8 +-- .../docs/v1.8/customize-installation.md | 4 +- site/content/docs/v1.8/examples.md | 2 +- site/content/docs/v1.8/image-tagging.md | 2 +- site/content/docs/v1.8/locations.md | 4 +- site/content/docs/v1.8/maintainers.md | 8 +-- site/content/docs/v1.8/overview-plugins.md | 2 +- .../docs/v1.8/plugin-release-instructions.md | 4 +- .../content/docs/v1.8/release-instructions.md | 14 ++-- site/content/docs/v1.8/restic.md | 2 +- site/content/docs/v1.8/start-contributing.md | 10 +-- site/content/docs/v1.8/supported-providers.md | 16 ++--- site/content/docs/v1.8/tilt.md | 6 +- site/content/docs/v1.8/troubleshooting.md | 2 +- site/content/docs/v1.8/upgrade-to-1.8.md | 2 +- site/content/docs/v1.9/_index.md | 8 +-- site/content/docs/v1.9/backup-hooks.md | 2 +- site/content/docs/v1.9/backup-reference.md | 2 +- site/content/docs/v1.9/basic-install.md | 4 +- site/content/docs/v1.9/build-from-source.md | 6 +- site/content/docs/v1.9/code-standards.md | 6 +- .../docs/v1.9/contributions/ibm-config.md | 4 +- site/content/docs/v1.9/contributions/minio.md | 8 +-- .../docs/v1.9/contributions/oracle-config.md | 4 +- site/content/docs/v1.9/csi.md | 6 +- site/content/docs/v1.9/custom-plugins.md | 6 +- .../docs/v1.9/customize-installation.md | 8 +-- site/content/docs/v1.9/examples.md | 2 +- site/content/docs/v1.9/image-tagging.md | 2 +- site/content/docs/v1.9/locations.md | 4 +- site/content/docs/v1.9/maintainers.md | 8 +-- site/content/docs/v1.9/migration-case.md | 2 +- site/content/docs/v1.9/overview-plugins.md | 2 +- .../docs/v1.9/plugin-release-instructions.md | 4 +- .../content/docs/v1.9/release-instructions.md | 14 ++-- site/content/docs/v1.9/restic.md | 2 +- .../docs/v1.9/self-signed-certificates.md | 2 +- site/content/docs/v1.9/start-contributing.md | 10 +-- site/content/docs/v1.9/support-process.md | 2 +- site/content/docs/v1.9/supported-providers.md | 16 ++--- site/content/docs/v1.9/tilt.md | 6 +- site/content/docs/v1.9/troubleshooting.md | 2 +- site/content/docs/v1.9/upgrade-to-1.9.md | 2 +- site/content/plugins/_index.md | 2 +- .../plugins/list/01-amazon-web-services.md | 2 +- .../plugins/list/01-google-cloud-platform.md | 2 +- .../plugins/list/01-microsoft-azure.md | 2 +- site/content/plugins/list/01-vsphere.md | 2 +- .../list/10-container-storage-interface.md | 2 +- ...Back-up-and-Migrate-Kubernetes-Clusters.md | 2 +- .../2019-05-20-velero-1.0-has-arrived.md | 4 +- .../posts/2019-08-22-announcing-velero-1.1.md | 8 +-- .../posts/2019-10-01-announcing-gh-move.md | 4 +- .../posts/2019-11-07-Velero-1.2-Sets-Sail.md | 4 +- .../2020-03-02-Velero-1.3-Voyage-Continues.md | 12 ++-- .../2020-05-26-Velero-1.4-Community-Wave.md | 10 +-- .../posts/2020-05-27-CSI-integration.md | 6 +- ...0-09-16-Velero-1.5-For-And-By-Community.md | 10 +-- ...3-Velero-1.6-Bring-All-Your-Credentials.md | 12 ++-- site/content/posts/2023-04-26-Velero-1.11.md | 18 +++--- site/layouts/404.html | 2 +- test/e2e/README.md | 4 +- test/e2e/backup/backup.go | 12 ++-- test/e2e/backups/deletion.go | 10 +-- test/e2e/backups/sync_backups.go | 10 +-- test/e2e/backups/ttl.go | 10 +-- .../api-group/enable_api_group_extentions.go | 6 +- .../api-group/enable_api_group_versions.go | 10 +-- test/e2e/basic/backup-volume-info/base.go | 12 ++-- .../backup-volume-info/csi_data_mover.go | 6 +- .../basic/backup-volume-info/csi_snapshot.go | 6 +- .../backup-volume-info/filesystem_upload.go | 6 +- .../backup-volume-info/native_snapshot.go | 6 +- .../backup-volume-info/skipped_volumes.go | 6 +- test/e2e/basic/namespace-mapping.go | 6 +- test/e2e/basic/nodeport.go | 8 +-- test/e2e/basic/resources-check/namespaces.go | 4 +- .../resources-check/namespaces_annotation.go | 4 +- test/e2e/basic/resources-check/rbac.go | 4 +- .../basic/resources-check/resources_check.go | 2 +- test/e2e/basic/restore_exec_hooks.go | 8 +-- test/e2e/basic/storage-class-changing.go | 12 ++-- test/e2e/bsl-mgmt/deletion.go | 12 ++-- test/e2e/e2e_suite_test.go | 48 +++++++------- test/e2e/migration/migration.go | 18 +++--- test/e2e/nodeagentconfig/cache_pvc.go | 14 ++-- test/e2e/nodeagentconfig/node-agent-config.go | 18 +++--- .../parallel_files_download.go | 8 +-- .../parallel_files_upload.go | 8 +-- test/e2e/privilegesmgmt/ssr.go | 8 +-- test/e2e/pv-backup/pv-backup-filter.go | 10 +-- .../repo_maintenance_config.go | 18 +++--- test/e2e/resource-filtering/base.go | 6 +- test/e2e/resource-filtering/exclude_label.go | 8 +-- .../resource-filtering/exclude_namespaces.go | 4 +- .../resource-filtering/exclude_resources.go | 6 +- .../resource-filtering/include_namespaces.go | 4 +- .../resource-filtering/include_resources.go | 4 +- test/e2e/resource-filtering/label_selector.go | 6 +- .../resource-filtering/wildcard_namespaces.go | 4 +- .../resourcemodifiers/resource_modifiers.go | 6 +- .../e2e/resourcepolicies/resource_policies.go | 8 +-- test/e2e/scale/multiple_namespaces.go | 4 +- test/e2e/schedule/in_progress.go | 12 ++-- test/e2e/schedule/ordered_resources.go | 12 ++-- test/e2e/schedule/periodical.go | 8 +-- test/e2e/test/test.go | 12 ++-- test/e2e/upgrade/upgrade.go | 14 ++-- test/perf/README.md | 2 +- test/perf/backup/backup.go | 4 +- test/perf/basic/basic.go | 6 +- test/perf/e2e_suite_test.go | 18 +++--- test/perf/metrics/minio.go | 2 +- test/perf/metrics/nfs.go | 2 +- test/perf/metrics/pod.go | 2 +- test/perf/restore/restore.go | 8 +-- test/perf/test/test.go | 14 ++-- test/pkg/client/client.go | 2 +- test/pkg/client/factory.go | 4 +- test/types.go | 4 +- test/util/csi/common.go | 2 +- test/util/eks/eks.go | 2 +- test/util/k8s/client.go | 2 +- test/util/k8s/clusterrolebinding.go | 2 +- test/util/k8s/common.go | 6 +- test/util/k8s/crd.go | 2 +- test/util/k8s/deployment.go | 4 +- test/util/k8s/namespace.go | 4 +- test/util/k8s/node.go | 2 +- test/util/k8s/pod.go | 4 +- test/util/k8s/serviceaccount.go | 2 +- test/util/k8s/statefulset.go | 2 +- test/util/kibishii/kibishii_utils.go | 12 ++-- test/util/metrics/minio.go | 2 +- test/util/providers/aws_utils.go | 4 +- test/util/providers/azure_utils.go | 4 +- test/util/providers/common.go | 6 +- test/util/providers/gcloud_utils.go | 2 +- test/util/report/report.go | 2 +- test/util/velero/install.go | 20 +++--- test/util/velero/velero_utils.go | 24 +++---- 1309 files changed, 4405 insertions(+), 4405 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 6851cf68b..68e065038 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -40,7 +40,7 @@ Please provide the output of the following commands (Pasting long output into a **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "I would like to see this bug fixed as soon as possible" diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 6e4e6841b..6468a2e2f 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1,5 @@ blank_issues_enabled: false contact_links: - name: Velero Q&A - url: https://github.com/vmware-tanzu/velero/discussions/categories/community-support-q-a + url: https://github.com/velero-io/velero/discussions/categories/community-support-q-a about: Have questions about Velero? Please ask them here. diff --git a/.github/ISSUE_TEMPLATE/feature-enhancement-request.md b/.github/ISSUE_TEMPLATE/feature-enhancement-request.md index bf95fd986..7e839def3 100644 --- a/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +++ b/.github/ISSUE_TEMPLATE/feature-enhancement-request.md @@ -26,7 +26,7 @@ about: Suggest an idea for this project **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "The project would be better with this feature added" diff --git a/.gitignore b/.gitignore index ce62679f1..e7e14f74d 100644 --- a/.gitignore +++ b/.gitignore @@ -60,6 +60,6 @@ debug.test* .cache/ # Go telemetry directory created when container sets HOME to working directory -# This happens because Makefile uses 'docker run -w /github.com/vmware-tanzu/velero' +# This happens because Makefile uses 'docker run -w /github.com/velero-io/velero' # and Go's os.UserConfigDir() falls back to $HOME/.config when XDG_CONFIG_HOME is unset .config/ diff --git a/.golangci.yaml b/.golangci.yaml index 72db2986b..582ed84ba 100644 --- a/.golangci.yaml +++ b/.golangci.yaml @@ -423,7 +423,7 @@ formatters: simplify: true goimports: local-prefixes: - - github.com/vmware-tanzu/velero + - github.com/velero-io/velero severity: default: error diff --git a/.goreleaser.yml b/.goreleaser.yml index f206d3f9c..1b30ab300 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -44,7 +44,7 @@ builds: - goos: windows goarch: s390x ldflags: - - -X "github.com/vmware-tanzu/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.ImageRegistry={{ .Env.REGISTRY }}" + - -X "github.com/velero-io/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/velero-io/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/velero-io/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}" -X "github.com/velero-io/velero/pkg/buildinfo.ImageRegistry={{ .Env.REGISTRY }}" archives: - name_template: "{{ .ProjectName }}-{{ .Tag }}-{{ .Os }}-{{ .Arch }}" wrap_in_directory: true diff --git a/ADOPTERS.md b/ADOPTERS.md index 7bc46e9c3..d8f320523 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -82,8 +82,8 @@ If you would like to add your logo to a future `Adopters of Velero` section on [ [1]: #adding-a-logo-to-veleroio [2]: https://velero.io -[3]: https://github.com/vmware-tanzu/velero/pulls -[4]: https://github.com/vmware-tanzu/velero/pull/2242 +[3]: https://github.com/velero-io/velero/pulls +[4]: https://github.com/velero-io/velero/pull/2242 [10]: https://www.nirmata.com/2019/08/14/kubernetes-disaster-recovery-using-velero-and-nirmata/ [11]: https://nirmata.com diff --git a/CHANGELOG.md b/CHANGELOG.md index cc3e910d0..c29f81481 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -28,29 +28,29 @@ * [CHANGELOG-0.3.md][1] -[25]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.15.md -[24]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.14.md -[23]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.13.md -[22]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.12.md -[21]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.11.md -[20]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.10.md -[19]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.9.md -[18]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.8.md -[17]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.7.md -[16]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.6.md -[15]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.5.md -[14]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.4.md -[13]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.3.md -[12]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.2.md -[11]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.1.md -[10]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.0.md -[9]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.11.md -[8]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.10.md -[7]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.9.md -[6]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.8.md -[5]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.7.md -[4]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.6.md -[3]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.5.md -[2]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.4.md -[1]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.3.md -[0]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/unreleased +[25]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.15.md +[24]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.14.md +[23]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.13.md +[22]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.12.md +[21]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.11.md +[20]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.10.md +[19]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.9.md +[18]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.8.md +[17]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.7.md +[16]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.6.md +[15]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.5.md +[14]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.4.md +[13]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.3.md +[12]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.2.md +[11]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.1.md +[10]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.0.md +[9]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.11.md +[8]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.10.md +[7]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.9.md +[6]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.8.md +[5]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.7.md +[4]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.6.md +[3]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.5.md +[2]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.4.md +[1]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.3.md +[0]: https://github.com/velero-io/velero/blob/main/changelogs/unreleased diff --git a/Dockerfile b/Dockerfile index 12306fad2..3c6b8d460 100644 --- a/Dockerfile +++ b/Dockerfile @@ -34,9 +34,9 @@ ENV CGO_ENABLED=0 \ GOARM=${TARGETVARIANT} \ LDFLAGS="-X ${PKG}/pkg/buildinfo.Version=${VERSION} -X ${PKG}/pkg/buildinfo.GitSHA=${GIT_SHA} -X ${PKG}/pkg/buildinfo.GitTreeState=${GIT_TREE_STATE} -X ${PKG}/pkg/buildinfo.ImageRegistry=${REGISTRY}" -WORKDIR /go/src/github.com/vmware-tanzu/velero +WORKDIR /go/src/github.com/velero-io/velero -COPY . /go/src/github.com/vmware-tanzu/velero +COPY . /go/src/github.com/velero-io/velero RUN mkdir -p /output/usr/bin && \ export GOARM=$( echo "${GOARM}" | cut -c2-) && \ diff --git a/Dockerfile-Windows b/Dockerfile-Windows index df588def5..26774b375 100644 --- a/Dockerfile-Windows +++ b/Dockerfile-Windows @@ -36,9 +36,9 @@ ENV CGO_ENABLED=0 \ GOARM=${TARGETVARIANT} \ LDFLAGS="-X ${PKG}/pkg/buildinfo.Version=${VERSION} -X ${PKG}/pkg/buildinfo.GitSHA=${GIT_SHA} -X ${PKG}/pkg/buildinfo.GitTreeState=${GIT_TREE_STATE} -X ${PKG}/pkg/buildinfo.ImageRegistry=${REGISTRY}" -WORKDIR /go/src/github.com/vmware-tanzu/velero +WORKDIR /go/src/github.com/velero-io/velero -COPY . /go/src/github.com/vmware-tanzu/velero +COPY . /go/src/github.com/velero-io/velero RUN mkdir -p /output/usr/bin && \ export GOARM=$( echo "${GOARM}" | cut -c2-) && \ diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 687baeb00..0bf265329 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -10,14 +10,14 @@ This document defines the project governance for Velero. The following code repositories are governed by Velero community and maintained under the `vmware-tanzu\Velero` organization. -* **[Velero](https://github.com/vmware-tanzu/velero):** Main Velero codebase +* **[Velero](https://github.com/velero-io/velero):** Main Velero codebase * **[Helm Chart](https://github.com/vmware-tanzu/helm-charts/tree/main/charts/velero):** The Helm chart for the Velero server component -* **[Velero CSI Plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi):** This repository contains Velero plugins for snapshotting CSI backed PVCs using the CSI beta snapshot APIs -* **[Velero Plugin for vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere):** This repository contains the Velero Plugin for vSphere. This plugin is a volume snapshotter plugin that provides crash-consistent snapshots of vSphere block volumes and backup of volume data into S3 compatible storage. -* **[Velero Plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws):** This repository contains the plugins to support running Velero on AWS, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp):** This repository contains the plugins to support running Velero on GCP, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin for Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure):** This repository contains the plugins to support running Velero on Azure, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin Example](https://github.com/vmware-tanzu/velero-plugin-example):** This repository contains example plugins for Velero +* **[Velero CSI Plugin](https://github.com/velero-io/velero-plugin-for-csi):** This repository contains Velero plugins for snapshotting CSI backed PVCs using the CSI beta snapshot APIs +* **[Velero Plugin for vSphere](https://github.com/velero-io/velero-plugin-for-vsphere):** This repository contains the Velero Plugin for vSphere. This plugin is a volume snapshotter plugin that provides crash-consistent snapshots of vSphere block volumes and backup of volume data into S3 compatible storage. +* **[Velero Plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws):** This repository contains the plugins to support running Velero on AWS, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp):** This repository contains the plugins to support running Velero on GCP, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin for Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure):** This repository contains the plugins to support running Velero on Azure, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin Example](https://github.com/velero-io/velero-plugin-example):** This repository contains example plugins for Velero ## Community Roles @@ -67,12 +67,12 @@ interested in implementing the proposal should be either deeply engaged in the proposal process or be an author of the proposal. The proposal should be documented as a separated markdown file pushed to the root of the -`design` folder in the [Velero](https://github.com/vmware-tanzu/velero/tree/main/design) +`design` folder in the [Velero](https://github.com/velero-io/velero/tree/main/design) repository via PR. The name of the file should follow the name pattern `_design.md`, e.g: `restore-hooks-design.md`. -Use the [Proposal Template](https://github.com/vmware-tanzu/velero/blob/main/design/_template.md) as a starting point. +Use the [Proposal Template](https://github.com/velero-io/velero/blob/main/design/_template.md) as a starting point. ### Proposal Lifecycle @@ -88,7 +88,7 @@ To maintain velocity in a project as busy as Velero, the concept of [Lazy Consensus](http://en.osswiki.info/concepts/lazy_consensus) is practiced. Ideas and / or proposals should be shared by maintainers via GitHub with the appropriate maintainer groups (e.g., -`@vmware-tanzu/velero-maintainers`) tagged. Out of respect for other contributors, +`@velero-io/velero-maintainers`) tagged. Out of respect for other contributors, major changes should also be accompanied by a ping on Slack or a note on the Velero mailing list as appropriate. Author(s) of proposal, Pull Requests, issues, etc. will give a time period of no less than five (5) working days for @@ -111,7 +111,7 @@ Lazy consensus does _not_ apply to the process of: ### Deprecation Process -Any contributor may introduce a request to deprecate a feature or an option of a feature by opening a feature request issue in the vmware-tanzu/velero GitHub project. The issue should describe why the feature is no longer needed or has become detrimental to Velero, as well as whether and how it has been superseded. The submitter should give as much detail as possible. +Any contributor may introduce a request to deprecate a feature or an option of a feature by opening a feature request issue in the velero-io/velero GitHub project. The issue should describe why the feature is no longer needed or has become detrimental to Velero, as well as whether and how it has been superseded. The submitter should give as much detail as possible. Once the issue is filed, a one-month discussion period begins. Discussions take place within the issue itself as well as in the community meetings. The person who opens the issue, or a maintainer, should add the date and time marking the end of the discussion period in a comment on the issue as soon as possible after it is opened. A decision on the issue needs to be made within this one-month period. diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 2789a573d..b3c157989 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,6 +1,6 @@ # Velero Maintainers -[GOVERNANCE.md](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities. +[GOVERNANCE.md](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities. ## Maintainers diff --git a/Makefile b/Makefile index 80db72e3a..cf0276f9b 100644 --- a/Makefile +++ b/Makefile @@ -18,7 +18,7 @@ BIN ?= velero # This repo's root import path (under GOPATH). -PKG := github.com/vmware-tanzu/velero +PKG := github.com/velero-io/velero # Where to push the docker image. REGISTRY ?= velero @@ -194,7 +194,7 @@ TTY := $(shell tty -s && echo "-t") # Example: make shell CMD="date > datefile" shell: build-dirs build-env - @# bind-mount the Velero root dir in at /github.com/vmware-tanzu/velero + @# bind-mount the Velero root dir in at /github.com/velero-io/velero @# because the Kubernetes code-generator tools require the project to @# exist in a directory hierarchy ending like this (but *NOT* necessarily @# under $GOPATH). @@ -204,7 +204,7 @@ shell: build-dirs build-env -i $(TTY) \ --rm \ -u $$(id -u):$$(id -g) \ - -v "$$(pwd):/github.com/vmware-tanzu/velero:delegated" \ + -v "$$(pwd):/github.com/velero-io/velero:delegated" \ -v "$$(pwd)/_output/bin:/output:delegated" \ -v "$$(pwd)/.go/pkg:/go/pkg:delegated" \ -v "$$(pwd)/.go/std:/go/std:delegated" \ @@ -212,7 +212,7 @@ shell: build-dirs build-env -v "$$(pwd)/.go/go-build:/.cache/go-build:delegated" \ -v "$$(pwd)/.go/golangci-lint:/.cache/golangci-lint:delegated" \ -v "$$(pwd)/.go/goimports:/.cache/goimports:delegated" \ - -w /github.com/vmware-tanzu/velero \ + -w /github.com/velero-io/velero \ $(BUILDER_IMAGE) \ /bin/sh $(CMD) @@ -432,7 +432,7 @@ changelog: # PUBLISH=false \ # make release # -# To run the release, which will publish a *DRAFT* GitHub release in github.com/vmware-tanzu/velero +# To run the release, which will publish a *DRAFT* GitHub release in github.com/velero-io/velero # (you still need to review/publish the GitHub release manually): # GITHUB_TOKEN=your-github-token \ # RELEASE_NOTES_FILE=changelogs/CHANGELOG-1.2.md \ diff --git a/ROADMAP.md b/ROADMAP.md index 798acf588..a9b7037fe 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1 +1 @@ -# Please go to the [Velero Wiki](https://github.com/vmware-tanzu/velero/wiki/) to see our latest roadmap, archived roadmaps and roadmap guidance. \ No newline at end of file +# Please go to the [Velero Wiki](https://github.com/velero-io/velero/wiki/) to see our latest roadmap, archived roadmaps and roadmap guidance. \ No newline at end of file diff --git a/SECURITY.md b/SECURITY.md index 84e6f45dc..219426f6f 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -5,7 +5,7 @@ Velero is an open source tool with a growing community devoted to safe backup an ## Supported Versions -The Velero project maintains the following [governance document](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md), [release document](https://github.com/vmware-tanzu/velero/blob/f42c63af1b9af445e38f78a7256b1c48ef79c10e/site/docs/main/release-instructions.md), and [support document](https://velero.io/docs/main/support-process/). Please refer to these for release and related details. Only the most recent version of Velero is supported. Each [release](https://github.com/vmware-tanzu/velero/releases) includes information about upgrading to the latest version. +The Velero project maintains the following [governance document](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md), [release document](https://github.com/velero-io/velero/blob/f42c63af1b9af445e38f78a7256b1c48ef79c10e/site/docs/main/release-instructions.md), and [support document](https://velero.io/docs/main/support-process/). Please refer to these for release and related details. Only the most recent version of Velero is supported. Each [release](https://github.com/velero-io/velero/releases) includes information about upgrading to the latest version. ## Reporting a Vulnerability - Private Disclosure Process @@ -18,7 +18,7 @@ If you know of a publicly disclosed security vulnerability for Velero, please ** **IMPORTANT: Do not file public issues on GitHub for security vulnerabilities** -To report a vulnerability or a security-related issue, please contact the email address with the details of the vulnerability. The email will be fielded by the Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/vmware-tanzu/velero/issues/new/choose) instead. +To report a vulnerability or a security-related issue, please contact the email address with the details of the vulnerability. The email will be fielded by the Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/velero-io/velero/issues/new/choose) instead. ## Proposed Email Content @@ -68,7 +68,7 @@ The Security Team will respond to vulnerability reports as follows: ## Public Disclosure Process -The Security Team publishes a [public advisory](https://github.com/vmware-tanzu/velero/security/advisories) to the Velero community via GitHub. In most cases, additional communication via Slack, Twitter, mailing lists, blog and other channels will assist in educating Velero users and rolling out the patched release to affected users. +The Security Team publishes a [public advisory](https://github.com/velero-io/velero/security/advisories) to the Velero community via GitHub. In most cases, additional communication via Slack, Twitter, mailing lists, blog and other channels will assist in educating Velero users and rolling out the patched release to affected users. The Security Team will also publish any mitigating steps users can take until the fix can be applied to their Velero instances. Velero distributors will handle creating and publishing their own security advisories. diff --git a/changelogs/CHANGELOG-0.10.md b/changelogs/CHANGELOG-0.10.md index e4f451d9d..699d1dd9c 100644 --- a/changelogs/CHANGELOG-0.10.md +++ b/changelogs/CHANGELOG-0.10.md @@ -69,8 +69,8 @@ carefully to ensure a successful upgrade!** - The `Config` CRD has been replaced by `BackupStorageLocation` and `VolumeSnapshotLocation` CRDs. - The interface for external plugins (object/block stores, backup/restore item actions) has changed. If you have authored any custom plugins, they'll need to be updated for v0.10. - - The [`ObjectStore.ListCommonPrefixes`](https://github.com/vmware-tanzu/velero/blob/main/pkg/cloudprovider/object_store.go#L50) signature has changed to add a `prefix` parameter. - - Registering plugins has changed. Create a new plugin server with the `NewServer` function, and register plugins with the appropriate functions. See the [`Server`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/server.go#L37) interface for details. + - The [`ObjectStore.ListCommonPrefixes`](https://github.com/velero-io/velero/blob/main/pkg/cloudprovider/object_store.go#L50) signature has changed to add a `prefix` parameter. + - Registering plugins has changed. Create a new plugin server with the `NewServer` function, and register plugins with the appropriate functions. See the [`Server`](https://github.com/velero-io/velero/blob/main/pkg/plugin/server.go#L37) interface for details. - The organization of Ark data in object storage has changed. Existing data will need to be moved around to conform to the new layout. ### All Changes diff --git a/changelogs/CHANGELOG-0.9.md b/changelogs/CHANGELOG-0.9.md index f29a0d28e..5e243128b 100644 --- a/changelogs/CHANGELOG-0.9.md +++ b/changelogs/CHANGELOG-0.9.md @@ -137,7 +137,7 @@ ### Highlights: * Ark now has support for backing up and restoring Kubernetes volumes using a free open-source backup tool called [restic](https://github.com/restic/restic). This provides users an out-of-the-box solution for backing up and restoring almost any type of Kubernetes volume, whether or not it has snapshot support - integrated with Ark. For more information, see the [documentation](https://github.com/vmware-tanzu/velero/blob/main/docs/restic.md). + integrated with Ark. For more information, see the [documentation](https://github.com/velero-io/velero/blob/main/docs/restic.md). * Support for Prometheus metrics has been added! View total number of backup attempts (including success or failure), total backup size in bytes, and backup durations. More metrics coming in future releases! diff --git a/changelogs/CHANGELOG-1.10.md b/changelogs/CHANGELOG-1.10.md index 412b23b07..aba7d8419 100644 --- a/changelogs/CHANGELOG-1.10.md +++ b/changelogs/CHANGELOG-1.10.md @@ -2,7 +2,7 @@ ### 2022-11-23 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.10.0 +https://github.com/velero-io/velero/releases/tag/v1.10.0 ### Container Image `velero/velero:v1.10.0` @@ -20,7 +20,7 @@ In this release, we introduced the Unified Repository architecture to build a da In this release, we also deeply integrate Velero with Kopia, specifically, Kopia's uploader modules are isolated as a generic file system uploader; Kopia's repository modules are encapsulated as the unified backup repository. -For more information, refer to the [design document](https://github.com/vmware-tanzu/velero/blob/v1.10.0/design/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md). +For more information, refer to the [design document](https://github.com/velero-io/velero/blob/v1.10.0/design/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md). #### File system backup refactor Velero's file system backup (a.k.s. pod volume backup or formerly restic backup) is refactored as the first user of the Unified Repository architecture. Specifically, we added a new path, the Kopia path, besides the existing Restic path. While Restic path is still available and set as default, you can opt in Kopia path by specifying the `uploader-type` parameter at installation time. Meanwhile, you are free to restore from existing backups under either path, Velero dynamically switches to the correct path to process the restore. @@ -33,7 +33,7 @@ Meanwhile, we've created a performance guide for both Restic path and Kopia path #### Plugin versioning V1 refactor In this release, Velero moves plugins BackupItemAction, RestoreItemAction and VolumeSnapshotterAction to version v1, this allows future plugin changes that do not support backward compatibility, so is a preparation for various complex tasks, for example, data movement tasks. -For more information, refer to the [plugin versioning design document](https://github.com/vmware-tanzu/velero/blob/v1.10.0/design/plugin-versioning.md). +For more information, refer to the [plugin versioning design document](https://github.com/velero-io/velero/blob/v1.10.0/design/plugin-versioning.md). #### Refactor the controllers using Kubebuilder v3 In this release we continued our code modernization work, rewriting some controllers using Kubebuilder v3. This work is ongoing and we will continue to make progress in future releases. @@ -75,9 +75,9 @@ Due to file system backup refactor, below modules and parameters name have been Due to the major changes of file system backup, the old upgrade steps are not suitable any more. For the new upgrade steps, visit [v1.10 upgrade guide document](https://velero.io/docs/v1.10/upgrade-to-1.10/). #### Limitations/Known issues -In this release, Kopia backup repository (so the Kopia path of file system backup) doesn't support self signed certificate for S3 compatible storage. To track this problem, refer to this [Velero issue](https://github.com/vmware-tanzu/velero/issues/5123) or [Kopia issue](https://github.com/kopia/kopia/issues/1443). +In this release, Kopia backup repository (so the Kopia path of file system backup) doesn't support self signed certificate for S3 compatible storage. To track this problem, refer to this [Velero issue](https://github.com/velero-io/velero/issues/5123) or [Kopia issue](https://github.com/kopia/kopia/issues/1443). -Due to the code change in Velero, there will be some code change required in vSphere plugin, without which the functionality may be impacted. Therefore, if you are using vSphere plugin in your workflow, please hold the upgrade until the issue [#485](https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/485) is fixed in vSphere plugin. +Due to the code change in Velero, there will be some code change required in vSphere plugin, without which the functionality may be impacted. Therefore, if you are using vSphere plugin in your workflow, please hold the upgrade until the issue [#485](https://github.com/velero-io/velero-plugin-for-vsphere/issues/485) is fixed in vSphere plugin. ### All changes @@ -185,6 +185,6 @@ Related issue: #2413 (#5178, @allenxu404) * Delete opened issues triage action. (#5041, @jxun) * When spec.RestoreStatus is empty, don't restore status (#5008, @sseago) * Added DownloadTargetKindCSIBackupVolumeSnapshots for retrieving the signed URL to download only the ``-csi-volumesnapshots.json.gz and DownloadTargetKindCSIBackupVolumeSnapshotContents to download only ``-csi-volumesnapshotcontents.json.gz in the DownloadRequest CR structure. These files are already present in the backup layout. (#4980, @anshulahuja98) - * Refactor BackupItemAction proto and related code to backupitemaction/v1 package. This is part of implementation of the plugin version design https://github.com/vmware-tanzu/velero/blob/main/design/plugin-versioning.md (#4943, @phuongatemc) + * Refactor BackupItemAction proto and related code to backupitemaction/v1 package. This is part of implementation of the plugin version design https://github.com/velero-io/velero/blob/main/design/plugin-versioning.md (#4943, @phuongatemc) * Unified Repository Design (#4926, @Lyndon-Li) * Add credentials to volume snapshot locations (#4864, @sseago) \ No newline at end of file diff --git a/changelogs/CHANGELOG-1.11.md b/changelogs/CHANGELOG-1.11.md index 75d08d4df..0eef338eb 100644 --- a/changelogs/CHANGELOG-1.11.md +++ b/changelogs/CHANGELOG-1.11.md @@ -2,7 +2,7 @@ ### 2023-04-07 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.11.0 +https://github.com/velero-io/velero/releases/tag/v1.11.0 ### Container Image `velero/velero:v1.11.0` @@ -26,10 +26,10 @@ This feature implemented the RestoreItemAction v2. RIA v2 has three new methods: 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. #### 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 [policy API design](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md#api-design)Β 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. +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 [policy API design](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md#api-design)Β 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. #### Resource Filters that can distinguish cluster scope and namespace scope resources This feature adds four new resource filters for backup. The new filters are separated into cluster scope and namespace scope. Before this feature, Velero could not filter cluster scope resources precisely. This feature provides the ability and refactors existing resource filter parameters. diff --git a/changelogs/CHANGELOG-1.12.md b/changelogs/CHANGELOG-1.12.md index 4b980641a..f65d5b663 100644 --- a/changelogs/CHANGELOG-1.12.md +++ b/changelogs/CHANGELOG-1.12.md @@ -2,7 +2,7 @@ ### 2023-08-18 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0 +https://github.com/velero-io/velero/releases/tag/v1.12.0 ### Container Image `velero/velero:v1.12.0` @@ -23,17 +23,17 @@ CSI Snapshot Data Movement is useful in below scenarios: * For on-premises users, the storage usually doesn't support durable snapshots, so it is impossible/less efficient/cost ineffective to keep volume snapshots by the storage This feature helps to move the snapshot data to a storage with lower cost and larger scale for long time preservation. * For public cloud users, this feature helps users to fulfill the multiple cloud strategy. It allows users to back up volume snapshots from one cloud provider and preserve or restore the data to another cloud provider. Then users will be free to flow their business data across cloud providers based on Velero backup and restore -CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design ([Volume Snapshot Data Movement](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md)). More details can be found in the design. +CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design ([Volume Snapshot Data Movement](https://github.com/velero-io/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md)). More details can be found in the design. #### Resource Modifiers In many use cases, customers often need to substitute specific values in Kubernetes resources during the restoration process like changing the namespace, changing the storage class, etc. -To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design ([Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/json-substitution-action-design.md)). +To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design ([Resource Modifiers](https://github.com/velero-io/velero/blob/main/design/Implemented/json-substitution-action-design.md)). #### Multiple VolumeSnapshotClasses Prior to version 1.12, the Velero CSI plugin would choose the VolumeSnapshotClass in the cluster based on matching driver names and the presence of the "velero.io/csi-volumesnapshot-class" label. However, this approach proved inadequate for many user scenarios. -With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design ([Multiple VolumeSnapshotClasses](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/multiple-csi-volumesnapshotclass-support.md)). +With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design ([Multiple VolumeSnapshotClasses](https://github.com/velero-io/velero/blob/main/design/Implemented/multiple-csi-volumesnapshotclass-support.md)). #### Restore Finalizer Before v1.12, the restore controller would only delete restore resources but wouldn’t delete restore data from the backup storage location when the command `velero restore delete` was executed. The only chance Velero deletes restores data from the backup storage location is when the associated backup is deleted. diff --git a/changelogs/CHANGELOG-1.13.md b/changelogs/CHANGELOG-1.13.md index ec7362bbe..26132ec64 100644 --- a/changelogs/CHANGELOG-1.13.md +++ b/changelogs/CHANGELOG-1.13.md @@ -2,7 +2,7 @@ ### 2024-01-10 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.13.0 +https://github.com/velero-io/velero/releases/tag/v1.13.0 ### Container Image `velero/velero:v1.13.0` @@ -16,7 +16,7 @@ https://velero.io/docs/v1.13/upgrade-to-1.13/ ### Highlights #### Resource Modifier Enhancement -Velero introduced the Resource Modifiers in v1.12.0. This feature allows users to specify a ConfigMap with a set of rules to modify the resources during restoration. However, only the JSON Patch is supported when creating the rules, and JSON Patch has some limitations, which cannot cover all use cases. In v1.13.0, Velero adds new support for JSON Merge Patch and Strategic Merge Patch, which provide more power and flexibility and allow users to use the same ConfigMap to apply patches on the resources. More design details can be found in [Support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md) design. For instructions on how to use the feature, please refer to the [Resource Modifiers](https://velero.io/docs/v1.13/restore-resource-modifiers/) doc. +Velero introduced the Resource Modifiers in v1.12.0. This feature allows users to specify a ConfigMap with a set of rules to modify the resources during restoration. However, only the JSON Patch is supported when creating the rules, and JSON Patch has some limitations, which cannot cover all use cases. In v1.13.0, Velero adds new support for JSON Merge Patch and Strategic Merge Patch, which provide more power and flexibility and allow users to use the same ConfigMap to apply patches on the resources. More design details can be found in [Support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers](https://github.com/velero-io/velero/blob/main/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md) design. For instructions on how to use the feature, please refer to the [Resource Modifiers](https://velero.io/docs/v1.13/restore-resource-modifiers/) doc. #### Node-Agent Concurrency Velero data movement activities from fs-backups and CSI snapshot data movements run in Velero node-agent, so may be hosted by every node in the cluster and consume resources (i.e. CPU, memory, network bandwidth) from there. With v1.13, users are allowed to configure how many data movement activities (a.k.a, loads) run in each node globally or by node, so that users can better leverage the performance of Velero data movement activities and the resource consumption in the cluster. For more information, check the [Node-Agent Concurrency](https://velero.io/docs/v1.13/node-agent-concurrency/) document. @@ -57,8 +57,8 @@ To fix CVEs and keep pace with Golang, Velero made changes as follows: ### Breaking changes * Backup describe command: due to the backup describe output enhancement, some existing information (i.e. the output for native snapshot, CSI snapshot, and fs-backup) has been moved to the Backup Volumes section with some format changes. -* API type changes: changes the field [DataMoverConfig](https://github.com/vmware-tanzu/velero/blob/v1.13.0/pkg/apis/velero/v2alpha1/data_upload_types.go#L54) in DataUploadSpec from `*map[string][string]`` to `map[string]string` -* Velero install command: due to the issue [#7264](https://github.com/vmware-tanzu/velero/issues/7264), v1.13.0 introduces a break change that make the informer cache enabled by default to keep the actual behavior consistent with the helper message(the informer cache is disabled by default before the change). +* API type changes: changes the field [DataMoverConfig](https://github.com/velero-io/velero/blob/v1.13.0/pkg/apis/velero/v2alpha1/data_upload_types.go#L54) in DataUploadSpec from `*map[string][string]`` to `map[string]string` +* Velero install command: due to the issue [#7264](https://github.com/velero-io/velero/issues/7264), v1.13.0 introduces a break change that make the informer cache enabled by default to keep the actual behavior consistent with the helper message(the informer cache is disabled by default before the change). ### Limitations/Known issues diff --git a/changelogs/CHANGELOG-1.14.md b/changelogs/CHANGELOG-1.14.md index 209334fc2..86a62b6b7 100644 --- a/changelogs/CHANGELOG-1.14.md +++ b/changelogs/CHANGELOG-1.14.md @@ -1,7 +1,7 @@ ## v1.14 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.14.0 +https://github.com/velero-io/velero/releases/tag/v1.14.0 ### Container Image `velero/velero:v1.14.0` diff --git a/changelogs/CHANGELOG-1.15.md b/changelogs/CHANGELOG-1.15.md index e52d6f7f4..883921563 100644 --- a/changelogs/CHANGELOG-1.15.md +++ b/changelogs/CHANGELOG-1.15.md @@ -1,7 +1,7 @@ ## v1.15 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.15.0 +https://github.com/velero-io/velero/releases/tag/v1.15.0 ### Container Image `velero/velero:v1.15.0` @@ -19,13 +19,13 @@ Data transfer activities for CSI Snapshot Data Movement are moved from node-agen - This enables users to to control resource (i.e., cpu, memory) allocations in a granular manner, e.g., control them per backup/restore of a volume. - This enhances the resilience, crash of one data movement activity won't affect others. - This prevents unnecessary full backup because of host path changes after workload pods restart. -- For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md. +- For more information, check the design https://github.com/velero-io/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md. #### Item Block concepts and ItemBlockAction (IBA) plugin Item Block concepts are introduced for resource backups to help to achieve multiple thread backups. Specifically, correlated resources are categorized in the same item block and item blocks could be processed concurrently in multiple threads. ItemBlockAction plugin is introduced to help Velero to categorize resources into item blocks. At present, Velero provides built-in IBAs for pods and PVCs and Velero also supports customized IBAs for any resources. In v1.15, Velero doesn't support multiple thread process of item blocks though item block concepts and IBA plugins are fully supported. The multiple thread support will be delivered in future releases. -For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/backup-performance-improvements.md. +For more information, check the design https://github.com/velero-io/velero/blob/main/design/backup-performance-improvements.md. #### Node selection for repository maintenance job Repository maintenance are resource consuming tasks, Velero now allows you to configure the nodes to run repository maintenance jobs, so that you can run repository maintenance jobs in idle nodes or avoid them to run in nodes hosting critical workloads. @@ -50,9 +50,9 @@ For more information, check the document https://velero.io/docs/v1.15/backup-rep #### Performance improvements In 1.15, several performance related issues/enhancements are included, which makes significant performance improvements in specific scenarios: -- There was a memory leak of Velero server after plugin calls, now it is fixed, see issue https://github.com/vmware-tanzu/velero/issues/7925 -- The `client-burst/client-qps` parameters are automatically inherited to plugins, so that you can use the same velero server parameters to accelerate the plugin executions when large number of API server calls happen, see issue https://github.com/vmware-tanzu/velero/issues/7806 -- Maintenance of Kopia repository takes huge memory in scenarios that huge number of files have been backed up, Velero 1.15 has included the Kopia upstream enhancement to fix the problem, see issue https://github.com/vmware-tanzu/velero/issues/7510 +- There was a memory leak of Velero server after plugin calls, now it is fixed, see issue https://github.com/velero-io/velero/issues/7925 +- The `client-burst/client-qps` parameters are automatically inherited to plugins, so that you can use the same velero server parameters to accelerate the plugin executions when large number of API server calls happen, see issue https://github.com/velero-io/velero/issues/7806 +- Maintenance of Kopia repository takes huge memory in scenarios that huge number of files have been backed up, Velero 1.15 has included the Kopia upstream enhancement to fix the problem, see issue https://github.com/velero-io/velero/issues/7510 ### Runtime and dependencies Golang runtime: v1.22.8 @@ -65,7 +65,7 @@ Therefore, a user option is added in the same backup PVC configuration configMap ### Breaking changes #### Deprecation of Restic -Restic path for fs-backup is in deprecation process starting from 1.15. According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy), for 1.15, if Restic path is used the backup/restore of fs-backup still creates and succeeds, but you will see warnings in below scenarios: +Restic path for fs-backup is in deprecation process starting from 1.15. According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy), for 1.15, if Restic path is used the backup/restore of fs-backup still creates and succeeds, but you will see warnings in below scenarios: - When `--uploader-type=restic` is used in Velero installation - When Restic path is used to create backup/restore of fs-backup @@ -83,7 +83,7 @@ In 1.15, below Velero server parameters for repository maintenance jobs are move ``` #### Changing PVC selected-node feature is deprecated -In 1.15, the [Changing PVC selected-node feature](https://velero.io/docs/v1.15/restore-reference/#changing-pvc-selected-node) enters deprecation process and will be removed in future releases according to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy). Usage of this feature for any purpose is not recommended. +In 1.15, the [Changing PVC selected-node feature](https://velero.io/docs/v1.15/restore-reference/#changing-pvc-selected-node) enters deprecation process and will be removed in future releases according to [Velero deprecation policy](https://github.com/velero-io/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy). Usage of this feature for any purpose is not recommended. ### All Changes * add no-relabeling option to backupPVC configmap (#8288, @sseago) diff --git a/changelogs/CHANGELOG-1.16.md b/changelogs/CHANGELOG-1.16.md index fa8793f16..b33ae4497 100644 --- a/changelogs/CHANGELOG-1.16.md +++ b/changelogs/CHANGELOG-1.16.md @@ -1,7 +1,7 @@ ## v1.16 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.16.0 +https://github.com/velero-io/velero/releases/tag/v1.16.0 ### Container Image `velero/velero:v1.16.0` @@ -15,28 +15,28 @@ https://velero.io/docs/v1.16/upgrade-to-1.16/ ### Highlights #### Windows cluster support In v1.16, Velero supports to run in Windows clusters and backup/restore Windows workloads, either stateful or stateless: - * Hybrid build and all-in-one image: the build process is enhanced to build an all-in-one image for hybrid CPU architecture and hybrid platform. For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/multiple-arch-build-with-windows.md + * Hybrid build and all-in-one image: the build process is enhanced to build an all-in-one image for hybrid CPU architecture and hybrid platform. For more information, check the design https://github.com/velero-io/velero/blob/main/design/multiple-arch-build-with-windows.md * Deployment in Windows clusters: Velero node-agent, data mover pods and maintenance jobs now support to run in both linux and Windows nodes * Data mover backup/restore Windows workloads: Velero built-in data mover supports Windows workloads throughout its full cycle, i.e., discovery, backup, restore, pre/post hook, etc. It automatically identifies Windows workloads and schedules data mover pods to the right group of nodes -Check the epic issue https://github.com/vmware-tanzu/velero/issues/8289 for more information. +Check the epic issue https://github.com/velero-io/velero/issues/8289 for more information. #### Parallel Item Block backup v1.16 now supports to back up item blocks in parallel. Specifically, during backup, correlated resources are grouped in item blocks and Velero backup engine creates a thread pool to back up the item blocks in parallel. This significantly improves the backup throughput, especially when there are large scale of resources. Pre/post hooks also belongs to item blocks, so will also run in parallel along with the item blocks. Users are allowed to configure the parallelism through the `--item-block-worker-count` Velero server parameter. If not configured, the default parallelism is 1. -For more information, check issue https://github.com/vmware-tanzu/velero/issues/8334. +For more information, check issue https://github.com/velero-io/velero/issues/8334. #### Data mover restore enhancement in scalability -In previous releases, for each volume of WaitForFirstConsumer mode, data mover restore is only allowed to happen in the node that the volume is attached. This severely degrades the parallelism and the balance of node resource(CPU, memory, network bandwidth) consumption for data mover restore (https://github.com/vmware-tanzu/velero/issues/8044). +In previous releases, for each volume of WaitForFirstConsumer mode, data mover restore is only allowed to happen in the node that the volume is attached. This severely degrades the parallelism and the balance of node resource(CPU, memory, network bandwidth) consumption for data mover restore (https://github.com/velero-io/velero/issues/8044). -In v1.16, users are allowed to configure data mover restores running and spreading evenly across all nodes in the cluster. The configuration is done through a new flag `ignoreDelayBinding` in node-agent configuration (https://github.com/vmware-tanzu/velero/issues/8242). +In v1.16, users are allowed to configure data mover restores running and spreading evenly across all nodes in the cluster. The configuration is done through a new flag `ignoreDelayBinding` in node-agent configuration (https://github.com/velero-io/velero/issues/8242). #### Data mover enhancements in observability In 1.16, some observability enhancements are added: - * Output various statuses of intermediate objects for failures of data mover backup/restore (https://github.com/vmware-tanzu/velero/issues/8267) - * Output the errors when Velero fails to delete intermediate objects during clean up (https://github.com/vmware-tanzu/velero/issues/8125) + * Output various statuses of intermediate objects for failures of data mover backup/restore (https://github.com/velero-io/velero/issues/8267) + * Output the errors when Velero fails to delete intermediate objects during clean up (https://github.com/velero-io/velero/issues/8125) The outputs are in the same node-agent log and enabled automatically. @@ -45,24 +45,24 @@ In previous releases, a unnecessary VolumeSnapshotContent object is retained for In 1.16, the retained VolumeSnapshotContent is removed from the backup, so no unnecessary CSI objects are synced or restored. -For more information, check issue https://github.com/vmware-tanzu/velero/issues/8725. +For more information, check issue https://github.com/velero-io/velero/issues/8725. #### Backup Repository Maintenance enhancement in resiliency and observability In v1.16, some enhancements of backup repository maintenance are added to improve the observability and resiliency: - * A new backup repository maintenance history section, called `RecentMaintenance`, is added to the BackupRepository CR. Specifically, for each BackupRepository, including start/completion time, completion status and error message. (https://github.com/vmware-tanzu/velero/issues/7810) - * Running maintenance jobs are now recaptured after Velero server restarts. (https://github.com/vmware-tanzu/velero/issues/7753) - * The maintenance job will not be launched for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8238) - * The backup repository will not try to initialize a new repository for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8091) - * Users now are allowed to configure the intervals of an effective maintenance in the way of `normalGC`, `fastGC` and `eagerGC`, through the `fullMaintenanceInterval` parameter in backupRepository configuration. (https://github.com/vmware-tanzu/velero/issues/8364) + * A new backup repository maintenance history section, called `RecentMaintenance`, is added to the BackupRepository CR. Specifically, for each BackupRepository, including start/completion time, completion status and error message. (https://github.com/velero-io/velero/issues/7810) + * Running maintenance jobs are now recaptured after Velero server restarts. (https://github.com/velero-io/velero/issues/7753) + * The maintenance job will not be launched for readOnly BackupStorageLocation. (https://github.com/velero-io/velero/issues/8238) + * The backup repository will not try to initialize a new repository for readOnly BackupStorageLocation. (https://github.com/velero-io/velero/issues/8091) + * Users now are allowed to configure the intervals of an effective maintenance in the way of `normalGC`, `fastGC` and `eagerGC`, through the `fullMaintenanceInterval` parameter in backupRepository configuration. (https://github.com/velero-io/velero/issues/8364) #### Volume Policy enhancement of filtering volumes by PVC labels -In v1.16, Volume Policy is extended to support filtering volumes by PVC labels. (https://github.com/vmware-tanzu/velero/issues/8256). +In v1.16, Volume Policy is extended to support filtering volumes by PVC labels. (https://github.com/velero-io/velero/issues/8256). #### Resource Status restore per object -In v1.16, users are allowed to define whether to restore resource status per object through an annotation `velero.io/restore-status` set on the object. (https://github.com/vmware-tanzu/velero/issues/8204). +In v1.16, users are allowed to define whether to restore resource status per object through an annotation `velero.io/restore-status` set on the object. (https://github.com/velero-io/velero/issues/8204). #### Velero Restore Helper binary is merged into Velero image -In v1.16, Velero banaries, i.e., velero, velero-helper and velero-restore-helper, are all included into the single Velero image. (https://github.com/vmware-tanzu/velero/issues/8484). +In v1.16, Velero banaries, i.e., velero, velero-helper and velero-restore-helper, are all included into the single Velero image. (https://github.com/velero-io/velero/issues/8484). ### Runtime and dependencies Golang runtime: 1.23.7 diff --git a/changelogs/CHANGELOG-1.17.md b/changelogs/CHANGELOG-1.17.md index 54e1c22dc..85fa75557 100644 --- a/changelogs/CHANGELOG-1.17.md +++ b/changelogs/CHANGELOG-1.17.md @@ -1,7 +1,7 @@ ## v1.17 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.17.0 +https://github.com/velero-io/velero/releases/tag/v1.17.0 ### Container Image `velero/velero:v1.17.0` @@ -19,11 +19,11 @@ In v1.17, Velero fs-backup is modernized to the micro-service architecture, whic - fs-backup is more robust, the running backup/restore could survive from node-agent restart; and the resource allocation is in a more granular manner, the failure of one backup/restore won't impact others. - The resource usage of node-agent is steady, especially, the node-agent pods won't request huge memory and hold it for a long time. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. #### fs-backup support Windows cluster In v1.17, Velero fs-backup supports to backup/restore Windows workloads. By leveraging the new micro-service architecture for fs-backup, data mover pods could run in Windows nodes and backup/restore Windows volumes. Together with CSI snapshot data movement for Windows which is delivered in 1.16, Velero now supports Windows workload backup/restore in full scenarios. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. #### Volume group snapshot support In v1.17, Velero supports [volume group snapshots](https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/) which is a beta feature in Kubernetes upstream, for both CSI snapshot backup and CSI snapshot data movement. This allows a snapshot to be taken from multiple volumes at the same point-in-time to achieve write order consistency, which is helpful to achieve better data consistency when multiple volumes being backed up are correlated. @@ -31,20 +31,20 @@ Check the document https://velero.io/docs/main/volume-group-snapshots/ for more #### Priority class support In v1.17, [Kubernetes priority class](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) is supported for all modules across Velero. Specifically, users are allowed to configure priority class to Velero server, node-agent, data mover pods, backup repository maintenance jobs separately. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/priority-class-name-support_design.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/Implemented/priority-class-name-support_design.md for more details. #### Scalability and Resiliency improvements of data movers ##### Reduce excessive number of data mover pods in Pending state In v1.17, Velero allows users to set a `PrepareQueueLength` in the node-agent configuration, data mover pods and volumes out of this number won't be created until data path quota is available, so that excessive number cluster resources won't be taken unnecessarily, which is particularly helpful for large scale environments. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/node-agent-load-soothing.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/node-agent-load-soothing.md for more details. ##### Enhancement on node-agent restart handling for data movements In v1.17, data movements in all phases could survive from node-agent restart and resume themselves; when a data movement gets orphaned in special cases, e.g., cluster node absent, it could also be canceled appropriately after the restart. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement. -Check issue https://github.com/vmware-tanzu/velero/issues/8534 for more details. +Check issue https://github.com/velero-io/velero/issues/8534 for more details. ##### CSI snapshot data movement restore node-selection and node-selection by storage class In v1.17, CSI snapshot data movement restore acquires the same node-selection capability as backup, that is, users could specify which nodes can/cannot run data mover pods for both backup and restore now. And users are also allowed to configure the node-selection per storage class, which is particularly helpful to the environments where a storage class are not usable by all cluster nodes. -Check issue https://github.com/vmware-tanzu/velero/issues/8186 and https://github.com/vmware-tanzu/velero/issues/8223 for more details. +Check issue https://github.com/velero-io/velero/issues/8186 and https://github.com/velero-io/velero/issues/8223 for more details. #### Include/exclude policy support for resource policy In v1.17, Velero resource policy supports `includeExcludePolicy` besides the existing `volumePolicy`. This allows users to set include/exclude filters for resources in a resource policy configmap, so that these filters are reusable among multiple backups. @@ -58,7 +58,7 @@ kopia: 0.21.1 ### Breaking changes #### Deprecation of Restic -According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy), backup of fs-backup under Restic path is removed in v1.17, so `--uploader-type=restic` is not a valid installation configuration anymore. This means you cannot create a backup under Restic path, but you can still restore from the previous backups under Restic path until v1.19. +According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#deprecation-policy), backup of fs-backup under Restic path is removed in v1.17, so `--uploader-type=restic` is not a valid installation configuration anymore. This means you cannot create a backup under Restic path, but you can still restore from the previous backups under Restic path until v1.19. #### Repository maintenance job configurations are removed from Velero server parameter Since the repository maintenance job configurations are moved to repository maintenance job configMap, in v1.17 below Velero sever parameters are removed: diff --git a/changelogs/CHANGELOG-1.18.md b/changelogs/CHANGELOG-1.18.md index 66c486ddf..358bee22e 100644 --- a/changelogs/CHANGELOG-1.18.md +++ b/changelogs/CHANGELOG-1.18.md @@ -1,7 +1,7 @@ ## v1.18 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.18.0 +https://github.com/velero-io/velero/releases/tag/v1.18.0 ### Container Image `velero/velero:v1.18.0` @@ -16,7 +16,7 @@ https://velero.io/docs/v1.18/upgrade-to-1.18/ #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: @@ -24,7 +24,7 @@ In v1.18, Velero allows users to configure cache volumes for data mover pods dur - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache limit configuration, cache volume with appropriate size helps to improve the restore throughput -Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/backup-repo-cache-volume.md for more details. +Check design https://github.com/velero-io/velero/blob/main/design/Implemented/backup-repo-cache-volume.md for more details. #### Incremental size for data movers In v1.18, Velero allows users to observe the incremental size of data movers backups for CSI snapshot data movement and fs-backup, so that users could visually see the data reduction due to incremental backup. @@ -53,7 +53,7 @@ kopia: 0.22.3 ### Breaking changes #### Deprecation of PVC selected node feature -According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy), PVC selected node feature is deprecated in v1.18. Velero could appropriately handle PVC's selected-node annotation, so users don't need to do anything particularly. +According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#deprecation-policy), PVC selected node feature is deprecated in v1.18. Velero could appropriately handle PVC's selected-node annotation, so users don't need to do anything particularly. ### All Changes * Remove backup from running list when backup fails validation (#9498, @sseago) diff --git a/changelogs/CHANGELOG-1.2.md b/changelogs/CHANGELOG-1.2.md index e3fd61641..808111aa1 100644 --- a/changelogs/CHANGELOG-1.2.md +++ b/changelogs/CHANGELOG-1.2.md @@ -2,7 +2,7 @@ #### 2019-11-07 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 +https://github.com/velero-io/velero/releases/tag/v1.2.0 ### Container Image `velero/velero:v1.2.0` diff --git a/changelogs/CHANGELOG-1.3.md b/changelogs/CHANGELOG-1.3.md index 6dbfb57d8..6d1476431 100644 --- a/changelogs/CHANGELOG-1.3.md +++ b/changelogs/CHANGELOG-1.3.md @@ -2,7 +2,7 @@ ### 2020-04-03 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.3.2 +https://github.com/velero-io/velero/releases/tag/v1.3.2 ### Container Image `velero/velero:v1.3.2` @@ -21,7 +21,7 @@ https://velero.io/docs/v1.3.2/upgrade-to-1.3/ ### 2020-03-10 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.3.1 +https://github.com/velero-io/velero/releases/tag/v1.3.1 ### Container Image `velero/velero:v1.3.1` @@ -44,7 +44,7 @@ Fixed a bug that caused failures when backing up CustomResourceDefinitions with #### 2020-03-02 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0 +https://github.com/velero-io/velero/releases/tag/v1.3.0 ### Container Image `velero/velero:v1.3.0` @@ -83,10 +83,10 @@ 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)) ### All Changes diff --git a/changelogs/CHANGELOG-1.4.md b/changelogs/CHANGELOG-1.4.md index 354e68514..71d26a61d 100644 --- a/changelogs/CHANGELOG-1.4.md +++ b/changelogs/CHANGELOG-1.4.md @@ -2,7 +2,7 @@ ### 2020-07-13 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2 +https://github.com/velero-io/velero/releases/tag/v1.4.2 ### Container Image `velero/velero:v1.4.2` @@ -27,7 +27,7 @@ This tag was created in code, but has no associated docker image due to misconfi ### 2020-05-26 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0 +https://github.com/velero-io/velero/releases/tag/v1.4.0 ### Container Image `velero/velero:v1.4.0` diff --git a/changelogs/CHANGELOG-1.5.md b/changelogs/CHANGELOG-1.5.md index 7013a85e7..d71ba0bf7 100644 --- a/changelogs/CHANGELOG-1.5.md +++ b/changelogs/CHANGELOG-1.5.md @@ -2,7 +2,7 @@ ### 2020-09-16 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.5.1 +https://github.com/velero-io/velero/releases/tag/v1.5.1 ### Container Image `velero/velero:v1.5.1` @@ -57,7 +57,7 @@ Displays the Timestamps when issued a print or describe (#2748, @thejasbabu) * StorageGrid compatibility by removing explicit gzip accept header setting (#2712, @fvsqr) * restic: add support for setting SecurityContext (runAsUser, runAsGroup) for restore (#2621, @jaygridley) * Add backupValidationFailureTotal to metrics (#2714, @kathpeony) - * bump Kubernetes module dependencies to v0.18.4 to fix https://github.com/vmware-tanzu/velero/issues/2540 by adding code compatibility with kubernetes v1.18 (#2651, @laverya) + * bump Kubernetes module dependencies to v0.18.4 to fix https://github.com/velero-io/velero/issues/2540 by adding code compatibility with kubernetes v1.18 (#2651, @laverya) * Add a BSL controller to handle validation + update BSL status phase (validation removed from the server and no longer blocks when there's any invalid BSL) (#2674, @carlisia) * updated acceptable values on cron schedule from 0-7 to 0-6 (#2676, @dthrasher) * Improve velero download doc (#2660, @carlisia) diff --git a/changelogs/CHANGELOG-1.6.md b/changelogs/CHANGELOG-1.6.md index 73cae45f0..df1c24ab1 100644 --- a/changelogs/CHANGELOG-1.6.md +++ b/changelogs/CHANGELOG-1.6.md @@ -2,7 +2,7 @@ ### 2021-04-12 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.6.0 +https://github.com/velero-io/velero/releases/tag/v1.6.0 ### Container Image `velero/velero:v1.6.0` diff --git a/changelogs/CHANGELOG-1.7.md b/changelogs/CHANGELOG-1.7.md index fdff3c2b0..5f769019a 100644 --- a/changelogs/CHANGELOG-1.7.md +++ b/changelogs/CHANGELOG-1.7.md @@ -2,7 +2,7 @@ ### 2021-09-07 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.7.0 +https://github.com/velero-io/velero/releases/tag/v1.7.0 ### Container Image `velero/velero:v1.7.0` @@ -75,6 +75,6 @@ This command collects information about a Velero installation, such as pod logs * πŸ› Fix plugin name derivation from image name (#3711, @ashish-amarnath) * ✨ ⚠️ Remove CSI volumesnapshot artifact deletion -This change requires https://github.com/vmware-tanzu/velero-plugin-for-csi/pull/86 for Velero to continue +This change requires https://github.com/velero-io/velero-plugin-for-csi/pull/86 for Velero to continue deleting of CSI volumesnapshots when the corresponding backups are deleted. (#3734, @ashish-amarnath) * use unstructured to marshal selective fields for service restore action (#3789, @alaypatel07) diff --git a/changelogs/CHANGELOG-1.8.md b/changelogs/CHANGELOG-1.8.md index e317849d1..c45b56536 100644 --- a/changelogs/CHANGELOG-1.8.md +++ b/changelogs/CHANGELOG-1.8.md @@ -2,7 +2,7 @@ ### 2022-01-14 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.8.0 +https://github.com/velero-io/velero/releases/tag/v1.8.0 ### Container Image `velero/velero:v1.8.0` @@ -41,7 +41,7 @@ When a Backup Storage Location (BSL) is deleted, backup and Restic repository re #### Breaking changes -Starting in v1.8, Velero will only support Kubernetes v1 CRD meaning that Velero v1.8+ will only run on Kubernetes v1.16+. Before upgrading, make sure you are running a supported Kubernetes version. For more information, see our [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). +Starting in v1.8, Velero will only support Kubernetes v1 CRD meaning that Velero v1.8+ will only run on Kubernetes v1.16+. Before upgrading, make sure you are running a supported Kubernetes version. For more information, see our [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). #### Upload Progress Monitoring and Item Snapshotter Item Snapshotter plugin API was merged. This will support both Upload Progress diff --git a/changelogs/CHANGELOG-1.9.md b/changelogs/CHANGELOG-1.9.md index 9f887aaf5..7472288a5 100644 --- a/changelogs/CHANGELOG-1.9.md +++ b/changelogs/CHANGELOG-1.9.md @@ -2,7 +2,7 @@ ### 2022-06-13 ### Download -https://github.com/vmware-tanzu/velero/releases/tag/v1.9.0 +https://github.com/velero-io/velero/releases/tag/v1.9.0 ### Container Image `velero/velero:v1.9.0` @@ -20,7 +20,7 @@ https://velero.io/docs/v1.9/upgrade-to-1.9/ - No VolumeSnapshot will be left in the source namespace of the workload - Report metrics for CSI snapshots -More improvements please refer to [CSI plugin improvement](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+label%3A%22CSI+plugin+-+GA+-+phase1%22+is%3Aclosed) +More improvements please refer to [CSI plugin improvement](https://github.com/velero-io/velero/issues?q=is%3Aissue+label%3A%22CSI+plugin+-+GA+-+phase1%22+is%3Aclosed) With these improvements we'll provide official support for CSI snapshots on AKS/EKS clusters. (with CSI plugin v0.3.0) diff --git a/cmd/velero/velero.go b/cmd/velero/velero.go index 07be4a884..6b150b844 100644 --- a/cmd/velero/velero.go +++ b/cmd/velero/velero.go @@ -22,8 +22,8 @@ import ( "k8s.io/klog/v2" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/velero" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/velero" ) func main() { diff --git a/design/2082-bsl-delete-associated-resources_design.md b/design/2082-bsl-delete-associated-resources_design.md index da5ac0bf0..907d10bcf 100644 --- a/design/2082-bsl-delete-associated-resources_design.md +++ b/design/2082-bsl-delete-associated-resources_design.md @@ -20,7 +20,7 @@ Update the `velero backup-location delete ` command to delete associat ## Non Goals -[It was suggested](https://github.com/vmware-tanzu/velero/issues/2082#issuecomment-827951311) to fix bug #2697 alongside this issue. +[It was suggested](https://github.com/velero-io/velero/issues/2082#issuecomment-827951311) to fix bug #2697 alongside this issue. However, I think that should be fixed separately because although it is similar (restore objects are not being deleted), it is also quite different. One is adding a command feature update (this issue) and the other is a bug fix and each affect different parts of the code base. @@ -31,7 +31,7 @@ Update the `velero backup-location delete ` command to do the followin - find in the same Velero namespace from which the BSL was deleted the associated backup resources and Restic repositories, called "backups.velero.io" and "resticrepositories.velero.io" respectively - delete the resources found -The above logic will be added to [where BSLs are deleted](https://github.com/vmware-tanzu/velero/blob/main/pkg/cmd/cli/backuplocation/delete.go). +The above logic will be added to [where BSLs are deleted](https://github.com/velero-io/velero/blob/main/pkg/cmd/cli/backuplocation/delete.go). ## Alternative Considered diff --git a/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md b/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md index e1503dba5..2798dc5bd 100644 --- a/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md +++ b/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md @@ -2,7 +2,7 @@ ## Abstract -Currently, the [VolumePolicies feature](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) which can be used to filter/handle volumes during backup only supports the skip action on matching conditions. Users need more actions to be supported. +Currently, the [VolumePolicies feature](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) which can be used to filter/handle volumes during backup only supports the skip action on matching conditions. Users need more actions to be supported. ## Background @@ -58,17 +58,17 @@ volumePolicies: ``` ## High-Level Design - When the VolumePolicy action is set as `fs-backup` the backup workflow modifications would be: - - We call [backupItem() -> backupItemInternal()](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up - - Here when we encounter [Pod as an item ](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L195) + - We call [backupItem() -> backupItemInternal()](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up + - Here when we encounter [Pod as an item ](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L195) - We will have to modify the backup workflow to account for the `fs-backup` VolumePolicy action - When the VolumePolicy action is set as `snapshot` the backup workflow modifications would be: - - Once again, We call [backupItem() -> backupItemInternal()](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up - - Here when we encounter [Persistent Volume as an item](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L253) - - And we call the [takePVSnapshot func](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) + - Once again, We call [backupItem() -> backupItemInternal()](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up + - Here when we encounter [Persistent Volume as an item](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L253) + - And we call the [takePVSnapshot func](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) - We need to modify the takePVSnapshot function to account for the `snapshot` VolumePolicy action. - - In case of csi snapshots for PVC objects, these snapshot actions are taken by the velero-plugin-for-csi, we need to modify the [executeActions()](https://github.com/vmware-tanzu/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L232) function to account for the `snapshot` VolumePolicy action. + - In case of csi snapshots for PVC objects, these snapshot actions are taken by the velero-plugin-for-csi, we need to modify the [executeActions()](https://github.com/velero-io/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L232) function to account for the `snapshot` VolumePolicy action. **Note:** `Snapshot` action can either be a native snapshot or a csi snapshot, as is the case with the current flow where velero itself makes the decision based on the backup CR. @@ -80,9 +80,9 @@ volumePolicies: - Else continue with the annotation based legacy approach workflow. - Modifications needed for `snapshot` action: - - In the [takePVSnapshot function](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) we will check the PV fits the volume policy criteria and see if the associated action is `snapshot` + - In the [takePVSnapshot function](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) we will check the PV fits the volume policy criteria and see if the associated action is `snapshot` - If it is not snapshot then we skip the further workflow and avoid taking the snapshot of the PV - - Similarly, For csi snapshot of PVC object, we need to do similar changes in [executeAction() function](https://github.com/vmware-tanzu/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L348). we will check the PVC fits the volume policy criteria and see if the associated action is `snapshot` via csi plugin + - Similarly, For csi snapshot of PVC object, we need to do similar changes in [executeAction() function](https://github.com/velero-io/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L348). we will check the PVC fits the volume policy criteria and see if the associated action is `snapshot` via csi plugin - If it is not snapshot then we skip the csi BIA execute action and avoid taking the snapshot of the PVC by not invoking the csi plugin action for the PVC **Note:** @@ -338,7 +338,7 @@ In the future, we envision the following actions that can be implemented: ## Related to Design -[Handle backup of volumes by resources filters](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) +[Handle backup of volumes by resources filters](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) ## Alternatives Considered Same as the earlier design as this is an extension of the original VolumePolicies design \ No newline at end of file diff --git a/design/Implemented/clean_artifacts_in_csi_flow.md b/design/Implemented/clean_artifacts_in_csi_flow.md index 2d42bb2a9..2f1b18181 100644 --- a/design/Implemented/clean_artifacts_in_csi_flow.md +++ b/design/Implemented/clean_artifacts_in_csi_flow.md @@ -371,4 +371,4 @@ In this design, no new information is added in backup and restore. As a result, ## Open Issues Please notice the CSI snapshot backup and restore mechanism not supporting all file-store-based volume, e.g. Azure Files, EFS or vSphere CNS File Volume. Only block-based volumes are supported. -Refer to [this comment](https://github.com/vmware-tanzu/velero/issues/3151#issuecomment-2623507686) for more details. +Refer to [this comment](https://github.com/velero-io/velero/issues/3151#issuecomment-2623507686) for more details. diff --git a/design/Implemented/cluster-scope-resource-filter.md b/design/Implemented/cluster-scope-resource-filter.md index 37267c5ac..a5ae5ea75 100644 --- a/design/Implemented/cluster-scope-resource-filter.md +++ b/design/Implemented/cluster-scope-resource-filter.md @@ -382,7 +382,7 @@ type BackupSpec struct { ``` ## Alternatives Considered -Proposal from Jibu Data [Issue 5120](https://github.com/vmware-tanzu/velero/issues/5120#issue-1304534563) +Proposal from Jibu Data [Issue 5120](https://github.com/velero-io/velero/issues/5120#issue-1304534563) ## Security Considerations No security impact. @@ -399,4 +399,4 @@ Plan to deprecate `IncludedResources`, `ExcludedResources` and `IncludeClusterRe ## Open Issues `LabelSelector/OrLabelSelectors` apply to namespace-scoped resources. It may be reasonable to make them also working on cluster-scoped resources. -An issue is created to trace this topic [resource label selector not work for cluster-scoped resources](https://github.com/vmware-tanzu/velero/issues/5787) +An issue is created to trace this topic [resource label selector not work for cluster-scoped resources](https://github.com/velero-io/velero/issues/5787) diff --git a/design/Implemented/custom-ca-support.md b/design/Implemented/custom-ca-support.md index 05bf9e769..b1a3936ad 100644 --- a/design/Implemented/custom-ca-support.md +++ b/design/Implemented/custom-ca-support.md @@ -73,8 +73,8 @@ This same approach can be taken for CA bundles. The bundle can be stored in a secret which is referenced on the BSL and written to a temp file prior to invoking Restic. -[1](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/repository_manager.go#L238-L245) -[2](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/common.go#L168-L203) +[1](https://github.com/velero-io/velero/blob/main/pkg/restic/repository_manager.go#L238-L245) +[2](https://github.com/velero-io/velero/blob/main/pkg/restic/common.go#L168-L203) ## Detailed Design @@ -126,7 +126,7 @@ would look like: $ velero client config set cacert PATH ``` -[1]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L135 -[2]: https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/command.go#L47 +[1]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L135 +[2]: https://github.com/velero-io/velero/blob/main/pkg/restic/command.go#L47 [3]: https://github.com/restic/restic/blob/main/internal/backend/http_transport.go#L81 -[4]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L154 +[4]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L154 diff --git a/design/Implemented/existing-resource-policy_design.md b/design/Implemented/existing-resource-policy_design.md index 7d119b8e7..0c4bd84d3 100644 --- a/design/Implemented/existing-resource-policy_design.md +++ b/design/Implemented/existing-resource-policy_design.md @@ -8,12 +8,12 @@ As of Today, Velero will skip over the restoration of resources that already exi - Fetches the `service` from the cluster - If the `service` exists then: - Checks whether the `service` instance in the cluster is equal to the `service` instance present in backup - - If not equal then skips the restore of the `service` and adds a restore warning (except for [ServiceAccount objects](https://github.com/vmware-tanzu/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/restore/restore.go#L1246)) + - If not equal then skips the restore of the `service` and adds a restore warning (except for [ServiceAccount objects](https://github.com/velero-io/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/restore/restore.go#L1246)) - If equal then skips the restore of the `service` and mentions that the restore of resource `service` is skipped in logs It is desired to add the functionality to specify whether or not to overwrite the instance of resource `service` in cluster with the one present in backup during the restore process. -Related issue: https://github.com/vmware-tanzu/velero/issues/4066 +Related issue: https://github.com/velero-io/velero/issues/4066 ## Goals - Add support for `ExistingResourcePolicy` to restore API for Kubernetes resources. @@ -31,7 +31,7 @@ Related issue: https://github.com/vmware-tanzu/velero/issues/4066 ### A. Production Cluster - Backup Cluster: Let's say you have a Backup Cluster which is identical to the Production Cluster. After some operations/usage/time the Production Cluster had changed itself, there might be new deployments, some secrets might have been updated. Now, this means that the Backup cluster will no longer be identical to the Production Cluster. In order to keep the Backup Cluster up to date/identical to the Production Cluster with respect to Kubernetes resources except PV data we would like to use Velero for scheduling new backups which would in turn help us update the Backup Cluster via Velero restore. -Reference: https://github.com/vmware-tanzu/velero/issues/4066#issuecomment-954320686 +Reference: https://github.com/velero-io/velero/issues/4066#issuecomment-954320686 ### B. Help identify resource delta: Here delta resources mean the resources restored by a previous backup, but they are no longer in the latest backup. Let's follow a sequence of steps to understand this scenario: @@ -43,7 +43,7 @@ Here delta resources mean the resources restored by a previous backup, but they - So the Delta here is (|Cluster B - Backup2|), Delete P1 and Update P2. - During Restore time we would want the Restore to help us identify this resource delta. -Reference: https://github.com/vmware-tanzu/velero/pull/4613#issuecomment-1027260446 +Reference: https://github.com/velero-io/velero/pull/4613#issuecomment-1027260446 ## High-Level Design ### Approach 1: Add a new spec field `existingResourcePolicy` to the Restore API @@ -238,7 +238,7 @@ IncludedResources []string } ``` -The restore workflow changes will be done [here](https://github.com/vmware-tanzu/velero/blob/b40bbda2d62af2f35d1406b9af4d387d4b396839/pkg/restore/restore.go#L1245) +The restore workflow changes will be done [here](https://github.com/velero-io/velero/blob/b40bbda2d62af2f35d1406b9af4d387d4b396839/pkg/restore/restore.go#L1245) ### CLI changes for Approach 1 We would introduce a new CLI flag called `existing-resource-policy` of string type. This flag would be used to accept the diff --git a/design/Implemented/general-progress-monitoring.md b/design/Implemented/general-progress-monitoring.md index 35c2ed2ae..6f64a0d4b 100644 --- a/design/Implemented/general-progress-monitoring.md +++ b/design/Implemented/general-progress-monitoring.md @@ -526,24 +526,24 @@ updates. Here is a list of some of these items: 1. Consts for the "Uploading" and "UploadingPartiallyFailed" phases have already been defined. These will need to be removed when the "WaitingForPluginOperations" and "WaitingForPluginOperationsPartiallyFailed" phases are defined. - - https://github.com/vmware-tanzu/velero/pull/3805 + - https://github.com/velero-io/velero/pull/3805 1. Remove the ItemSnapshotter plugin APIs (and related code) since the revised design will reuse VolumeSnapshotter and BackupItemAction plugins. - - https://github.com/vmware-tanzu/velero/pull/4077 - - https://github.com/vmware-tanzu/velero/pull/4417 + - https://github.com/velero-io/velero/pull/4077 + - https://github.com/velero-io/velero/pull/4417 1. UploadProgressFeatureFlag shouldn't be needed anymore. The current design won't really need a feature flag here -- the new features will be added to V2 of the VolumeSnapshotter, BackupItemAction, and RestoreItemAction plugins, and it will only be used if there are plugins which return operation IDs. - - https://github.com/vmware-tanzu/velero/pull/4416 + - https://github.com/velero-io/velero/pull/4416 1. Adds -itemsnapshots.gz file to backup (when provided) -- this is still part of the revised design, so it should stay. - - https://github.com/vmware-tanzu/velero/pull/4429 + - https://github.com/velero-io/velero/pull/4429 1. Upload Progress Monitoring and Item Snapshotter basic support: This PR is not yet merged, so nothing will need to be reverted. While the implementation here will be useful in informing the implementation of the new design, several things have changed in the design proposal since the PR was written. - - https://github.com/vmware-tanzu/velero/pull/4467 + - https://github.com/velero-io/velero/pull/4467 # Implementation tasks diff --git a/design/Implemented/include-exclude-in-resource-policy.md b/design/Implemented/include-exclude-in-resource-policy.md index ddba2a874..ead936ddb 100644 --- a/design/Implemented/include-exclude-in-resource-policy.md +++ b/design/Implemented/include-exclude-in-resource-policy.md @@ -4,7 +4,7 @@ This enhancement will allow the user to set include and exclude filters for reso these filters are reusable and the user will not need to set them each time they create a backup. ## Background -As mentioned in issue [#8610](https://github.com/vmware-tanzu/velero/issues/8610). When there's a long list of resources +As mentioned in issue [#8610](https://github.com/velero-io/velero/issues/8610). When there's a long list of resources to include or exclude in a backup, it can be cumbersome to set them each time a backup is created. There's a requirement to set these filters in a separate data structure so that they can be reused in multiple backups. diff --git a/design/Implemented/json-substitution-action-design.md b/design/Implemented/json-substitution-action-design.md index 102503beb..f48834e76 100644 --- a/design/Implemented/json-substitution-action-design.md +++ b/design/Implemented/json-substitution-action-design.md @@ -150,7 +150,7 @@ Compatibility with existing StorageClass mapping RestoreItemAction and similar p ## Implementation - Changes in Restore CRD. Add a new field to the RestoreSpec to reference the configmap. -- One example of where code will be modified: https://github.com/vmware-tanzu/velero/blob/eeee4e06d209df7f08bfabda326b27aaf0054759/pkg/restore/restore.go#L1266 On the obj before Creation, we can apply the conditions to check if the resource is filtered out using given parameters. Then using JsonPatch provided, we can update the resource. +- One example of where code will be modified: https://github.com/velero-io/velero/blob/eeee4e06d209df7f08bfabda326b27aaf0054759/pkg/restore/restore.go#L1266 On the obj before Creation, we can apply the conditions to check if the resource is filtered out using given parameters. Then using JsonPatch provided, we can update the resource. - For Jsonpatch - https://github.com/evanphx/json-patch library is used. - JSON Patch RFC https://datatracker.ietf.org/doc/html/rfc6902 diff --git a/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md b/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md index a8127bc49..a5f34317a 100644 --- a/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md +++ b/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md @@ -49,7 +49,7 @@ This proposal is to add support for JSON Merge Patch and Strategic Merge Patch i - New fields `MergePatches` and `StrategicPatches` will be added to the `ResourceModifierRule` struct to support all three patch types. - Only one of the three patch types can be specified in a single `ResourceModifierRule`. - Add wildcard support for `groupResource` in `conditions` struct. -- The workflow to create Resource Modifier ConfigMap and reference it in RestoreSpec will remain the same as described in document [Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/site/content/docs/main/restore-resource-modifiers.md). +- The workflow to create Resource Modifier ConfigMap and reference it in RestoreSpec will remain the same as described in document [Resource Modifiers](https://github.com/velero-io/velero/blob/main/site/content/docs/main/restore-resource-modifiers.md). ### How to choose the right patch type - [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) is a naively simple format, with limited usability. Probably it is a good choice if you are building something small, with very simple JSON Schema. @@ -187,7 +187,7 @@ Compatible with current Resource Modifiers. ## Future enhancements - add a Velero subcommand to generate/validate the patchData for Strategic Merge Patch and JSON Merge Patch. -- add jq support for more complex conditions or patches, to meet the situations that the current conditions or patches can not handle. like [this issue](https://github.com/vmware-tanzu/velero/issues/6344) +- add jq support for more complex conditions or patches, to meet the situations that the current conditions or patches can not handle. like [this issue](https://github.com/velero-io/velero/issues/6344) ## Open Issues N/A diff --git a/design/Implemented/move-gh-org.md b/design/Implemented/move-gh-org.md index 0d76a748a..0a2102257 100644 --- a/design/Implemented/move-gh-org.md +++ b/design/Implemented/move-gh-org.md @@ -17,7 +17,7 @@ Currently, the Velero repository sits under the Heptio GitHub organization. With #### Pre move - [ ] PR: Blog post communicating the move. https://github.com/heptio/velero/issues/1841. Who: TBD. -- [ ] PR: Find/replace in all Go, script, yaml, documentation, and website files: `github.com/heptio/velero -> github.com/vmware-tanzu/velero`. Who: a Velero developer; TBD +- [ ] PR: Find/replace in all Go, script, yaml, documentation, and website files: `github.com/heptio/velero -> github.com/velero-io/velero`. Who: a Velero developer; TBD - [ ] PR: Update website with the correct GH links. Who: a Velero developer; TBD - [ ] PR: Change deployment and grpc-push scripts with the new location path. Who: a Velero developer; TBD - [ ] Delete branches not to be carried over (https://github.com/heptio/velero/branches/all). Who: Any of the current repo owners; TBD @@ -32,7 +32,7 @@ Currently, the Velero repository sits under the Heptio GitHub organization. With #### Post move -- [ ] Each individual developer should point their origin to the new location: `git remote set-url origin git@github.com:vmware-tanzu/velero.git` +- [ ] Each individual developer should point their origin to the new location: `git remote set-url origin git@github.com:velero-io/velero.git` - [ ] Transfer ZenHub. Who: Any of the new repo owners; TBD - [ ] Update Netlify deploy settings. Any of the new repo owners; TBD - [ ] GH app: Netlify integration. Who: Any of the new repo owners; TBD diff --git a/design/Implemented/multiple-csi-volumesnapshotclass-support.md b/design/Implemented/multiple-csi-volumesnapshotclass-support.md index 089557193..a1fa1557e 100644 --- a/design/Implemented/multiple-csi-volumesnapshotclass-support.md +++ b/design/Implemented/multiple-csi-volumesnapshotclass-support.md @@ -95,7 +95,7 @@ The Velero CSI plugin chooses the VolumeSnapshotClass in the cluster that has th We can add support for - velero backup create my-backup --annotations "velero.io/csi:csi.cloud.disk.driver=csi-diskdriver-snapclass" ### Stage 2 Approach -The above annotations route is to get started and for initial design closure/ implementation, north star is to either introduce CSI specific fields (considering that CSI might be a very core part of velero going forward) in the backup/restore CR OR leverage the pluginInputs field as being tracked in: https://github.com/vmware-tanzu/velero/pull/5981 +The above annotations route is to get started and for initial design closure/ implementation, north star is to either introduce CSI specific fields (considering that CSI might be a very core part of velero going forward) in the backup/restore CR OR leverage the pluginInputs field as being tracked in: https://github.com/velero-io/velero/pull/5981 Refer section Alternatives 2. **Through generic property bag in the velero contracts**: in the design doc for more details on the pluginInputs field. diff --git a/design/Implemented/multiple-label-selectors_design.md b/design/Implemented/multiple-label-selectors_design.md index 9c301f3b5..d4d9e144b 100644 --- a/design/Implemented/multiple-label-selectors_design.md +++ b/design/Implemented/multiple-label-selectors_design.md @@ -14,7 +14,7 @@ backup for resources consisting of a label from a set of labels (label1 OR label create multiple backups per label rule. It would be really useful if Velero Backup API could respect a set of labels (OR Rule) for a single backup request. -Related Issue: https://github.com/vmware-tanzu/velero/issues/1508 +Related Issue: https://github.com/velero-io/velero/issues/1508 ## Goals - Enable support for backing up resources based on multiple labels (OR Logic) in a single backup config. @@ -130,9 +130,9 @@ OrLabelSelectors []\*metav1.LabelSelector ``` The logic to collect resources to be backed up for a particular backup will be updated in the `backup/item_collector.go` -around [here](https://github.com/vmware-tanzu/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/backup/item_collector.go#L294). +around [here](https://github.com/velero-io/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/backup/item_collector.go#L294). -And for filtering the resources to be restored, the changes will go [here](https://github.com/vmware-tanzu/velero/blob/d1063bda7e513150fd9ae09c3c3c8b1115cb1965/pkg/restore/restore.go#L1769) +And for filtering the resources to be restored, the changes will go [here](https://github.com/velero-io/velero/blob/d1063bda7e513150fd9ae09c3c3c8b1115cb1965/pkg/restore/restore.go#L1769) **Note:** - This feature will not be exposed via Velero CLI. \ No newline at end of file diff --git a/design/Implemented/plugin-backup-and-restore-progress-design.md b/design/Implemented/plugin-backup-and-restore-progress-design.md index 46544f01b..f3eefd0b5 100644 --- a/design/Implemented/plugin-backup-and-restore-progress-design.md +++ b/design/Implemented/plugin-backup-and-restore-progress-design.md @@ -154,7 +154,7 @@ In order to know the CR created for the particular backup of a volume, Velero ad - `velero.io/pv-name` with value as volume that is undergoing backup Backup name being unique won't cause issues like duplicates in identifying the CR. -Labels will be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). +Labels will be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). If Plugin supports showing progress of the operation it is performing, it does following: - finds the VolumePluginBackup CR related to this backup operation by using `tags` passed in CreateSnapshot call @@ -281,7 +281,7 @@ In order to know the CR created for the particular restore of a volume, Velero a - `velero.io/snapshot-id` with value as snapshot id that need to be restored - `velero.io/provider` with value as `Provider` in `VolumeSnapshotLocation` -Labels will be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). +Labels will be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). Plugin will be able to identify CR by using snapshotID that it received as parameter of CreateVolumeFromSnapshot API, and plugin's Provider name. It updates the progress of restore operation regularly if plugin supports feature of showing progress. @@ -376,7 +376,7 @@ In order to know the CR created for the particular backup of a volume, volume sn Backup name being unique won't cause issues like duplicates in identifying the CR. -Plugin need to sanitize the value that can be set for above labels. Label need to be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). +Plugin need to sanitize the value that can be set for above labels. Label need to be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). Though no restrictions are required on the name of CR, as a general practice, volume snapshotter can name this CR with the value same as return value of CreateSnapshot. diff --git a/design/Implemented/plugin-versioning.md b/design/Implemented/plugin-versioning.md index 43b236f96..99e3eaae0 100644 --- a/design/Implemented/plugin-versioning.md +++ b/design/Implemented/plugin-versioning.md @@ -92,7 +92,7 @@ type ObjectStore interface { If a method is being added to the `ObjectStore` API, a file would be added to `pkg/plugin/velero/objectstore/v2/` and may contain a new API definition as follows: ``` -import "github.com/vmware-tanzu/velero/pkg/plugin/velero/objectstore/v1" +import "github.com/velero-io/velero/pkg/plugin/velero/objectstore/v1" type ObjectStore interface { // Import all the methods from the previous version of the API if they are to be included as is @@ -147,15 +147,15 @@ The message definitions can be shared however, so these could be extracted from ### Plugin Framework To allow plugins to register which versions of the API they implement, the plugin framework will need to be adapted to accept new versions. -Currently, the plugin manager stores a [`map[string]RestartableProcess`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L69), where the string key is the binary name for the plugin process (e.g. "velero-plugin-for-aws"). -Each `RestartableProcess` contains a [`map[kindAndName]interface{}`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/restartable_process.go#L60) which represents each of the unique plugin implementations provided by that binary. -[`kindAndName`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/registry.go#L42) is a struct which combines the plugin kind (`ObjectStore`, `VolumeSnapshotter`) and the plugin name ("velero.io/aws", "velero.io/azure"). +Currently, the plugin manager stores a [`map[string]RestartableProcess`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L69), where the string key is the binary name for the plugin process (e.g. "velero-plugin-for-aws"). +Each `RestartableProcess` contains a [`map[kindAndName]interface{}`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/restartable_process.go#L60) which represents each of the unique plugin implementations provided by that binary. +[`kindAndName`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/registry.go#L42) is a struct which combines the plugin kind (`ObjectStore`, `VolumeSnapshotter`) and the plugin name ("velero.io/aws", "velero.io/azure"). Each plugin version registration must be unique (to allow for multiple versions to be implemented within the same plugin binary). This will be achieved by adding a specific registration method for each version to the Server interface in the plugin framework. For example, if adding a V2 `RestoreItemAction` plugin, the Server interface would be modified to add the `RegisterRestoreItemActionV2` method. -This would require [adding a new plugin Kind const](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/framework/plugin_kinds.go#L28-L46) to represent the new plugin version, e.g. `PluginKindRestoreItemActionV2`. -It also requires the creation of a new implementation of the go-plugin interface ([example](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/framework/object_store.go)) to support that version and use the generated gRPC code from the proto definition (including a client and server implementation). +This would require [adding a new plugin Kind const](https://github.com/velero-io/velero/blob/main/pkg/plugin/framework/plugin_kinds.go#L28-L46) to represent the new plugin version, e.g. `PluginKindRestoreItemActionV2`. +It also requires the creation of a new implementation of the go-plugin interface ([example](https://github.com/velero-io/velero/blob/main/pkg/plugin/framework/object_store.go)) to support that version and use the generated gRPC code from the proto definition (including a client and server implementation). The Server will also need to be adapted to recognize this new plugin Kind and to serve the new implementation. Existing plugin Kind consts and registration methods will be left unchanged and will correspond to the current version of the plugin APIs (assumed to be v1). @@ -241,7 +241,7 @@ In cases where the methods signatures remain the same, the adaptation layer will Examples where an adaptation may be safe: - A method signature is being changed to add a new parameter but the parameter could be optional (for example, adding a context parameter). The adaptation could call through to the method provided in the previous version but omit the parameter. - A method signature is being changed to remove a parameter, but it is safe to pass a default value to the previous version. The adaptation could call through to the method provided in the previous version but use a default value for the parameter. -- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed. +- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/velero-io/velero/blob/main/design/Implemented/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed. - A method is being deleted as it is no longer used. The adaptation would call through to any methods which are still included but would omit the deleted method in the adaptation. Examples where an adaptation may not be safe: diff --git a/design/Implemented/pv-cloning.md b/design/Implemented/pv-cloning.md index f840bda84..8140a0641 100644 --- a/design/Implemented/pv-cloning.md +++ b/design/Implemented/pv-cloning.md @@ -32,11 +32,11 @@ It will also update the `spec.volumeName` of the related persistent volume claim ## Detailed Design -In `pkg/restore/restore.go`, around [line 872](https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L872), Velero has special-case code for persistent volumes. +In `pkg/restore/restore.go`, around [line 872](https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L872), Velero has special-case code for persistent volumes. This code will be updated to check for the two preconditions described in the previous section. If the preconditions are met, the object will be given a new name. The persistent volume will also be annotated with the original name, e.g. `velero.io/original-pv-name=NAME`. -Importantly, the name change will occur **before** [line 890](https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L890), where Velero checks to see if it should restore the persistent volume. +Importantly, the name change will occur **before** [line 890](https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L890), where Velero checks to see if it should restore the persistent volume. Additionally, the old and new persistent volume names will be recorded in a new field that will be added to the `context` struct, `renamedPVs map[string]string`. In the special-case code for persistent volume claims starting on [line 987](https://github.com/heptio/velero/blob/main/pkg/restore/restore.go#L987), Velero will check to see if the claimed persistent volume has been renamed by looking in `ctx.renamedPVs`. diff --git a/design/Implemented/pv_backup_info.md b/design/Implemented/pv_backup_info.md index 90cd998cb..ff080a797 100644 --- a/design/Implemented/pv_backup_info.md +++ b/design/Implemented/pv_backup_info.md @@ -9,7 +9,7 @@ This new additional metadata file is needed when: * Retrieve the PV's snapshot information for backup. ## Background -There is already a [PR](https://github.com/vmware-tanzu/velero/pull/6496) to track the skipped PVC in the backup. This design will depend on it and go further to get a summary of PVC and PV information, then persist into a metadata file in the backup repository. +There is already a [PR](https://github.com/velero-io/velero/pull/6496) to track the skipped PVC in the backup. This design will depend on it and go further to get a summary of PVC and PV information, then persist into a metadata file in the backup repository. In the restore process, the Velero server needs to decide how the PV resource should be restored according to how the PV is backed up. The current logic is to check whether it's backed up by Velero-native snapshot, by file-system backup, or having `DeletionPolicy` set as `Delete`. @@ -28,7 +28,7 @@ Another thing that needs noticing is when describing the backup, there is no gen ## High-Level Design Create _backup-name_-volumes-info.json metadata file in the backup's repository. This file will be encoded to contain all the PVC and PV information included in the backup. The information covers whether the PV or PVC's data is skipped during backup, how its data is backed up, and the backed-up detail information. -Please notice that the new metadata file includes all skipped volume information. This is used to address [the second phase needs of skipped volumes information](https://github.com/vmware-tanzu/velero/issues/5834#issuecomment-1526624211). +Please notice that the new metadata file includes all skipped volume information. This is used to address [the second phase needs of skipped volumes information](https://github.com/velero-io/velero/issues/5834#issuecomment-1526624211). The `restoreItem` function can decode the _backup-name_-volumes-info.json file to determine how to handle the PV resource. @@ -169,13 +169,13 @@ After introducing the VolumeInfo array, the following logic will be added. _backup-name_-volumes-info.json file is deleted during backup deletion. ## Alternatives Considered -The restore process needs more information about how the PVs are backed up to determine whether this PV should be restored. The released branches also need a similar function, but backporting a new feature into previous releases may not be a good idea, so according to [Anshul Ahuja's suggestion](https://github.com/vmware-tanzu/velero/issues/6595#issuecomment-1731081580), adding more cases here to support checking PV backed-up by CSI plugin and CSI snapshot data mover: https://github.com/vmware-tanzu/velero/blob/5ff5073cc3f364bafcfbd26755e2a92af68ba180/pkg/restore/restore.go#L1206-L1324. +The restore process needs more information about how the PVs are backed up to determine whether this PV should be restored. The released branches also need a similar function, but backporting a new feature into previous releases may not be a good idea, so according to [Anshul Ahuja's suggestion](https://github.com/velero-io/velero/issues/6595#issuecomment-1731081580), adding more cases here to support checking PV backed-up by CSI plugin and CSI snapshot data mover: https://github.com/velero-io/velero/blob/5ff5073cc3f364bafcfbd26755e2a92af68ba180/pkg/restore/restore.go#L1206-L1324. ## Security Considerations There should be no security impact introduced by this design. ## Compatibility -After this design is implemented, there should be no impact on the existing [skipped PVC summary feature](https://github.com/vmware-tanzu/velero/pull/6496). +After this design is implemented, there should be no impact on the existing [skipped PVC summary feature](https://github.com/velero-io/velero/pull/6496). To support older version backup, which doesn't have the VolumeInfo metadata file, the old logic, which is checking the Velero native snapshots list, PodVolumeBackup list, and PVC DeletionPolicy, is still kept, and supporting CSI snapshots and snapshot data mover logic will be added too. diff --git a/design/Implemented/pv_restore_info.md b/design/Implemented/pv_restore_info.md index d2e49655c..91df863af 100644 --- a/design/Implemented/pv_restore_info.md +++ b/design/Implemented/pv_restore_info.md @@ -139,5 +139,5 @@ The data structures referenced by volume info is shared between both restore and we must make sure there will only be incremental changes to the metadata, such that no break change will be introduced to the client. ## Open Issues -https://github.com/vmware-tanzu/velero/issues/7546 -https://github.com/vmware-tanzu/velero/issues/6478 +https://github.com/velero-io/velero/issues/7546 +https://github.com/velero-io/velero/issues/6478 diff --git a/design/Implemented/repo_maintenance_job_config.md b/design/Implemented/repo_maintenance_job_config.md index 195b5b9dc..cda8a9a5c 100644 --- a/design/Implemented/repo_maintenance_job_config.md +++ b/design/Implemented/repo_maintenance_job_config.md @@ -20,7 +20,7 @@ This design reuses the data structure introduced by design [Velero Generic Data - Let user can choose repository maintenance Job running on which nodes. ## Non Goals -- There was an [issue](https://github.com/vmware-tanzu/velero/issues/7911) to require the whole Job's PodSpec should be configurable. That's not in the scope of this design. +- There was an [issue](https://github.com/velero-io/velero/issues/7911) to require the whole Job's PodSpec should be configurable. That's not in the scope of this design. - Please notice this new configuration is dedicated for the repository maintenance. Repository itself configuration is not covered. @@ -43,7 +43,7 @@ Propose to deprecate the `velero server` parameters `--maintenance-job-cpu-reque That means those parameters will be deleted in release-1.17. After deletion, those resources-related parameters are replaced by the ConfigMap specified by `velero server` CLI's parameter `--repo-maintenance-job-configmap`. `--keep-latest-maintenance-jobs` is deleted from `velero server` CLI. It turns into a non-configurable internal parameter, and its value is 3. -Please check [issue 7923](https://github.com/vmware-tanzu/velero/issues/7923) for more information why deleting this parameter. +Please check [issue 7923](https://github.com/velero-io/velero/issues/7923) for more information why deleting this parameter. ## Design This design introduces a new ConfigMap specified by `velero server` CLI parameter `--repo-maintenance-job-configmap` as the source of the repository maintenance job configuration. The specified ConfigMap is read from the namespace where Velero is installed. @@ -92,7 +92,7 @@ The other keys in the map is the combination of three elements of a BackupReposi * The BackupRepository referenced BackupStorageLocation's name. * The BackupRepository's type. Possible values are `kopia` and `restic`. -Those three keys can identify a [unique BackupRepository](https://github.com/vmware-tanzu/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/repository/backup_repo_op.go#L32-L37). +Those three keys can identify a [unique BackupRepository](https://github.com/velero-io/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/repository/backup_repo_op.go#L32-L37). If there is a key match with BackupRepository, the key's value is applied to the BackupRepository's maintenance jobs. By this way, it's possible to let user configure before the BackupRepository is created. diff --git a/design/Implemented/resource-status-restore.md b/design/Implemented/resource-status-restore.md index f57e86a4f..9d394c1b8 100644 --- a/design/Implemented/resource-status-restore.md +++ b/design/Implemented/resource-status-restore.md @@ -76,7 +76,7 @@ metadata: We are targeting the implementation of this design for Velero 1.16 release. -Current restoreStatus logic resides here: https://github.com/vmware-tanzu/velero/blob/32a8c62920ad96c70f1465252c0197b83d5fa6b6/pkg/restore/restore.go#L1652 +Current restoreStatus logic resides here: https://github.com/velero-io/velero/blob/32a8c62920ad96c70f1465252c0197b83d5fa6b6/pkg/restore/restore.go#L1652 The modified logic would look somewhat like: diff --git a/design/Implemented/restore-finalizing-phase_design.md b/design/Implemented/restore-finalizing-phase_design.md index 0d4d0170d..7e84a2e61 100644 --- a/design/Implemented/restore-finalizing-phase_design.md +++ b/design/Implemented/restore-finalizing-phase_design.md @@ -9,7 +9,7 @@ Currently, the restore process enters a terminal phase once all item restoration To address this, a new finalization phase should be added to the existing restore workflow. in this phase, all plugin operations and item restoration has been fully completed, which provides a clean opportunity to perform any wrap-up work before termination, improving the overall restore process. Wrap-up tasks in Velero can serve several purposes: -- Post-restore modification - Velero can modify the restored data that was temporarily changed for some purpose but required to be changed back finally or data that was newly created but missing some information. For example, [issue6435](https://github.com/vmware-tanzu/velero/issues/6435) indicates that some custom settings(like labels, reclaim policy) on restored PVs was lost because those restored PVs was newly dynamically provisioned. Velero can address it by patching the PVs' custom settings back in the finalization phase. +- Post-restore modification - Velero can modify the restored data that was temporarily changed for some purpose but required to be changed back finally or data that was newly created but missing some information. For example, [issue6435](https://github.com/velero-io/velero/issues/6435) indicates that some custom settings(like labels, reclaim policy) on restored PVs was lost because those restored PVs was newly dynamically provisioned. Velero can address it by patching the PVs' custom settings back in the finalization phase. - Clean up unused data - Velero can identify and delete any data that are no longer needed after a successful restore in the finalization phase. - Post-restore validation - Velero can validate the state of restored data and report any errors to help users locate the issue in the finalization phase. diff --git a/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md b/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md index e5580f948..65891a898 100644 --- a/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md +++ b/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md @@ -8,7 +8,7 @@ This document proposes a solution to select an API group version to restore from ## Background -It is possible that between the time a backup has been made and a restore occurs that the target Kubernetes version has incremented more than one version. In such a case where at least a versions of Kubernetes was skipped, the preferred source cluster's API group versions for resources may no longer be supported by the target cluster. With [PR#2373](https://github.com/vmware-tanzu/velero/pull/2373), all supported API group versions were backed up if the EnableAPIGroupVersions feature flag was set for Velero. The next step (outlined by this design proposal) will be to see if any of the backed up versions are supported in the target cluster and if so, choose one to restore for each backed up resource. +It is possible that between the time a backup has been made and a restore occurs that the target Kubernetes version has incremented more than one version. In such a case where at least a versions of Kubernetes was skipped, the preferred source cluster's API group versions for resources may no longer be supported by the target cluster. With [PR#2373](https://github.com/velero-io/velero/pull/2373), all supported API group versions were backed up if the EnableAPIGroupVersions feature flag was set for Velero. The next step (outlined by this design proposal) will be to see if any of the backed up versions are supported in the target cluster and if so, choose one to restore for each backed up resource. ## Goals @@ -50,19 +50,19 @@ There are six objectives to achieve the above stated goals: ### Objective 1: Determine if the APIGroupVersionsFeatureFlag is enabled and Backup Objects use Status.FormatVersion 1.1.0 -For restore to be able to choose from multiple supported backed up versions, the feature flag must have been enabled during the restore processes. Backup objects must also have [Status.FormatVersion == "1.1.0"](https://github.com/vmware-tanzu/velero/blob/a1e182e723a8c5f6d4175d8db2361233a94d2502/pkg/backup/backup.go#L58). +For restore to be able to choose from multiple supported backed up versions, the feature flag must have been enabled during the restore processes. Backup objects must also have [Status.FormatVersion == "1.1.0"](https://github.com/velero-io/velero/blob/a1e182e723a8c5f6d4175d8db2361233a94d2502/pkg/backup/backup.go#L58). The reason for checking for the feature flag during restore is to ensure the user would like to restore a version that might not be the source cluster preferred version. This check is done via `features.IsEnabled(velerov1api.APIGroupVersionsFeatureFlag)`. The reason for checking `Status.FormatVersion` is to ensure the changes made by this proposed design is backward compatible. Only with Velero version 1.4 and forward was Format Version 1.1.0 used to structure the backup directories. Format Version 1.1.0 is required for the restore process proposed in this design doc to work. Before v1.4, the backed up files were in a directory structure that will not be recognized by the proposed code changes. In this case, restore should not attempt to restore from multiple versions as they will not exist. -The [`Status.FormatVersion`](https://github.com/vmware-tanzu/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/apis/velero/v1/backup.go#L235) is stored in a `restoreContext` struct field called [`backup`](https://github.com/vmware-tanzu/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/restore/restore.go#L229). The full chain is `ctx.backup.Status.FormatVersion`. +The [`Status.FormatVersion`](https://github.com/velero-io/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/apis/velero/v1/backup.go#L235) is stored in a `restoreContext` struct field called [`backup`](https://github.com/velero-io/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/restore/restore.go#L229). The full chain is `ctx.backup.Status.FormatVersion`. The above two checks can be done inside a new method on the `*restoreContext` object with the method signature `meetsAPIGVRestoreReqs() bool`. This method can remain in the `restore` package, but for organizational purposes, it can be moved to a file called `prioritize_group_version.go`. ### Objective 2: List the backed up API group versions -Currently, in `pkg/restore/restore.go`, in the `execute(...)` method, around [line 363](https://github.com/vmware-tanzu/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L363), the resources and their backed up items are saved in a map called `backupResources`. +Currently, in `pkg/restore/restore.go`, in the `execute(...)` method, around [line 363](https://github.com/velero-io/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L363), the resources and their backed up items are saved in a map called `backupResources`. At this point, the feature flag and format versions can be checked (described in Objective #1). If the requirements are met, the `backedupResources` map can be sent to a method (to be created) with the signature `ctx.chooseAPIVersionsToRestore(backupResources)`. The `ctx` object has the type `*restore.Context`. @@ -158,7 +158,7 @@ To see example cases with version priorities, see a blog post written by Rafael ### Objective 6: Modify the paths to the backup files in the tarball -The method doing the bulk of the restoration work is `ctx.restoreResource(...)`. Inside this method, around [line 714](https://github.com/vmware-tanzu/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L714) in `pkg/restore/restore.go`, the path to backup json file for the item being restored is set. +The method doing the bulk of the restoration work is `ctx.restoreResource(...)`. Inside this method, around [line 714](https://github.com/velero-io/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L714) in `pkg/restore/restore.go`, the path to backup json file for the item being restored is set. After the groupResource is instantiated at pkg/restore/restore.go:733, and before the `for` loop that ranges through the `items`, the `ctx.chosenGRVsToRestore` map can be checked. If the groupResource exists in the map, the path saved to `resource` variable can be updated. diff --git a/design/Implemented/retry-patching-configuration_design.md b/design/Implemented/retry-patching-configuration_design.md index 5975db6dd..0c2296774 100644 --- a/design/Implemented/retry-patching-configuration_design.md +++ b/design/Implemented/retry-patching-configuration_design.md @@ -7,7 +7,7 @@ If a patch call fails to update status to completion, it should be retried up to This design proposes a way to configure timeout for this retry time limit. ## Background -Original Issue: https://github.com/vmware-tanzu/velero/issues/7207 +Original Issue: https://github.com/velero-io/velero/issues/7207 Velero was performing a restore when the API server was rolling out to a new version. It had trouble connecting to the API server, but eventually, the restore was successful. @@ -17,7 +17,7 @@ After the connection was restored, it didn't attempt to update, causing the rest This can lead to incorrect decisions for other components that rely on the backup/restore CR status to determine completion. ## Goals -- Make timeout configurable for retry patching by reusing existing [`--resource-timeout` server flag](https://github.com/vmware-tanzu/velero/blob/d9ca14747925630664c9e4f85a682b5fc356806d/pkg/cmd/server/server.go#L245) +- Make timeout configurable for retry patching by reusing existing [`--resource-timeout` server flag](https://github.com/velero-io/velero/blob/d9ca14747925630664c9e4f85a682b5fc356806d/pkg/cmd/server/server.go#L245) ## Non Goals - Create a new timeout flag @@ -97,7 +97,7 @@ func RetryOnErrorMaxBackOff(maxDuration time.Duration, fn func() error) error { ``` ## Alternatives Considered - - Requeuing InProgress backups that is not known by current velero instance to still be in progress as failed (attempted in [#7863](https://github.com/vmware-tanzu/velero/pull/7863)) + - Requeuing InProgress backups that is not known by current velero instance to still be in progress as failed (attempted in [#7863](https://github.com/velero-io/velero/pull/7863)) - It was deemed as making backup restore flow hard to enhance for future reconciler updates such as adding cancel or adding parallel backups. ## Security Considerations @@ -107,5 +107,5 @@ None Retry should only trigger a restore or backup that is already in progress and not patching successfully by current instance. Prior InProgress backups/restores will not be re-processed and will remain stuck InProgress until there is another velero server (re)start. ## Implementation -There is a past implementation in [#7845](https://github.com/vmware-tanzu/velero/pull/7845/) where implementation for this design will be based upon. +There is a past implementation in [#7845](https://github.com/velero-io/velero/pull/7845/) where implementation for this design will be based upon. diff --git a/design/Implemented/schedule-skip-immediately-config_design.md b/design/Implemented/schedule-skip-immediately-config_design.md index 223e6b15a..f8dd8ea83 100644 --- a/design/Implemented/schedule-skip-immediately-config_design.md +++ b/design/Implemented/schedule-skip-immediately-config_design.md @@ -6,7 +6,7 @@ New Schedules also create new backup immediately. This design allows user to *skip **immediately due** backup run upon unpausing or schedule creation*. ## Background -Currently, the default behavior of schedule when `.Status.LastBackup` is nil or is due immediately after unpausing, a backup will be created. This may not be a desired by all users (https://github.com/vmware-tanzu/velero/issues/6517) +Currently, the default behavior of schedule when `.Status.LastBackup` is nil or is due immediately after unpausing, a backup will be created. This may not be a desired by all users (https://github.com/velero-io/velero/issues/6517) User want ability to skip the first immediately due backup when schedule is unpaused and or created. diff --git a/design/Implemented/secrets.md b/design/Implemented/secrets.md index b1999c037..56be05237 100644 --- a/design/Implemented/secrets.md +++ b/design/Implemented/secrets.md @@ -138,12 +138,12 @@ If we instead wanted to use an unique file each time, we could work around the o Once the credentials have been serialized, this path will be made available to the plugins. Instead of setting the necessary environment variable for the plugin process, the `config` map for the BSL will be modified to include an addiitional entry with the path to the credentials file: `credentialsFile`. -This will be passed through when [initializing the BSL](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/velero/object_store.go#L27-L30) and it will be the responsibility of the plugin to use the passed credentials when starting a session. -For an example of how this would affect the AWS plugin, see [this PR](https://github.com/vmware-tanzu/velero-plugin-for-aws/pull/69). +This will be passed through when [initializing the BSL](https://github.com/velero-io/velero/blob/main/pkg/plugin/velero/object_store.go#L27-L30) and it will be the responsibility of the plugin to use the passed credentials when starting a session. +For an example of how this would affect the AWS plugin, see [this PR](https://github.com/velero-io/velero-plugin-for-aws/pull/69). The restic controllers will also need to be updated to use the correct credentials. The BackupStorageLocation for a given PVB/PVR will be fetched and the `Credential` field from that BSL will be serialized. -The existing setup for the restic commands use the credentials from the environment variables with [some repo provider specific overrides](https://github.com/vmware-tanzu/velero/blob/main/pkg/controller/pod_volume_backup_controller.go#L260-L273). +The existing setup for the restic commands use the credentials from the environment variables with [some repo provider specific overrides](https://github.com/velero-io/velero/blob/main/pkg/controller/pod_volume_backup_controller.go#L260-L273). Instead of relying on the existing environment variables, if there are credentials for a particular BSL, the environment will be specifically created for each `RepoIdentifier`. This will use a lot of the existing logic with the exception that it will be modified to work with a serialized secret rather than find the secret file from an environment variable. Currently, GCP is the only provider that relies on the existing environment variables with no specific overrides. @@ -214,16 +214,16 @@ Prior to using any secret for a BSL, it will need to be serialized to disk. Using the details in the `Credential` field in the BSL, the contents of the Secret will be read and serialized to a file. Each plugin process would still have the same set of environment variables set, however the value used for each of these variables would instead be the path to the serialized secret. -To set the environment variables for a plugin process, the plugin manager must be modified so that when creating an ObjectStore, we pass in the entire BSL object, rather than [just the provider](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L132-L158). -The plugin manager currently stores a map of [plugin executables to an associated `RestartableProcess`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L59-L70). -New restartable processes are created only [with the executable that the process would run](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L122). -This could be modified to also take the necessary environment variables so that when [underlying go-plugin process is created](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/client_builder.go#L78), these environment variables could be provided and would be set on the plugin process. +To set the environment variables for a plugin process, the plugin manager must be modified so that when creating an ObjectStore, we pass in the entire BSL object, rather than [just the provider](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L132-L158). +The plugin manager currently stores a map of [plugin executables to an associated `RestartableProcess`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L59-L70). +New restartable processes are created only [with the executable that the process would run](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L122). +This could be modified to also take the necessary environment variables so that when [underlying go-plugin process is created](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/client_builder.go#L78), these environment variables could be provided and would be set on the plugin process. Taking this approach would not require any changes from plugins as the credentials information would be made available to them in the same way. However, it is quite a significant change in how we initialize and invoke plugins. We would also need to ensure that the restic controllers are updated in the same way so that correct credentials are used (when creating a `ResticRepository` or processing `PodVolumeBackup`/`PodVolumeRestore`). -This could be achieved by modifying the existing function to [run a restic command](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/repository_manager.go#L237-L290). +This could be achieved by modifying the existing function to [run a restic command](https://github.com/velero-io/velero/blob/main/pkg/restic/repository_manager.go#L237-L290). This function already sets environment variables for the restic process depending on which storage provider is being used. #### Include the details of the secret in `config` map passed to a plugin diff --git a/design/Implemented/supporting-volumeattributes-resource-policy.md b/design/Implemented/supporting-volumeattributes-resource-policy.md index a4f4d1bfc..d8f606d7f 100644 --- a/design/Implemented/supporting-volumeattributes-resource-policy.md +++ b/design/Implemented/supporting-volumeattributes-resource-policy.md @@ -1,7 +1,7 @@ # Adding Support For VolumeAttributes in Resource Policy ## Abstract -Currently [Velero Resource policies](https://velero.io/docs/main/resource-filtering/#creating-resource-policies) are only supporting "Driver" to be filtered for [CSI volume conditions](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28) +Currently [Velero Resource policies](https://velero.io/docs/main/resource-filtering/#creating-resource-policies) are only supporting "Driver" to be filtered for [CSI volume conditions](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28) If user want to skip certain CSI volumes based on other volume attributes like protocol or SKU, etc, they can't do it with the current Velero resource policies. It would be convenient if Velero resource policies could be extended to filter on volume attributes along with existing driver filter in the resource policies `conditions` to handle the backup of volumes just by `some specific volumes attributes conditions`. @@ -37,7 +37,7 @@ parameters: ``` ## High-Level Design -Modifying the existing Resource Policies code for [csiVolumeSource](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28C6-L28C22) to add the new `VolumeAttributes` filter for CSI volumes and adding validations in existing [csiCondition](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources.go#L150) to match with volume attributes in the conditions from Resource Policy config map and original persistent volume. +Modifying the existing Resource Policies code for [csiVolumeSource](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28C6-L28C22) to add the new `VolumeAttributes` filter for CSI volumes and adding validations in existing [csiCondition](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources.go#L150) to match with volume attributes in the conditions from Resource Policy config map and original persistent volume. ## Detailed Design The volume resources policies should contain a list of policies which is the combination of conditions and related `action`, when target volumes meet the conditions, the related `action` will take effection. diff --git a/design/Implemented/velero-debug.md b/design/Implemented/velero-debug.md index 7da56e48f..bde147585 100644 --- a/design/Implemented/velero-debug.md +++ b/design/Implemented/velero-debug.md @@ -3,7 +3,7 @@ ## Abstract To simplify the communication between velero users and developers, this document proposes the `velero debug` command to generate a tarball including the logs needed for debugging. -Github issue: https://github.com/vmware-tanzu/velero/issues/675 +Github issue: https://github.com/velero-io/velero/issues/675 ## Background Gathering information to troubleshoot a Velero deployment is currently spread across multiple commands, and is not very efficient. Logs for the Velero server itself are accessed via a kubectl logs command, while information on specific backups or restores are accessed via a Velero subcommand. Restic logs are even more complicated to retrieve, since one must gather logs for every instance of the daemonset, and there’s currently no good mechanism to locate which node a particular restic backup ran against. diff --git a/design/Implemented/vgdp-affinity-enhancement.md b/design/Implemented/vgdp-affinity-enhancement.md index dc9e458c7..b0edeca44 100644 --- a/design/Implemented/vgdp-affinity-enhancement.md +++ b/design/Implemented/vgdp-affinity-enhancement.md @@ -191,7 +191,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/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md b/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md index 0766bc9d4..bba5e67ca 100644 --- a/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md +++ b/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md @@ -654,9 +654,9 @@ CLI is not changed. [2]: ../volume-snapshot-data-movement/volume-snapshot-data-movement.md [3]: ../vgdp-micro-service/vgdp-micro-service.md [4]: ../node-agent-concurrency.md -[5]: https://github.com/vmware-tanzu/velero/issues/8955 -[6]: https://github.com/vmware-tanzu/velero/issues/8956 -[7]: https://github.com/vmware-tanzu/velero/issues/8289 +[5]: https://github.com/velero-io/velero/issues/8955 +[6]: https://github.com/velero-io/velero/issues/8956 +[7]: https://github.com/velero-io/velero/issues/8289 [8]: https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/ -[9]: https://github.com/vmware-tanzu/velero/issues/7725 -[10]: https://github.com/vmware-tanzu/velero/issues/8423 \ No newline at end of file +[9]: https://github.com/velero-io/velero/issues/7725 +[10]: https://github.com/velero-io/velero/issues/8423 \ No newline at end of file diff --git a/design/Implemented/volume-group-snapshot.md b/design/Implemented/volume-group-snapshot.md index 83bc5a574..d10cb6941 100644 --- a/design/Implemented/volume-group-snapshot.md +++ b/design/Implemented/volume-group-snapshot.md @@ -308,7 +308,7 @@ Backup workflow: } ``` -- Changes to the Existing [PVC ItemBlockAction plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/itemblock/actions/pvc_action.go#L64) (Update the GetRelatedItems function): +- Changes to the Existing [PVC ItemBlockAction plugin](https://github.com/velero-io/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/itemblock/actions/pvc_action.go#L64) (Update the GetRelatedItems function): ```go // Retrieve the VGS label key from the Backup spec. vgsLabelKey := backup.Spec.VolumeGroupSnapshotLabelKey @@ -338,7 +338,7 @@ Backup workflow: } ``` -- Updates to [CSI PVC plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/backup/actions/csi/pvc_action.go#L200) (Update the Execute method): +- Updates to [CSI PVC plugin](https://github.com/velero-io/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/backup/actions/csi/pvc_action.go#L200) (Update the Execute method): ```go func (p *pvcBackupItemAction) Execute( item runtime.Unstructured, diff --git a/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md b/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md index 8f46276b8..25a3a5456 100644 --- a/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md +++ b/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md @@ -931,7 +931,7 @@ For 3, Velero leverage on DMs to decide how to save the log, but they will not g DMs need to be configured during installation so that they can be installed. Plugin DMs may have their own configuration, for VGDM, the only requirement is to install Velero node-agent. Moreover, the DMP is also required during the installation. -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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/velero` repository. The reason to merge the CSI plugin is: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. diff --git a/design/Implemented/wait-for-additional-items.md b/design/Implemented/wait-for-additional-items.md index 8cff712b0..852c0a2f4 100644 --- a/design/Implemented/wait-for-additional-items.md +++ b/design/Implemented/wait-for-additional-items.md @@ -44,7 +44,7 @@ When each `RestoreItemAction` `Execute()` call returns, the restored. After restoring these items, Velero needs to be able to wait for them to be ready before moving on to the next item. Right after looping over the additional items at -https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L960-L991 +https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L960-L991 we still have a reference to the additional items (`GroupResource` and namespaced name), as well as a reference to the `RestoreItemAction` @@ -53,7 +53,7 @@ plugin which required it. At this point, if the `RestoreItemActionExecuteOutput` `WaitForAdditionalItems` field is set to `true` we need to call a func similar to `crdAvailable` which we will call `itemsAvailable` -https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L623 +https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L623 This func should also be defined within restore.go Instead of the one minute CRD timeout, we'll use a timeout specific to @@ -182,7 +182,7 @@ use an explicit `AreAdditionalItemsReady` func. Since this will break backwards compatibility with current `RestoreItemAction` plugins, implementation of this feature should wait until Velero plugin versioning, as described in -https://github.com/vmware-tanzu/velero/issues/3285 is +https://github.com/velero-io/velero/issues/3285 is implemented. With plugin versioning in place, existing (non-versioned or 1.0-versioned) `RestoreItemAction` plugins which do not define `AreAdditionalItemsReady` would be able to coexist with a diff --git a/design/Implemented/wildcard-namespace-support-design.md b/design/Implemented/wildcard-namespace-support-design.md index 45c4d4641..c9076e662 100644 --- a/design/Implemented/wildcard-namespace-support-design.md +++ b/design/Implemented/wildcard-namespace-support-design.md @@ -7,7 +7,7 @@ Velero currently treats namespace patterns with glob characters as literal strin ## Background -Requested in [#1874](https://github.com/vmware-tanzu/velero/issues/1874) for more flexible namespace selection. +Requested in [#1874](https://github.com/velero-io/velero/issues/1874) for more flexible namespace selection. ## Goals diff --git a/design/cli-install-changes.md b/design/cli-install-changes.md index 3464ce0e5..c9f278190 100644 --- a/design/cli-install-changes.md +++ b/design/cli-install-changes.md @@ -276,9 +276,9 @@ The value for these flags will be stored as annotations. #### Handling CA certs -In anticipation of a new configuration implementation to handle custom CA certs (as per design doc https://github.com/vmware-tanzu/velero/blob/main/design/custom-ca-support.md), a new flag `velero storage-location create/set --cacert-file mapStringString` is proposed. It sets the configuration to use for creating a secret containing a custom certificate for an S3 location of a plugin provider. Format is provider:path-to-file. +In anticipation of a new configuration implementation to handle custom CA certs (as per design doc https://github.com/velero-io/velero/blob/main/design/custom-ca-support.md), a new flag `velero storage-location create/set --cacert-file mapStringString` is proposed. It sets the configuration to use for creating a secret containing a custom certificate for an S3 location of a plugin provider. Format is provider:path-to-file. -See discussion https://github.com/vmware-tanzu/velero/pull/2259#discussion_r384700723 for more clarification. +See discussion https://github.com/velero-io/velero/pull/2259#discussion_r384700723 for more clarification. #### Renaming "provider" to "location-plugin" @@ -344,7 +344,7 @@ Another new behavior that must be added: the server needs to identify when there As it is today, a valid VSL would not be required to create backups, unless the backup included a PV. -To make it easier for the user to identify if their Velero server is ready to create backups or not, a `velero status` command should be added. This issue has been created some time ago for this purpose: https://github.com/vmware-tanzu/velero/issues/1094. +To make it easier for the user to identify if their Velero server is ready to create backups or not, a `velero status` command should be added. This issue has been created some time ago for this purpose: https://github.com/velero-io/velero/issues/1094. ## Alternatives Considered diff --git a/design/new-prepost-backuprestore-plugin-hooks.md b/design/new-prepost-backuprestore-plugin-hooks.md index 65e305147..15fd02728 100644 --- a/design/new-prepost-backuprestore-plugin-hooks.md +++ b/design/new-prepost-backuprestore-plugin-hooks.md @@ -8,7 +8,7 @@ The proposed plugin hooks are to be executed only once: pre-backup (before backu ### PreBackup and PostBackup Actions -For the backup, the sequence of events of Velero backup are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/vmware-tanzu/velero/issues/3533) ): +For the backup, the sequence of events of Velero backup are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/velero-io/velero/issues/3533) ): ``` New Backup Request @@ -40,16 +40,16 @@ New Backup Request ``` These plugin hooks will be invoked: -- PreBackupAction: plugin actions are executed after the backup object is created and validated but before the backup is being processed, more precisely _before_ function [c.backupper.Backup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L590). If the PreBackupActions return an err, the backup object is not processed and the Backup phase will be set as `FailedPreBackupActions`. +- PreBackupAction: plugin actions are executed after the backup object is created and validated but before the backup is being processed, more precisely _before_ function [c.backupper.Backup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L590). If the PreBackupActions return an err, the backup object is not processed and the Backup phase will be set as `FailedPreBackupActions`. -- PostBackupAction: plugin actions are executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). +- PostBackupAction: plugin actions are executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). The proposed plugin hooks will execute actions that will have statuses on their own: `Backup.Status.PreBackupActionsStatuses` and `Backup.Status.PostBackupActionsStatuses` which will be an array of a proposed struct `ActionStatus` with PluginName, StartTimestamp, CompletionTimestamp and Phase. ### PreRestore and PostRestore Actions -For the restore, the sequence of events of Velero restore are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/vmware-tanzu/velero/issues/3533) ): +For the restore, the sequence of events of Velero restore are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/velero-io/velero/issues/3533) ): ``` New Restore Request |--> Validation of the request @@ -84,9 +84,9 @@ New Restore Request These plugin hooks will be invoked: -- PreRestoreAction: plugin actions are executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. +- PreRestoreAction: plugin actions are executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. -- PostRestoreAction: plugin actions are executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). +- PostRestoreAction: plugin actions are executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). The proposed plugin hooks will execute actions that will have statuses on their own: `Restore.Status.PreRestoreActionsStatuses` and `Restore.Status.PostRestoreActionsStatuses` which will be an array of a proposed struct `ActionStatus` with PluginName, StartTimestamp, CompletionTimestamp and Phase. @@ -148,7 +148,7 @@ The PostBackupAction plugin API will resemble the BackupItemAction plugin design By this stage, the backup has already been executed, with items backed up and volumes snapshots processed and persisted. The `PostBackupAction` interface will only have an `Execute()` method since the plugin will be executed only once per Backup, not per item. -If there are any PostBackupAction plugins registered, they will be executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). +If there are any PostBackupAction plugins registered, they will be executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). The Velero restore controller package will be modified for `PreRestoreAction` and `PostRestoreAction`. @@ -156,13 +156,13 @@ The PreRestoreAction plugin API will resemble the RestoreItemAction plugin desig It will not receive any resource list items because the restore has not yet been running at that stage. In addition, the `PreRestoreAction` interface will only have an `Execute()` method since the plugin will be executed only once per Restore creation, not per item. -The Velero restore controller will be modified so that if there are any PreRestoreAction plugins registered, they will be executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. +The Velero restore controller will be modified so that if there are any PreRestoreAction plugins registered, they will be executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. The PostRestoreAction plugin API will resemble the RestoreItemAction plugin design, but with the fundamental difference that it will receive only as input the Velero `Restore` object without any resource list items. At this stage, the restore has already been executed. The `PostRestoreAction` interface will only have an `Execute()` method since the plugin will be executed only once per Restore, not per item. -If any PostRestoreAction plugins are registered, they will be executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). +If any PostRestoreAction plugins are registered, they will be executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). ## Detailed Design diff --git a/design/restore-progress.md b/design/restore-progress.md index d86b2cfa6..3ce38414e 100644 --- a/design/restore-progress.md +++ b/design/restore-progress.md @@ -217,4 +217,4 @@ TBD ## Open Issues -https://github.com/vmware-tanzu/velero/issues/21 \ No newline at end of file +https://github.com/velero-io/velero/issues/21 \ No newline at end of file diff --git a/go.mod b/go.mod index 25b753d8c..a4f26fd35 100644 --- a/go.mod +++ b/go.mod @@ -1,4 +1,4 @@ -module github.com/vmware-tanzu/velero +module github.com/velero-io/velero go 1.26.0 diff --git a/hack/issue-template-gen/main.go b/hack/issue-template-gen/main.go index dcdcf782e..5950f84c5 100644 --- a/hack/issue-template-gen/main.go +++ b/hack/issue-template-gen/main.go @@ -24,7 +24,7 @@ import ( "os" "text/template" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/bug" + "github.com/velero-io/velero/pkg/cmd/cli/bug" ) func main() { diff --git a/hack/release-tools/brew-update.sh b/hack/release-tools/brew-update.sh index dfb1f52be..5241340eb 100755 --- a/hack/release-tools/brew-update.sh +++ b/hack/release-tools/brew-update.sh @@ -13,7 +13,7 @@ then fi # GitHub URL which contains the source code archive for the tagged release -URL=https://github.com/vmware-tanzu/velero/archive/$VELERO_VERSION.tar.gz +URL=https://github.com/velero-io/velero/archive/$VELERO_VERSION.tar.gz # Update brew so we're sure we have the latest Velero formula brew update diff --git a/hack/release-tools/gen-docs.sh b/hack/release-tools/gen-docs.sh index 595de2ee6..956153805 100755 --- a/hack/release-tools/gen-docs.sh +++ b/hack/release-tools/gen-docs.sh @@ -100,7 +100,7 @@ rm $DATA_DOCS_DIRECTORY/$NEW_DOCS_TOC.yml && cp $DATA_DOCS_DIRECTORY/$MAIN_BRANC if [[ $(uname) == "Darwin" ]]; then echo "[OS X] updating version-specific links" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://velero.io/docs/$MAIN_BRANCH|https://velero.io/docs/$VELERO_VERSION|g" - find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://github.com/vmware-tanzu/velero/blob/$MAIN_BRANCH|https://github.com/vmware-tanzu/velero/blob/$VELERO_VERSION|g" + find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://github.com/velero-io/velero/blob/$MAIN_BRANCH|https://github.com/velero-io/velero/blob/$VELERO_VERSION|g" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "_index.md" | xargs sed -i '' "s|version: $MAIN_BRANCH|version: $NEW_DOCS_VERSION|g" echo "[OS X] Updating latest version in $CONFIG_FILE" @@ -121,7 +121,7 @@ ${NEW_DOCS_VERSION}: ${NEW_DOCS_TOC} else echo "[Linux] updating version-specific links" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://velero.io/docs/$MAIN_BRANCH|https://velero.io/docs/$VELERO_VERSION|g" - find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://github.com/vmware-tanzu/velero/blob/$MAIN_BRANCH|https://github.com/vmware-tanzu/velero/blob/$VELERO_VERSION|g" + find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://github.com/velero-io/velero/blob/$MAIN_BRANCH|https://github.com/velero-io/velero/blob/$VELERO_VERSION|g" echo "[Linux] Updating latest version in $CONFIG_FILE" sed -i'' "s/latest: ${PREVIOUS_DOCS_VERSION}/latest: ${NEW_DOCS_VERSION}/" $CONFIG_FILE diff --git a/hack/update-1fmt.sh b/hack/update-1fmt.sh index a23261cb2..002f3d27f 100755 --- a/hack/update-1fmt.sh +++ b/hack/update-1fmt.sh @@ -47,7 +47,7 @@ else fi echo "${ACTION} goimports" -output=$(goimports "${MODE}" -local github.com/vmware-tanzu/velero ${files}) +output=$(goimports "${MODE}" -local github.com/velero-io/velero ${files}) if [[ -n "${output}" ]]; then VERIFY_IMPORTS_FAILED=1 echo "${output}" diff --git a/hack/update-2proto.sh b/hack/update-2proto.sh index 07cc732f5..cd7e85cb0 100755 --- a/hack/update-2proto.sh +++ b/hack/update-2proto.sh @@ -23,7 +23,7 @@ protoc \ -I pkg/plugin/proto/ \ -I /usr/include \ --go_out=pkg/plugin/generated/ \ - --go_opt=module=github.com/vmware-tanzu/velero/pkg/plugin/generated \ + --go_opt=module=github.com/velero-io/velero/pkg/plugin/generated \ --go-grpc_out=pkg/plugin/generated \ --go-grpc_opt=paths=source_relative \ --go-grpc_opt=require_unimplemented_servers=false \ diff --git a/internal/credentials/file_store.go b/internal/credentials/file_store.go index d1f1fb10a..53d15cf68 100644 --- a/internal/credentials/file_store.go +++ b/internal/credentials/file_store.go @@ -25,8 +25,8 @@ import ( corev1api "k8s.io/api/core/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" ) // FileStore defines operations for interacting with credentials diff --git a/internal/credentials/file_store_test.go b/internal/credentials/file_store_test.go index d748ca29e..ae84bd9be 100644 --- a/internal/credentials/file_store_test.go +++ b/internal/credentials/file_store_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestNamespacedFileStore(t *testing.T) { diff --git a/internal/credentials/secret_store.go b/internal/credentials/secret_store.go index f4d2111a5..d6307f23b 100644 --- a/internal/credentials/secret_store.go +++ b/internal/credentials/secret_store.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/kube" ) // SecretStore defines operations for interacting with credentials diff --git a/internal/delete/actions/csi/volumesnapshotcontent_action.go b/internal/delete/actions/csi/volumesnapshotcontent_action.go index 9473686e0..791cdb5c3 100644 --- a/internal/delete/actions/csi/volumesnapshotcontent_action.go +++ b/internal/delete/actions/csi/volumesnapshotcontent_action.go @@ -29,10 +29,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/client" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/client" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) // volumeSnapshotContentDeleteItemAction is a restore item action plugin for Velero diff --git a/internal/delete/actions/csi/volumesnapshotcontent_action_test.go b/internal/delete/actions/csi/volumesnapshotcontent_action_test.go index e8a0b5865..c5c6fc734 100644 --- a/internal/delete/actions/csi/volumesnapshotcontent_action_test.go +++ b/internal/delete/actions/csi/volumesnapshotcontent_action_test.go @@ -32,11 +32,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) // fakeClientWithErrors wraps a real client and injects errors for specific operations. diff --git a/internal/delete/delete_item_action_handler.go b/internal/delete/delete_item_action_handler.go index ba242c0ca..2e4f7588b 100644 --- a/internal/delete/delete_item_action_handler.go +++ b/internal/delete/delete_item_action_handler.go @@ -19,7 +19,7 @@ package delete import ( "io" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -27,11 +27,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/filesystem" ) // Context provides the necessary environment to run DeleteItemAction plugins diff --git a/internal/delete/delete_item_action_handler_test.go b/internal/delete/delete_item_action_handler_test.go index 6743cd1f9..4d20fc3e0 100644 --- a/internal/delete/delete_item_action_handler_test.go +++ b/internal/delete/delete_item_action_handler_test.go @@ -29,12 +29,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) func TestInvokeDeleteItemActionsRunForCorrectItems(t *testing.T) { diff --git a/internal/hook/item_hook_handler.go b/internal/hook/item_hook_handler.go index 52dd815ab..bb0fe1c9f 100644 --- a/internal/hook/item_hook_handler.go +++ b/internal/hook/item_hook_handler.go @@ -34,13 +34,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/podexec" - "github.com/vmware-tanzu/velero/pkg/restorehelper" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/podexec" + "github.com/velero-io/velero/pkg/restorehelper" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/kube" ) type HookPhase string @@ -147,7 +147,7 @@ func (i *InitContainerRestoreHookHandler) HandleRestoreHooks( labels := labels.Set(metadata.GetLabels()) // Apply the hook according to the target namespace in which the pod will be restored - // more details see https://github.com/vmware-tanzu/velero/issues/4720 + // more details see https://github.com/velero-io/velero/issues/4720 if namespaceMapping != nil { if n, ok := namespaceMapping[namespace]; ok { namespace = n diff --git a/internal/hook/item_hook_handler_test.go b/internal/hook/item_hook_handler_test.go index 37f1500a3..747af28f7 100644 --- a/internal/hook/item_hook_handler_test.go +++ b/internal/hook/item_hook_handler_test.go @@ -32,12 +32,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" ) func TestHandleHooksSkips(t *testing.T) { diff --git a/internal/hook/wait_exec_hook_handler.go b/internal/hook/wait_exec_hook_handler.go index 92a905c8c..85c804f20 100644 --- a/internal/hook/wait_exec_hook_handler.go +++ b/internal/hook/wait_exec_hook_handler.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/tools/cache" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/podexec" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/podexec" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) type WaitExecHookHandler interface { diff --git a/internal/hook/wait_exec_hook_handler_test.go b/internal/hook/wait_exec_hook_handler_test.go index fb102b16f..bc3da65f4 100644 --- a/internal/hook/wait_exec_hook_handler_test.go +++ b/internal/hook/wait_exec_hook_handler_test.go @@ -32,10 +32,10 @@ import ( "k8s.io/client-go/tools/cache" fcache "k8s.io/client-go/tools/cache/testing" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" ) type fakeListWatchFactory struct { diff --git a/internal/resourcemodifiers/resource_modifiers.go b/internal/resourcemodifiers/resource_modifiers.go index cc780df03..8ee1e0e20 100644 --- a/internal/resourcemodifiers/resource_modifiers.go +++ b/internal/resourcemodifiers/resource_modifiers.go @@ -30,7 +30,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/yaml" - "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/collections" ) const ( diff --git a/internal/resourcepolicies/resource_policies.go b/internal/resourcepolicies/resource_policies.go index ce32dba19..e605b1e15 100644 --- a/internal/resourcepolicies/resource_policies.go +++ b/internal/resourcepolicies/resource_policies.go @@ -28,7 +28,7 @@ import ( corev1api "k8s.io/api/core/v1" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) type VolumeActionType string diff --git a/internal/restartabletest/restartable_delegate.go b/internal/restartabletest/restartable_delegate.go index 41d56cf31..0d9633b88 100644 --- a/internal/restartabletest/restartable_delegate.go +++ b/internal/restartabletest/restartable_delegate.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" ) type MockRestartableProcess struct { diff --git a/internal/storage/storagelocation.go b/internal/storage/storagelocation.go index d5fe548c0..370c85118 100644 --- a/internal/storage/storagelocation.go +++ b/internal/storage/storagelocation.go @@ -25,7 +25,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // DefaultBackupLocationInfo holds server default backup storage location information diff --git a/internal/storage/storagelocation_test.go b/internal/storage/storagelocation_test.go index 44eabff48..fad95988d 100644 --- a/internal/storage/storagelocation_test.go +++ b/internal/storage/storagelocation_test.go @@ -23,10 +23,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util" ) func TestIsReadyToValidate(t *testing.T) { diff --git a/internal/velero/images.go b/internal/velero/images.go index cefbd1441..18903e1cc 100644 --- a/internal/velero/images.go +++ b/internal/velero/images.go @@ -19,7 +19,7 @@ package velero import ( "fmt" - "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/buildinfo" ) // Use Dockerhub as the default registry if the build process didn't supply a registry diff --git a/internal/velero/images_test.go b/internal/velero/images_test.go index 5a68a4fd1..ecdf2d995 100644 --- a/internal/velero/images_test.go +++ b/internal/velero/images_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/buildinfo" ) func TestImageTag(t *testing.T) { diff --git a/internal/velero/serverstatusrequest.go b/internal/velero/serverstatusrequest.go index c9c8acc0a..f4013774a 100644 --- a/internal/velero/serverstatusrequest.go +++ b/internal/velero/serverstatusrequest.go @@ -17,9 +17,9 @@ limitations under the License. package velero import ( - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" ) type PluginLister interface { diff --git a/internal/volume/snapshotlocation.go b/internal/volume/snapshotlocation.go index ad23fa1f4..5fb52aa00 100644 --- a/internal/volume/snapshotlocation.go +++ b/internal/volume/snapshotlocation.go @@ -19,8 +19,8 @@ package volume import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // UpdateVolumeSnapshotLocationWithCredentialConfig adds the credentials file path to the config diff --git a/internal/volume/utils.go b/internal/volume/utils.go index fbb3ec67b..fd613d3f0 100644 --- a/internal/volume/utils.go +++ b/internal/volume/utils.go @@ -20,7 +20,7 @@ import ( "regexp" ) -// it has to have the same value as "github.com/vmware-tanzu/velero/pkg/restore".ItemRestoreResultCreated +// it has to have the same value as "github.com/velero-io/velero/pkg/restore".ItemRestoreResultCreated const itemRestoreResultCreated = "created" // RestoredPVCFromRestoredResourceList returns a set of PVCs that were restored from the given restoredResourceList. diff --git a/internal/volume/volumes_information.go b/internal/volume/volumes_information.go index 4d5961bdb..f3ebe0548 100644 --- a/internal/volume/volumes_information.go +++ b/internal/volume/volumes_information.go @@ -29,13 +29,13 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/label" + "github.com/velero-io/velero/pkg/label" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" ) type Method string diff --git a/internal/volume/volumes_information_test.go b/internal/volume/volumes_information_test.go index b39ba82f8..ba6143dda 100644 --- a/internal/volume/volumes_information_test.go +++ b/internal/volume/volumes_information_test.go @@ -31,14 +31,14 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/logging" ) func TestGenerateVolumeInfoForSkippedPV(t *testing.T) { diff --git a/internal/volumehelper/volume_policy_helper.go b/internal/volumehelper/volume_policy_helper.go index 339b80011..84ab0768e 100644 --- a/internal/volumehelper/volume_policy_helper.go +++ b/internal/volumehelper/volume_policy_helper.go @@ -12,13 +12,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" - vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" + "github.com/velero-io/velero/internal/resourcepolicies" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/util/boolptr" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" + vhutil "github.com/velero-io/velero/pkg/util/volumehelper" ) type volumeHelperImpl struct { diff --git a/internal/volumehelper/volume_policy_helper_test.go b/internal/volumehelper/volume_policy_helper_test.go index 5e52ae73b..979803c3f 100644 --- a/internal/volumehelper/volume_policy_helper_test.go +++ b/internal/volumehelper/volume_policy_helper_test.go @@ -29,12 +29,12 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/utils/ptr" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" + "github.com/velero-io/velero/internal/resourcepolicies" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + velerotest "github.com/velero-io/velero/pkg/test" + podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" ) func TestVolumeHelperImpl_ShouldPerformSnapshot(t *testing.T) { diff --git a/pkg/apis/velero/v1/pod_volume_backup_types.go b/pkg/apis/velero/v1/pod_volume_backup_types.go index b246906fb..2eea3b545 100644 --- a/pkg/apis/velero/v1/pod_volume_backup_types.go +++ b/pkg/apis/velero/v1/pod_volume_backup_types.go @@ -20,7 +20,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + "github.com/velero-io/velero/pkg/apis/velero/shared" ) // PodVolumeBackupSpec is the specification for a PodVolumeBackup. diff --git a/pkg/apis/velero/v1/pod_volume_restore_type.go b/pkg/apis/velero/v1/pod_volume_restore_type.go index c1d75b71c..ae84f1c5d 100644 --- a/pkg/apis/velero/v1/pod_volume_restore_type.go +++ b/pkg/apis/velero/v1/pod_volume_restore_type.go @@ -20,7 +20,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + "github.com/velero-io/velero/pkg/apis/velero/shared" ) // PodVolumeRestoreSpec is the specification for a PodVolumeRestore. diff --git a/pkg/apis/velero/v2alpha1/data_download_types.go b/pkg/apis/velero/v2alpha1/data_download_types.go index 4ea7128ec..93e194ff5 100644 --- a/pkg/apis/velero/v2alpha1/data_download_types.go +++ b/pkg/apis/velero/v2alpha1/data_download_types.go @@ -19,7 +19,7 @@ package v2alpha1 import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + "github.com/velero-io/velero/pkg/apis/velero/shared" ) // DataDownloadSpec is the specification for a DataDownload. diff --git a/pkg/apis/velero/v2alpha1/data_upload_types.go b/pkg/apis/velero/v2alpha1/data_upload_types.go index 751da4555..b40475c1b 100644 --- a/pkg/apis/velero/v2alpha1/data_upload_types.go +++ b/pkg/apis/velero/v2alpha1/data_upload_types.go @@ -19,7 +19,7 @@ package v2alpha1 import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + "github.com/velero-io/velero/pkg/apis/velero/shared" ) // DataUploadSpec is the specification for a DataUpload. diff --git a/pkg/archive/extractor.go b/pkg/archive/extractor.go index aae9a7a85..42c65be39 100644 --- a/pkg/archive/extractor.go +++ b/pkg/archive/extractor.go @@ -26,7 +26,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/filesystem" ) // Extractor unzips/extracts a backup tarball to a local diff --git a/pkg/archive/extractor_test.go b/pkg/archive/extractor_test.go index a4daf02ca..dde69d4aa 100644 --- a/pkg/archive/extractor_test.go +++ b/pkg/archive/extractor_test.go @@ -26,8 +26,8 @@ import ( "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/filesystem" ) func TestUnzipAndExtractBackup(t *testing.T) { diff --git a/pkg/archive/filesystem.go b/pkg/archive/filesystem.go index 73b0d1dcf..c3a196930 100644 --- a/pkg/archive/filesystem.go +++ b/pkg/archive/filesystem.go @@ -22,8 +22,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/filesystem" ) // GetItemFilePath returns an item's file path once extracted from a Velero backup archive. diff --git a/pkg/archive/filesystem_test.go b/pkg/archive/filesystem_test.go index bf7f16c76..08e526466 100644 --- a/pkg/archive/filesystem_test.go +++ b/pkg/archive/filesystem_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/test" ) func TestGetItemFilePath(t *testing.T) { diff --git a/pkg/archive/parser.go b/pkg/archive/parser.go index 166e03114..4f682d333 100644 --- a/pkg/archive/parser.go +++ b/pkg/archive/parser.go @@ -25,8 +25,8 @@ import ( "github.com/sirupsen/logrus" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/filesystem" ) var ErrNotExist = errors.New("does not exist") diff --git a/pkg/archive/parser_test.go b/pkg/archive/parser_test.go index 1af8077e8..3ea837bb5 100644 --- a/pkg/archive/parser_test.go +++ b/pkg/archive/parser_test.go @@ -24,7 +24,7 @@ import ( "github.com/stretchr/testify/require" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/test" ) func TestParse(t *testing.T) { diff --git a/pkg/backup/actions/backup_pv_action.go b/pkg/backup/actions/backup_pv_action.go index c3f378fac..b1c9a4826 100644 --- a/pkg/backup/actions/backup_pv_action.go +++ b/pkg/backup/actions/backup_pv_action.go @@ -25,9 +25,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) // PVCAction inspects a PersistentVolumeClaim for the PersistentVolume diff --git a/pkg/backup/actions/backup_pv_action_test.go b/pkg/backup/actions/backup_pv_action_test.go index 41af9e9bf..5b0fc3a47 100644 --- a/pkg/backup/actions/backup_pv_action_test.go +++ b/pkg/backup/actions/backup_pv_action_test.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBackupPVAction(t *testing.T) { diff --git a/pkg/backup/actions/csi/pvc_action.go b/pkg/backup/actions/csi/pvc_action.go index 7f5fd2afa..fa6414f39 100644 --- a/pkg/backup/actions/csi/pvc_action.go +++ b/pkg/backup/actions/csi/pvc_action.go @@ -44,21 +44,21 @@ import ( "k8s.io/apimachinery/pkg/api/resource" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/label" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/utils/volumehelper" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - uploaderUtil "github.com/vmware-tanzu/velero/pkg/uploader/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" - vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + veleroclient "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/label" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/utils/volumehelper" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + uploaderUtil "github.com/velero-io/velero/pkg/uploader/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" + vhutil "github.com/velero-io/velero/pkg/util/volumehelper" ) // TODO: Replace hardcoded VolumeSnapshot finalizer strings with constants from diff --git a/pkg/backup/actions/csi/pvc_action_test.go b/pkg/backup/actions/csi/pvc_action_test.go index 629c5e9cd..9d9818571 100644 --- a/pkg/backup/actions/csi/pvc_action_test.go +++ b/pkg/backup/actions/csi/pvc_action_test.go @@ -23,7 +23,7 @@ import ( "testing" "time" - "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/kuberesource" volumegroupsnapshotv1beta2 "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumegroupsnapshot/v1beta2" "github.com/stretchr/testify/assert" @@ -31,7 +31,7 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/utils/pointer" - "github.com/vmware-tanzu/velero/pkg/label" + "github.com/velero-io/velero/pkg/label" "github.com/google/go-cmp/cmp" "github.com/google/go-cmp/cmp/cmpopts" @@ -50,13 +50,13 @@ import ( "k8s.io/apimachinery/pkg/util/wait" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) const testDriver = "csi.example.com" diff --git a/pkg/backup/actions/csi/volumesnapshot_action.go b/pkg/backup/actions/csi/volumesnapshot_action.go index 0e0e9a840..5eefde544 100644 --- a/pkg/backup/actions/csi/volumesnapshot_action.go +++ b/pkg/backup/actions/csi/volumesnapshot_action.go @@ -30,16 +30,16 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/label" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/label" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) // volumeSnapshotBackupItemAction is a backup item action plugin to backup diff --git a/pkg/backup/actions/csi/volumesnapshot_action_test.go b/pkg/backup/actions/csi/volumesnapshot_action_test.go index 1db5cd475..1684c2371 100644 --- a/pkg/backup/actions/csi/volumesnapshot_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshot_action_test.go @@ -28,12 +28,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestVSExecute(t *testing.T) { diff --git a/pkg/backup/actions/csi/volumesnapshotclass_action.go b/pkg/backup/actions/csi/volumesnapshotclass_action.go index 8200b465f..b54a59271 100644 --- a/pkg/backup/actions/csi/volumesnapshotclass_action.go +++ b/pkg/backup/actions/csi/volumesnapshotclass_action.go @@ -24,11 +24,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + csiutil "github.com/velero-io/velero/pkg/util/csi" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) // volumeSnapshotClassBackupItemAction is a backup item action plugin to diff --git a/pkg/backup/actions/csi/volumesnapshotclass_action_test.go b/pkg/backup/actions/csi/volumesnapshotclass_action_test.go index 3bd90a8aa..92999361a 100644 --- a/pkg/backup/actions/csi/volumesnapshotclass_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshotclass_action_test.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) func TestVSClassExecute(t *testing.T) { diff --git a/pkg/backup/actions/csi/volumesnapshotcontent_action.go b/pkg/backup/actions/csi/volumesnapshotcontent_action.go index d4cd6d46c..e0e2d9d32 100644 --- a/pkg/backup/actions/csi/volumesnapshotcontent_action.go +++ b/pkg/backup/actions/csi/volumesnapshotcontent_action.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + csiutil "github.com/velero-io/velero/pkg/util/csi" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) // volumeSnapshotContentBackupItemAction is a backup item action plugin to backup diff --git a/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go b/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go index e24623d9a..f858d6054 100644 --- a/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestVSCExecute(t *testing.T) { diff --git a/pkg/backup/actions/pod_action.go b/pkg/backup/actions/pod_action.go index 8ed5e3b44..8a2c81018 100644 --- a/pkg/backup/actions/pod_action.go +++ b/pkg/backup/actions/pod_action.go @@ -22,9 +22,9 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) // PodAction implements ItemAction. diff --git a/pkg/backup/actions/pod_action_test.go b/pkg/backup/actions/pod_action_test.go index d0d30b653..a363043ec 100644 --- a/pkg/backup/actions/pod_action_test.go +++ b/pkg/backup/actions/pod_action_test.go @@ -23,9 +23,9 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestPodActionAppliesTo(t *testing.T) { diff --git a/pkg/backup/actions/remap_crd_version_action.go b/pkg/backup/actions/remap_crd_version_action.go index 3f8c2f79d..c7ad51bdc 100644 --- a/pkg/backup/actions/remap_crd_version_action.go +++ b/pkg/backup/actions/remap_crd_version_action.go @@ -30,10 +30,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // RemapCRDVersionAction inspects CustomResourceDefinition and decides if it is a v1 diff --git a/pkg/backup/actions/remap_crd_version_action_test.go b/pkg/backup/actions/remap_crd_version_action_test.go index 8f21fb151..4eb03f5bd 100644 --- a/pkg/backup/actions/remap_crd_version_action_test.go +++ b/pkg/backup/actions/remap_crd_version_action_test.go @@ -31,11 +31,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestRemapCRDVersionAction(t *testing.T) { diff --git a/pkg/backup/actions/service_account_action.go b/pkg/backup/actions/service_account_action.go index b563f7a03..810de51c1 100644 --- a/pkg/backup/actions/service_account_action.go +++ b/pkg/backup/actions/service_account_action.go @@ -22,10 +22,10 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) // ServiceAccountAction implements ItemAction. diff --git a/pkg/backup/actions/service_account_action_test.go b/pkg/backup/actions/service_account_action_test.go index 90d09005b..c5164d40b 100644 --- a/pkg/backup/actions/service_account_action_test.go +++ b/pkg/backup/actions/service_account_action_test.go @@ -28,10 +28,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) func newV1ClusterRoleBindingList(rbacCRBList []rbacv1.ClusterRoleBinding) []actionhelpers.ClusterRoleBinding { diff --git a/pkg/backup/backup.go b/pkg/backup/backup.go index 9edaf6a85..0c75cf447 100644 --- a/pkg/backup/backup.go +++ b/pkg/backup/backup.go @@ -42,28 +42,28 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/volume" - "github.com/vmware-tanzu/velero/internal/volumehelper" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/itemblock" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podexec" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/volume" + "github.com/velero-io/velero/internal/volumehelper" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/itemblock" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podexec" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/kube" ) // BackupVersion is the current backup major version for Velero. @@ -327,7 +327,7 @@ func (kb *kubernetesBackupper) BackupWithResolvers( // check if there are any namespaces included in the backup which are managed by argoCD // We will check for the existence of a ArgoCD label in the includedNamespaces and add a warning // so that users are at least aware about the existence of argoCD managed ns in their backup - // Related Issue: https://github.com/vmware-tanzu/velero/issues/7905 + // Related Issue: https://github.com/velero-io/velero/issues/7905 if len(nsManagedByArgoCD) > 0 { log.Warnf("backup operation may encounter complications and potentially produce undesirable results due to the inclusion of namespaces %v managed by ArgoCD in the backup.", nsManagedByArgoCD) } diff --git a/pkg/backup/backup_test.go b/pkg/backup/backup_test.go index f9351245c..c4215eaf9 100644 --- a/pkg/backup/backup_test.go +++ b/pkg/backup/backup_test.go @@ -41,26 +41,26 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/internal/volume" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/persistence" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/test" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/volume" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/persistence" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/test" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) func TestBackedUpItemsMatchesTarballContents(t *testing.T) { @@ -1180,7 +1180,7 @@ func TestBackupResourceCohabitation(t *testing.T) { // TestBackupUsesNewCohabitatingResourcesForEachBackup ensures that when two backups are // run that each include cohabiting resources, one copy of the relevant resources is // backed up in each backup. Verification is done by looking at the contents of the backup -// tarball. This covers a specific issue that was fixed by https://github.com/vmware-tanzu/velero/pull/485. +// tarball. This covers a specific issue that was fixed by https://github.com/velero-io/velero/pull/485. func TestBackupUsesNewCohabitatingResourcesForEachBackup(t *testing.T) { h := newHarness(t, nil) defer h.itemBlockPool.Stop() diff --git a/pkg/backup/delete_helpers.go b/pkg/backup/delete_helpers.go index fa4cbb744..4641ed597 100644 --- a/pkg/backup/delete_helpers.go +++ b/pkg/backup/delete_helpers.go @@ -21,8 +21,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/label" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/label" ) // NewDeleteBackupRequest creates a DeleteBackupRequest for the backup identified by name and uid. diff --git a/pkg/backup/item_backupper.go b/pkg/backup/item_backupper.go index 2ca266e91..9a5476cd9 100644 --- a/pkg/backup/item_backupper.go +++ b/pkg/backup/item_backupper.go @@ -37,23 +37,23 @@ import ( "k8s.io/apimachinery/pkg/util/sets" kbClient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemblock" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" - "github.com/vmware-tanzu/velero/pkg/util/volumehelper" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemblock" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/util/boolptr" + csiutil "github.com/velero-io/velero/pkg/util/csi" + "github.com/velero-io/velero/pkg/util/volumehelper" ) const ( diff --git a/pkg/backup/item_backupper_test.go b/pkg/backup/item_backupper_test.go index be91b6d34..0e56e5aca 100644 --- a/pkg/backup/item_backupper_test.go +++ b/pkg/backup/item_backupper_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" ctrlfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/pkg/kuberesource" "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" @@ -34,7 +34,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/velero-io/velero/pkg/builder" ) func Test_resourceKey(t *testing.T) { diff --git a/pkg/backup/item_collector.go b/pkg/backup/item_collector.go index 3dace71fd..17b71a8c1 100644 --- a/pkg/backup/item_collector.go +++ b/pkg/backup/item_collector.go @@ -35,11 +35,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/client-go/tools/pager" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/collections" ) // itemCollector collects items from the Kubernetes API according to @@ -150,7 +150,7 @@ func (nt *nsTracker) init( // Skip the backup when the backup's namespace filter has // default value, and the namespace doesn't match backup // LabelSelector and OrLabelSelector. - // https://github.com/vmware-tanzu/velero/issues/7105 + // https://github.com/velero-io/velero/issues/7105 if nt.namespaceFilter.IncludeEverything() && (nt.singleLabelSelector != nil || len(nt.orLabelSelector) > 0) { continue diff --git a/pkg/backup/item_collector_test.go b/pkg/backup/item_collector_test.go index 54e2ed4c3..2349994ee 100644 --- a/pkg/backup/item_collector_test.go +++ b/pkg/backup/item_collector_test.go @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/collections" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/collections" ) func TestSortCoreGroup(t *testing.T) { diff --git a/pkg/backup/itemblock.go b/pkg/backup/itemblock.go index dee553f72..81febefd4 100644 --- a/pkg/backup/itemblock.go +++ b/pkg/backup/itemblock.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/pkg/itemblock" + "github.com/velero-io/velero/pkg/itemblock" ) type BackupItemBlock struct { diff --git a/pkg/backup/request.go b/pkg/backup/request.go index ca2e638c2..eb712387e 100644 --- a/pkg/backup/request.go +++ b/pkg/backup/request.go @@ -22,13 +22,13 @@ import ( "github.com/gobwas/glob" "k8s.io/apimachinery/pkg/labels" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/util/collections" ) type itemKey struct { diff --git a/pkg/backup/snapshots.go b/pkg/backup/snapshots.go index c77e1cd6e..a06e74413 100644 --- a/pkg/backup/snapshots.go +++ b/pkg/backup/snapshots.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/util/sets" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/util/boolptr" ) // GetBackupCSIResources is used to get CSI snapshot related resources. diff --git a/pkg/backup/volume_snapshotter_cache.go b/pkg/backup/volume_snapshotter_cache.go index 620ebc337..0c72a03f2 100644 --- a/pkg/backup/volume_snapshotter_cache.go +++ b/pkg/backup/volume_snapshotter_cache.go @@ -3,8 +3,8 @@ package backup import ( "sync" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" ) type VolumeSnapshotterCache struct { diff --git a/pkg/builder/backup_builder.go b/pkg/builder/backup_builder.go index d5b955e43..a5e368c1b 100644 --- a/pkg/builder/backup_builder.go +++ b/pkg/builder/backup_builder.go @@ -23,13 +23,13 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/internal/resourcepolicies" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/logging" ) /* diff --git a/pkg/builder/backup_storage_location_builder.go b/pkg/builder/backup_storage_location_builder.go index 33becd2a7..d1d5ef25a 100644 --- a/pkg/builder/backup_storage_location_builder.go +++ b/pkg/builder/backup_storage_location_builder.go @@ -22,7 +22,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // BackupStorageLocationBuilder builds BackupStorageLocation objects. diff --git a/pkg/builder/container_builder.go b/pkg/builder/container_builder.go index 762462c86..64275cc7c 100644 --- a/pkg/builder/container_builder.go +++ b/pkg/builder/container_builder.go @@ -23,7 +23,7 @@ import ( corev1api "k8s.io/api/core/v1" apimachineryRuntime "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/label" + "github.com/velero-io/velero/pkg/label" ) // ContainerBuilder builds Container objects diff --git a/pkg/builder/container_builder_test.go b/pkg/builder/container_builder_test.go index b23cbddfd..b8f57eb15 100644 --- a/pkg/builder/container_builder_test.go +++ b/pkg/builder/container_builder_test.go @@ -89,8 +89,8 @@ func TestGetName(t *testing.T) { }, { name: "pull by digest", - image: "quay.io/vmware-tanzu/velero@sha256:a75f9e8c3ced3943515f249597be389f8233e1258d289b11184796edceaa7dab", - expected: "vmware-tanzu-velero", + image: "quay.io/velero-io/velero@sha256:a75f9e8c3ced3943515f249597be389f8233e1258d289b11184796edceaa7dab", + expected: "velero-io-velero", }, } diff --git a/pkg/builder/data_download_builder.go b/pkg/builder/data_download_builder.go index 20cea868f..f219275cb 100644 --- a/pkg/builder/data_download_builder.go +++ b/pkg/builder/data_download_builder.go @@ -19,8 +19,8 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) // DataDownloadBuilder builds DataDownload objects. diff --git a/pkg/builder/data_upload_builder.go b/pkg/builder/data_upload_builder.go index c8fa34956..0ef01f66d 100644 --- a/pkg/builder/data_upload_builder.go +++ b/pkg/builder/data_upload_builder.go @@ -19,8 +19,8 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) // DataUploadBuilder builds DataUpload objects diff --git a/pkg/builder/delete_backup_request_builder.go b/pkg/builder/delete_backup_request_builder.go index c0dfdbdbf..aa3fd1f9c 100644 --- a/pkg/builder/delete_backup_request_builder.go +++ b/pkg/builder/delete_backup_request_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // DeleteBackupRequestBuilder builds DeleteBackupRequest objects diff --git a/pkg/builder/download_request_builder.go b/pkg/builder/download_request_builder.go index 05d5c0daa..cca81db11 100644 --- a/pkg/builder/download_request_builder.go +++ b/pkg/builder/download_request_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // DownloadRequestBuilder builds DownloadRequest objects. diff --git a/pkg/builder/item_operation_builder.go b/pkg/builder/item_operation_builder.go index 210752b82..b76de79b2 100644 --- a/pkg/builder/item_operation_builder.go +++ b/pkg/builder/item_operation_builder.go @@ -22,8 +22,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/plugin/velero" ) // OperationStatusBuilder builds OperationStatus objects diff --git a/pkg/builder/pod_volume_backup_builder.go b/pkg/builder/pod_volume_backup_builder.go index 9db8beacd..dbcc72c9a 100644 --- a/pkg/builder/pod_volume_backup_builder.go +++ b/pkg/builder/pod_volume_backup_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // PodVolumeBackupBuilder builds PodVolumeBackup objects diff --git a/pkg/builder/pod_volume_restore_builder.go b/pkg/builder/pod_volume_restore_builder.go index 50f277eac..02108cb4a 100644 --- a/pkg/builder/pod_volume_restore_builder.go +++ b/pkg/builder/pod_volume_restore_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // PodVolumeRestoreBuilder builds PodVolumeRestore objects. diff --git a/pkg/builder/restore_builder.go b/pkg/builder/restore_builder.go index bad4327e9..168136552 100644 --- a/pkg/builder/restore_builder.go +++ b/pkg/builder/restore_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // RestoreBuilder builds Restore objects. diff --git a/pkg/builder/schedule_builder.go b/pkg/builder/schedule_builder.go index 7c9a9b1d9..ef9e03a1a 100644 --- a/pkg/builder/schedule_builder.go +++ b/pkg/builder/schedule_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // ScheduleBuilder builds Schedule objects. diff --git a/pkg/builder/server_status_request_builder.go b/pkg/builder/server_status_request_builder.go index bc8876718..80fc8078c 100644 --- a/pkg/builder/server_status_request_builder.go +++ b/pkg/builder/server_status_request_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // ServerStatusRequestBuilder builds ServerStatusRequest objects. diff --git a/pkg/builder/testcr_builder.go b/pkg/builder/testcr_builder.go index 85bc83b1c..02da95b73 100644 --- a/pkg/builder/testcr_builder.go +++ b/pkg/builder/testcr_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // CustomResourceBuilder builds objects based on velero APIVersion CRDs. diff --git a/pkg/builder/volume_snapshot_location_builder.go b/pkg/builder/volume_snapshot_location_builder.go index af94471e3..848dff401 100644 --- a/pkg/builder/volume_snapshot_location_builder.go +++ b/pkg/builder/volume_snapshot_location_builder.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // VolumeSnapshotLocationBuilder builds VolumeSnapshotLocation objects. diff --git a/pkg/cbtservice/mocks/Service.go b/pkg/cbtservice/mocks/Service.go index f7a9567a8..68016f393 100644 --- a/pkg/cbtservice/mocks/Service.go +++ b/pkg/cbtservice/mocks/Service.go @@ -8,7 +8,7 @@ import ( "context" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/cbtservice" + "github.com/velero-io/velero/pkg/cbtservice" ) // NewService creates a new instance of Service. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/client/client.go b/pkg/client/client.go index dccdc05fc..f37091b03 100644 --- a/pkg/client/client.go +++ b/pkg/client/client.go @@ -24,7 +24,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/clientcmd" - "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/buildinfo" ) // Config returns a *rest.Config, using either the kubeconfig (if specified) or an in-cluster diff --git a/pkg/client/factory.go b/pkg/client/factory.go index 51dfb62c3..0590dff02 100644 --- a/pkg/client/factory.go +++ b/pkg/client/factory.go @@ -35,8 +35,8 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/rest" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) //go:generate mockery --name Factory diff --git a/pkg/cmd/cli/backup/backup.go b/pkg/cmd/cli/backup/backup.go index 34a0f9e97..147336bec 100644 --- a/pkg/cmd/cli/backup/backup.go +++ b/pkg/cmd/cli/backup/backup.go @@ -19,7 +19,7 @@ package backup import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backup/backup_test.go b/pkg/cmd/cli/backup/backup_test.go index 0c316ca8c..1b8e8ecf7 100644 --- a/pkg/cmd/cli/backup/backup_test.go +++ b/pkg/cmd/cli/backup/backup_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" ) func TestNewBackupCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/create.go b/pkg/cmd/cli/backup/create.go index 31564aae8..c15a95cc9 100644 --- a/pkg/cmd/cli/backup/create.go +++ b/pkg/cmd/cli/backup/create.go @@ -28,14 +28,14 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/kube" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/create_test.go b/pkg/cmd/cli/backup/create_test.go index c8fd15baa..5709e912e 100644 --- a/pkg/cmd/cli/backup/create_test.go +++ b/pkg/cmd/cli/backup/create_test.go @@ -33,12 +33,12 @@ import ( controllerclient "sigs.k8s.io/controller-runtime/pkg/client" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - "github.com/vmware-tanzu/velero/pkg/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + "github.com/velero-io/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestCreateOptions_BuildBackup(t *testing.T) { diff --git a/pkg/cmd/cli/backup/delete.go b/pkg/cmd/cli/backup/delete.go index 692b82dbf..afacf53f8 100644 --- a/pkg/cmd/cli/backup/delete.go +++ b/pkg/cmd/cli/backup/delete.go @@ -27,13 +27,13 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" - "github.com/vmware-tanzu/velero/pkg/label" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" + "github.com/velero-io/velero/pkg/cmd/util/confirm" + "github.com/velero-io/velero/pkg/label" ) // NewDeleteCommand creates a new command that deletes a backup. diff --git a/pkg/cmd/cli/backup/delete_test.go b/pkg/cmd/cli/backup/delete_test.go index 3278e8153..a0954127f 100644 --- a/pkg/cmd/cli/backup/delete_test.go +++ b/pkg/cmd/cli/backup/delete_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/cmd/cli" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/describe.go b/pkg/cmd/cli/backup/describe.go index b0ef4a93e..35b910085 100644 --- a/pkg/cmd/cli/backup/describe.go +++ b/pkg/cmd/cli/backup/describe.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" - "github.com/vmware-tanzu/velero/pkg/label" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/label" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/describe_test.go b/pkg/cmd/cli/backup/describe_test.go index 5d5486473..9a22d6da7 100644 --- a/pkg/cmd/cli/backup/describe_test.go +++ b/pkg/cmd/cli/backup/describe_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/client-go/rest" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewDescribeCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/download.go b/pkg/cmd/cli/backup/download.go index 8bb973ff0..2c2d1b0cc 100644 --- a/pkg/cmd/cli/backup/download.go +++ b/pkg/cmd/cli/backup/download.go @@ -28,11 +28,11 @@ import ( "github.com/spf13/pflag" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" ) func NewDownloadCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backup/download_test.go b/pkg/cmd/cli/backup/download_test.go index 999799ff3..921cc9174 100644 --- a/pkg/cmd/cli/backup/download_test.go +++ b/pkg/cmd/cli/backup/download_test.go @@ -27,11 +27,11 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewDownloadCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/get.go b/pkg/cmd/cli/backup/get.go index 159fac30d..81a6d3028 100644 --- a/pkg/cmd/cli/backup/get.go +++ b/pkg/cmd/cli/backup/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/get_test.go b/pkg/cmd/cli/backup/get_test.go index 28c41a6de..c0d587eb0 100644 --- a/pkg/cmd/cli/backup/get_test.go +++ b/pkg/cmd/cli/backup/get_test.go @@ -27,11 +27,11 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/logs.go b/pkg/cmd/cli/backup/logs.go index a0149acf1..62ec71942 100644 --- a/pkg/cmd/cli/backup/logs.go +++ b/pkg/cmd/cli/backup/logs.go @@ -27,11 +27,11 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" ) type LogsOptions struct { diff --git a/pkg/cmd/cli/backup/logs_test.go b/pkg/cmd/cli/backup/logs_test.go index 87e100732..598ca06f4 100644 --- a/pkg/cmd/cli/backup/logs_test.go +++ b/pkg/cmd/cli/backup/logs_test.go @@ -33,12 +33,12 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestNewLogsCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/backup_location.go b/pkg/cmd/cli/backuplocation/backup_location.go index f008b2a1e..3b8d28fb0 100644 --- a/pkg/cmd/cli/backuplocation/backup_location.go +++ b/pkg/cmd/cli/backuplocation/backup_location.go @@ -19,7 +19,7 @@ package backuplocation import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/backup_location_test.go b/pkg/cmd/cli/backuplocation/backup_location_test.go index 7fc73d63d..735cbbfd3 100644 --- a/pkg/cmd/cli/backuplocation/backup_location_test.go +++ b/pkg/cmd/cli/backuplocation/backup_location_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" ) func TestNewCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/create.go b/pkg/cmd/cli/backuplocation/create.go index 343bc790a..191bc64d0 100644 --- a/pkg/cmd/cli/backuplocation/create.go +++ b/pkg/cmd/cli/backuplocation/create.go @@ -31,13 +31,13 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/internal/storage" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/create_test.go b/pkg/cmd/cli/backuplocation/create_test.go index 25d5b2cd6..aa0f88f9e 100644 --- a/pkg/cmd/cli/backuplocation/create_test.go +++ b/pkg/cmd/cli/backuplocation/create_test.go @@ -30,9 +30,9 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBuildBackupStorageLocationSetsNamespace(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/delete.go b/pkg/cmd/cli/backuplocation/delete.go index f2c3bcc3d..4ffde572c 100644 --- a/pkg/cmd/cli/backuplocation/delete.go +++ b/pkg/cmd/cli/backuplocation/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" + "github.com/velero-io/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting backup-locations. diff --git a/pkg/cmd/cli/backuplocation/delete_test.go b/pkg/cmd/cli/backuplocation/delete_test.go index 70ff7568b..9c524e1a3 100644 --- a/pkg/cmd/cli/backuplocation/delete_test.go +++ b/pkg/cmd/cli/backuplocation/delete_test.go @@ -27,12 +27,12 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/cmd/cli" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/get.go b/pkg/cmd/cli/backuplocation/get.go index fd7c057c2..58090212f 100644 --- a/pkg/cmd/cli/backuplocation/get.go +++ b/pkg/cmd/cli/backuplocation/get.go @@ -24,10 +24,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/get_test.go b/pkg/cmd/cli/backuplocation/get_test.go index d45231fce..6887a674e 100644 --- a/pkg/cmd/cli/backuplocation/get_test.go +++ b/pkg/cmd/cli/backuplocation/get_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/set.go b/pkg/cmd/cli/backuplocation/set.go index 8aa018e29..1ece5ff82 100644 --- a/pkg/cmd/cli/backuplocation/set.go +++ b/pkg/cmd/cli/backuplocation/set.go @@ -28,13 +28,13 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/internal/storage" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/util/boolptr" ) func NewSetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/set_test.go b/pkg/cmd/cli/backuplocation/set_test.go index 0ebf8a8d3..efd24c7f1 100644 --- a/pkg/cmd/cli/backuplocation/set_test.go +++ b/pkg/cmd/cli/backuplocation/set_test.go @@ -28,12 +28,12 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewSetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/bug/bug.go b/pkg/cmd/cli/bug/bug.go index 33fbb38b7..54836a3b6 100644 --- a/pkg/cmd/cli/bug/bug.go +++ b/pkg/cmd/cli/bug/bug.go @@ -31,16 +31,16 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/features" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/features" ) const ( // kubectlTimeout is how long we wait in seconds for `kubectl version` // before killing the process kubectlTimeout = 5 * time.Second - issueURL = "https://github.com/vmware-tanzu/velero/issues/new" + issueURL = "https://github.com/velero-io/velero/issues/new" // IssueTemplate is used to generate .github/ISSUE_TEMPLATE/bug_report.md // as well as the initial text that's place in a new Github issue as // the result of running `velero bug`. @@ -95,7 +95,7 @@ Please provide the output of the following commands (Pasting long output into a **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "I would like to see this bug fixed as soon as possible" diff --git a/pkg/cmd/cli/client/client.go b/pkg/cmd/cli/client/client.go index 5d0650b10..75f996c6a 100644 --- a/pkg/cmd/cli/client/client.go +++ b/pkg/cmd/cli/client/client.go @@ -19,7 +19,7 @@ package client import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/client/config" + "github.com/velero-io/velero/pkg/cmd/cli/client/config" ) func NewCommand() *cobra.Command { diff --git a/pkg/cmd/cli/client/config/get.go b/pkg/cmd/cli/client/config/get.go index f69a8cadf..a1c70382b 100644 --- a/pkg/cmd/cli/client/config/get.go +++ b/pkg/cmd/cli/client/config/get.go @@ -22,8 +22,8 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" ) func NewGetCommand() *cobra.Command { diff --git a/pkg/cmd/cli/client/config/set.go b/pkg/cmd/cli/client/config/set.go index 229ca1553..afcb34c96 100644 --- a/pkg/cmd/cli/client/config/set.go +++ b/pkg/cmd/cli/client/config/set.go @@ -23,8 +23,8 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" ) func NewSetCommand() *cobra.Command { diff --git a/pkg/cmd/cli/create/create.go b/pkg/cmd/cli/create/create.go index e158d1560..07ed10eef 100644 --- a/pkg/cmd/cli/create/create.go +++ b/pkg/cmd/cli/create/create.go @@ -19,12 +19,12 @@ package create import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" + "github.com/velero-io/velero/pkg/cmd/cli/restore" + "github.com/velero-io/velero/pkg/cmd/cli/schedule" + "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/datamover/backup.go b/pkg/cmd/cli/datamover/backup.go index 2b647bb24..8b266bc0a 100644 --- a/pkg/cmd/cli/datamover/backup.go +++ b/pkg/cmd/cli/datamover/backup.go @@ -30,22 +30,22 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/klog/v2" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/datamover" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/datamover" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/datamover/backup_test.go b/pkg/cmd/cli/datamover/backup_test.go index 2dd1e681d..fc91f3910 100644 --- a/pkg/cmd/cli/datamover/backup_test.go +++ b/pkg/cmd/cli/datamover/backup_test.go @@ -24,10 +24,10 @@ import ( "github.com/stretchr/testify/mock" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/internal/credentials" + cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/filesystem" ) func fakeCreateDataPathServiceWithErr(_ *dataMoverBackup) (dataPathService, error) { diff --git a/pkg/cmd/cli/datamover/data_mover.go b/pkg/cmd/cli/datamover/data_mover.go index 265d57bd8..e56bdb6b6 100644 --- a/pkg/cmd/cli/datamover/data_mover.go +++ b/pkg/cmd/cli/datamover/data_mover.go @@ -18,7 +18,7 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/datamover/restore.go b/pkg/cmd/cli/datamover/restore.go index b2efdbc34..d6091c9f1 100644 --- a/pkg/cmd/cli/datamover/restore.go +++ b/pkg/cmd/cli/datamover/restore.go @@ -31,19 +31,19 @@ import ( "k8s.io/klog/v2" ctrl "sigs.k8s.io/controller-runtime" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/datamover" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/datamover" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/datamover/restore_test.go b/pkg/cmd/cli/datamover/restore_test.go index 664c2bdbc..8fbc44fec 100644 --- a/pkg/cmd/cli/datamover/restore_test.go +++ b/pkg/cmd/cli/datamover/restore_test.go @@ -20,8 +20,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) func fakeCreateDataPathRestoreWithErr(_ *dataMoverRestore) (dataPathService, error) { diff --git a/pkg/cmd/cli/debug/debug.go b/pkg/cmd/cli/debug/debug.go index 400eddde1..a2f92a313 100644 --- a/pkg/cmd/cli/debug/debug.go +++ b/pkg/cmd/cli/debug/debug.go @@ -35,9 +35,9 @@ import ( "k8s.io/client-go/tools/clientcmd" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" ) //go:embed cshd-scripts/velero.cshd diff --git a/pkg/cmd/cli/delete/delete.go b/pkg/cmd/cli/delete/delete.go index 1eb910307..389247a59 100644 --- a/pkg/cmd/cli/delete/delete.go +++ b/pkg/cmd/cli/delete/delete.go @@ -19,11 +19,11 @@ package delete import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" + "github.com/velero-io/velero/pkg/cmd/cli/restore" + "github.com/velero-io/velero/pkg/cmd/cli/schedule" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/delete_options.go b/pkg/cmd/cli/delete_options.go index 78c7ae337..b6b923945 100644 --- a/pkg/cmd/cli/delete_options.go +++ b/pkg/cmd/cli/delete_options.go @@ -23,8 +23,8 @@ import ( "github.com/spf13/pflag" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/util/confirm" ) // DeleteOptions contains parameters used for deleting a restore. diff --git a/pkg/cmd/cli/describe/describe.go b/pkg/cmd/cli/describe/describe.go index 9f45260fa..b7c93d78f 100644 --- a/pkg/cmd/cli/describe/describe.go +++ b/pkg/cmd/cli/describe/describe.go @@ -19,10 +19,10 @@ package describe import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/cli/restore" + "github.com/velero-io/velero/pkg/cmd/cli/schedule" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/get/get.go b/pkg/cmd/cli/get/get.go index 24ad16afb..e12abe08c 100644 --- a/pkg/cmd/cli/get/get.go +++ b/pkg/cmd/cli/get/get.go @@ -19,13 +19,13 @@ package get import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/plugin" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" + "github.com/velero-io/velero/pkg/cmd/cli/plugin" + "github.com/velero-io/velero/pkg/cmd/cli/restore" + "github.com/velero-io/velero/pkg/cmd/cli/schedule" + "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/install/install.go b/pkg/cmd/cli/install/install.go index 8115e1353..01ef58f75 100644 --- a/pkg/cmd/cli/install/install.go +++ b/pkg/cmd/cli/install/install.go @@ -28,16 +28,16 @@ import ( "github.com/spf13/pflag" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/velero" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" - "github.com/vmware-tanzu/velero/pkg/install" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/install" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) // Options collects all the options for installing Velero into a Kubernetes cluster. diff --git a/pkg/cmd/cli/install/install_test.go b/pkg/cmd/cli/install/install_test.go index 1e0e7a4cf..2a0572db2 100644 --- a/pkg/cmd/cli/install/install_test.go +++ b/pkg/cmd/cli/install/install_test.go @@ -27,8 +27,8 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestPriorityClassNameFlag(t *testing.T) { diff --git a/pkg/cmd/cli/nodeagent/node_agent.go b/pkg/cmd/cli/nodeagent/node_agent.go index 7b0b6ebf0..96a46b4a7 100644 --- a/pkg/cmd/cli/nodeagent/node_agent.go +++ b/pkg/cmd/cli/nodeagent/node_agent.go @@ -19,7 +19,7 @@ package nodeagent import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/nodeagent/server.go b/pkg/cmd/cli/nodeagent/server.go index bb1764cb3..ed9aa1adb 100644 --- a/pkg/cmd/cli/nodeagent/server.go +++ b/pkg/cmd/cli/nodeagent/server.go @@ -47,23 +47,23 @@ import ( ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/manager" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/controller" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - repository "github.com/vmware-tanzu/velero/pkg/repository/manager" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/controller" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/nodeagent" + repository "github.com/velero-io/velero/pkg/repository/manager" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ) var ( diff --git a/pkg/cmd/cli/nodeagent/server_test.go b/pkg/cmd/cli/nodeagent/server_test.go index 152016ab6..5ddb3bfe5 100644 --- a/pkg/cmd/cli/nodeagent/server_test.go +++ b/pkg/cmd/cli/nodeagent/server_test.go @@ -31,12 +31,12 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/kubernetes/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - testutil "github.com/vmware-tanzu/velero/pkg/test" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/nodeagent" + testutil "github.com/velero-io/velero/pkg/test" + velerotypes "github.com/velero-io/velero/pkg/types" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) func Test_validatePodVolumesHostPath(t *testing.T) { diff --git a/pkg/cmd/cli/plugin/add.go b/pkg/cmd/cli/plugin/add.go index 9ea199fa9..17f203227 100644 --- a/pkg/cmd/cli/plugin/add.go +++ b/pkg/cmd/cli/plugin/add.go @@ -29,11 +29,11 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/confirm" + "github.com/velero-io/velero/pkg/cmd/util/flag" ) const ( diff --git a/pkg/cmd/cli/plugin/get.go b/pkg/cmd/cli/plugin/get.go index 60a939257..45d91b741 100644 --- a/pkg/cmd/cli/plugin/get.go +++ b/pkg/cmd/cli/plugin/get.go @@ -24,10 +24,10 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/serverstatus" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli/serverstatus" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/plugin/helpers.go b/pkg/cmd/cli/plugin/helpers.go index 28f681993..328e7b063 100644 --- a/pkg/cmd/cli/plugin/helpers.go +++ b/pkg/cmd/cli/plugin/helpers.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/client-go/kubernetes" - "github.com/vmware-tanzu/velero/pkg/install" + "github.com/velero-io/velero/pkg/install" ) // veleroDeployment returns a Velero deployment object, selected with label and container name, -// refer to https://github.com/vmware-tanzu/velero/issues/3961 for more information +// refer to https://github.com/velero-io/velero/issues/3961 for more information func veleroDeployment(ctx context.Context, kubeClient kubernetes.Interface, namespace string) (*appsv1api.Deployment, error) { veleroLabels := labels.FormatLabels(install.Labels()) diff --git a/pkg/cmd/cli/plugin/plugin.go b/pkg/cmd/cli/plugin/plugin.go index 0ba2f6177..ee6cbee67 100644 --- a/pkg/cmd/cli/plugin/plugin.go +++ b/pkg/cmd/cli/plugin/plugin.go @@ -19,7 +19,7 @@ package plugin import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/plugin/remove.go b/pkg/cmd/cli/plugin/remove.go index ed25dc680..8983fa08e 100644 --- a/pkg/cmd/cli/plugin/remove.go +++ b/pkg/cmd/cli/plugin/remove.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" ) func NewRemoveCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/podvolume/backup.go b/pkg/cmd/cli/podvolume/backup.go index ed2d6c09a..a8c9f1fdc 100644 --- a/pkg/cmd/cli/podvolume/backup.go +++ b/pkg/cmd/cli/podvolume/backup.go @@ -30,21 +30,21 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/klog/v2" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/podvolume/backup_test.go b/pkg/cmd/cli/podvolume/backup_test.go index 1c59af751..4ce5192d9 100644 --- a/pkg/cmd/cli/podvolume/backup_test.go +++ b/pkg/cmd/cli/podvolume/backup_test.go @@ -24,10 +24,10 @@ import ( "github.com/stretchr/testify/mock" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/internal/credentials" + cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/filesystem" ) func fakeCreateDataPathServiceWithErr(_ *podVolumeBackup) (dataPathService, error) { diff --git a/pkg/cmd/cli/podvolume/podvolume.go b/pkg/cmd/cli/podvolume/podvolume.go index 998e4683a..480538f1a 100644 --- a/pkg/cmd/cli/podvolume/podvolume.go +++ b/pkg/cmd/cli/podvolume/podvolume.go @@ -18,7 +18,7 @@ import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/podvolume/restore.go b/pkg/cmd/cli/podvolume/restore.go index 4c1596a04..3be43e731 100644 --- a/pkg/cmd/cli/podvolume/restore.go +++ b/pkg/cmd/cli/podvolume/restore.go @@ -31,18 +31,18 @@ import ( "k8s.io/klog/v2" ctrl "sigs.k8s.io/controller-runtime" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/podvolume/restore_test.go b/pkg/cmd/cli/podvolume/restore_test.go index 74fbb8090..3bc688781 100644 --- a/pkg/cmd/cli/podvolume/restore_test.go +++ b/pkg/cmd/cli/podvolume/restore_test.go @@ -20,8 +20,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) func fakeCreateRestoreDataPathServiceWithErr(_ *podVolumeRestore) (dataPathService, error) { diff --git a/pkg/cmd/cli/repo/get.go b/pkg/cmd/cli/repo/get.go index ec57b9845..adf4bbb66 100644 --- a/pkg/cmd/cli/repo/get.go +++ b/pkg/cmd/cli/repo/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/repo/repo.go b/pkg/cmd/cli/repo/repo.go index 957dad793..7c193c434 100644 --- a/pkg/cmd/cli/repo/repo.go +++ b/pkg/cmd/cli/repo/repo.go @@ -19,7 +19,7 @@ package repo import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/repomantenance/maintenance.go b/pkg/cmd/cli/repomantenance/maintenance.go index 46c54f7d2..4cdcd4ddd 100644 --- a/pkg/cmd/cli/repomantenance/maintenance.go +++ b/pkg/cmd/cli/repomantenance/maintenance.go @@ -18,16 +18,16 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerocli "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerocli "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/logging" - repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" - "github.com/vmware-tanzu/velero/pkg/repository/maintenance" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + repokey "github.com/velero-io/velero/pkg/repository/keys" + "github.com/velero-io/velero/pkg/repository/maintenance" + repomanager "github.com/velero-io/velero/pkg/repository/manager" ) type Options struct { diff --git a/pkg/cmd/cli/restore/create.go b/pkg/cmd/cli/restore/create.go index 2fb21433e..1bc04224b 100644 --- a/pkg/cmd/cli/restore/create.go +++ b/pkg/cmd/cli/restore/create.go @@ -31,15 +31,15 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/resourcemodifiers" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/velero/restore" + "github.com/velero-io/velero/internal/resourcemodifiers" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/velero/restore" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/create_test.go b/pkg/cmd/cli/restore/create_test.go index 8cc369dea..6f7344555 100644 --- a/pkg/cmd/cli/restore/create_test.go +++ b/pkg/cmd/cli/restore/create_test.go @@ -26,11 +26,11 @@ import ( controllerclient "sigs.k8s.io/controller-runtime/pkg/client" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestMostRecentBackup(t *testing.T) { diff --git a/pkg/cmd/cli/restore/delete.go b/pkg/cmd/cli/restore/delete.go index a2e70953d..41e4eb0dc 100644 --- a/pkg/cmd/cli/restore/delete.go +++ b/pkg/cmd/cli/restore/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" + "github.com/velero-io/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting restores. diff --git a/pkg/cmd/cli/restore/delete_test.go b/pkg/cmd/cli/restore/delete_test.go index e98f9b804..fd6b778a7 100644 --- a/pkg/cmd/cli/restore/delete_test.go +++ b/pkg/cmd/cli/restore/delete_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/cmd/cli" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/describe.go b/pkg/cmd/cli/restore/describe.go index 6404ef21d..939b359f6 100644 --- a/pkg/cmd/cli/restore/describe.go +++ b/pkg/cmd/cli/restore/describe.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" - "github.com/vmware-tanzu/velero/pkg/label" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/pkg/label" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/describe_test.go b/pkg/cmd/cli/restore/describe_test.go index 7c2ffe5f8..43c32cb72 100644 --- a/pkg/cmd/cli/restore/describe_test.go +++ b/pkg/cmd/cli/restore/describe_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/client-go/rest" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewDescribeCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/get.go b/pkg/cmd/cli/restore/get.go index 9a4014b25..ebacf90cc 100644 --- a/pkg/cmd/cli/restore/get.go +++ b/pkg/cmd/cli/restore/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/get_test.go b/pkg/cmd/cli/restore/get_test.go index 22b10e152..3c63e0466 100644 --- a/pkg/cmd/cli/restore/get_test.go +++ b/pkg/cmd/cli/restore/get_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + velerotest "github.com/velero-io/velero/pkg/test" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/logs.go b/pkg/cmd/cli/restore/logs.go index f4315c917..e11fc591f 100644 --- a/pkg/cmd/cli/restore/logs.go +++ b/pkg/cmd/cli/restore/logs.go @@ -26,11 +26,11 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" ) func NewLogsCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/restore/logs_test.go b/pkg/cmd/cli/restore/logs_test.go index 61c2392b6..a06fc0d93 100644 --- a/pkg/cmd/cli/restore/logs_test.go +++ b/pkg/cmd/cli/restore/logs_test.go @@ -25,12 +25,12 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + cmdtest "github.com/velero-io/velero/pkg/cmd/test" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestNewLogsCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/restore.go b/pkg/cmd/cli/restore/restore.go index 728c800ed..8ee152b19 100644 --- a/pkg/cmd/cli/restore/restore.go +++ b/pkg/cmd/cli/restore/restore.go @@ -19,7 +19,7 @@ package restore import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/restore/restore_test.go b/pkg/cmd/cli/restore/restore_test.go index 85f4b662a..1820882e1 100644 --- a/pkg/cmd/cli/restore/restore_test.go +++ b/pkg/cmd/cli/restore/restore_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" ) func TestNewRestoreCommand(t *testing.T) { diff --git a/pkg/cmd/cli/schedule/create.go b/pkg/cmd/cli/schedule/create.go index 47c19318f..29b9bffe3 100644 --- a/pkg/cmd/cli/schedule/create.go +++ b/pkg/cmd/cli/schedule/create.go @@ -26,12 +26,12 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/velero-io/velero/internal/resourcepolicies" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/delete.go b/pkg/cmd/cli/schedule/delete.go index 77b0bf883..a6dd9b284 100644 --- a/pkg/cmd/cli/schedule/delete.go +++ b/pkg/cmd/cli/schedule/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" + "github.com/velero-io/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting schedules. diff --git a/pkg/cmd/cli/schedule/describe.go b/pkg/cmd/cli/schedule/describe.go index 82c88dac7..39b86ec61 100644 --- a/pkg/cmd/cli/schedule/describe.go +++ b/pkg/cmd/cli/schedule/describe.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/get.go b/pkg/cmd/cli/schedule/get.go index 88bd49fe0..2b9c5564b 100644 --- a/pkg/cmd/cli/schedule/get.go +++ b/pkg/cmd/cli/schedule/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/pause.go b/pkg/cmd/cli/schedule/pause.go index 820e887a7..24b11ed03 100644 --- a/pkg/cmd/cli/schedule/pause.go +++ b/pkg/cmd/cli/schedule/pause.go @@ -28,10 +28,10 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" ) // NewPauseCommand creates the command for pause diff --git a/pkg/cmd/cli/schedule/schedule.go b/pkg/cmd/cli/schedule/schedule.go index 85c51c399..91eb5e2c7 100644 --- a/pkg/cmd/cli/schedule/schedule.go +++ b/pkg/cmd/cli/schedule/schedule.go @@ -19,7 +19,7 @@ package schedule import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/skip_options.go b/pkg/cmd/cli/schedule/skip_options.go index 14ea1b4ce..a425e23af 100644 --- a/pkg/cmd/cli/schedule/skip_options.go +++ b/pkg/cmd/cli/schedule/skip_options.go @@ -3,7 +3,7 @@ package schedule import ( "github.com/spf13/pflag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/flag" ) type SkipOptions struct { diff --git a/pkg/cmd/cli/schedule/unpause.go b/pkg/cmd/cli/schedule/unpause.go index 72197a934..bb1278cb8 100644 --- a/pkg/cmd/cli/schedule/unpause.go +++ b/pkg/cmd/cli/schedule/unpause.go @@ -19,9 +19,9 @@ package schedule import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli" ) // NewUnpauseCommand creates the command for unpause diff --git a/pkg/cmd/cli/select_option.go b/pkg/cmd/cli/select_option.go index b0f18f4ef..5dab105f0 100644 --- a/pkg/cmd/cli/select_option.go +++ b/pkg/cmd/cli/select_option.go @@ -23,7 +23,7 @@ import ( "golang.org/x/text/cases" "golang.org/x/text/language" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/flag" ) // SelectOptions defines the options for selecting resources diff --git a/pkg/cmd/cli/select_option_test.go b/pkg/cmd/cli/select_option_test.go index ea726bd4e..c53ca759a 100644 --- a/pkg/cmd/cli/select_option_test.go +++ b/pkg/cmd/cli/select_option_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/flag" ) func TestCompleteOfSelectOption(t *testing.T) { diff --git a/pkg/cmd/cli/serverstatus/server_status.go b/pkg/cmd/cli/serverstatus/server_status.go index ab994e2d6..885ed3078 100644 --- a/pkg/cmd/cli/serverstatus/server_status.go +++ b/pkg/cmd/cli/serverstatus/server_status.go @@ -24,9 +24,9 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + veleroclient "github.com/velero-io/velero/pkg/client" ) type Getter interface { diff --git a/pkg/cmd/cli/snapshotlocation/create.go b/pkg/cmd/cli/snapshotlocation/create.go index db55ad834..7cdb5fd56 100644 --- a/pkg/cmd/cli/snapshotlocation/create.go +++ b/pkg/cmd/cli/snapshotlocation/create.go @@ -25,12 +25,12 @@ import ( "github.com/spf13/pflag" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/get.go b/pkg/cmd/cli/snapshotlocation/get.go index 2acddbf7f..58ebf8eb3 100644 --- a/pkg/cmd/cli/snapshotlocation/get.go +++ b/pkg/cmd/cli/snapshotlocation/get.go @@ -23,10 +23,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/set.go b/pkg/cmd/cli/snapshotlocation/set.go index f6b8ac368..9326db185 100644 --- a/pkg/cmd/cli/snapshotlocation/set.go +++ b/pkg/cmd/cli/snapshotlocation/set.go @@ -26,12 +26,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/output" ) func NewSetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/snapshot_location.go b/pkg/cmd/cli/snapshotlocation/snapshot_location.go index baebff451..3993515c7 100644 --- a/pkg/cmd/cli/snapshotlocation/snapshot_location.go +++ b/pkg/cmd/cli/snapshotlocation/snapshot_location.go @@ -19,7 +19,7 @@ package snapshotlocation import ( "github.com/spf13/cobra" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/uninstall/uninstall.go b/pkg/cmd/cli/uninstall/uninstall.go index 80a349c92..5968b5643 100644 --- a/pkg/cmd/cli/uninstall/uninstall.go +++ b/pkg/cmd/cli/uninstall/uninstall.go @@ -41,14 +41,14 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller/controllerutil" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" - "github.com/vmware-tanzu/velero/pkg/controller" - "github.com/vmware-tanzu/velero/pkg/install" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/util/confirm" + "github.com/velero-io/velero/pkg/controller" + "github.com/velero-io/velero/pkg/install" + kubeutil "github.com/velero-io/velero/pkg/util/kube" ) var gracefulDeletionMaximumDuration = 1 * time.Minute @@ -213,7 +213,7 @@ func deleteNamespace(ctx context.Context, kbClient kbclient.Client, namespace st fmt.Print(".") } - // Must wait until the namespace is deleted to avoid the issue https://github.com/vmware-tanzu/velero/issues/3974 + // Must wait until the namespace is deleted to avoid the issue https://github.com/velero-io/velero/issues/3974 wait.Until(checkFunc, 5*time.Millisecond, ctx.Done()) if err != nil { return err diff --git a/pkg/cmd/cli/version/version.go b/pkg/cmd/cli/version/version.go index f8d261116..57a42ece5 100644 --- a/pkg/cmd/cli/version/version.go +++ b/pkg/cmd/cli/version/version.go @@ -27,10 +27,10 @@ import ( "golang.org/x/mod/semver" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/serverstatus" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/cli/serverstatus" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/version/version_test.go b/pkg/cmd/cli/version/version_test.go index 355626802..cb629653d 100644 --- a/pkg/cmd/cli/version/version_test.go +++ b/pkg/cmd/cli/version/version_test.go @@ -26,10 +26,10 @@ import ( "github.com/stretchr/testify/mock" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/buildinfo" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestPrintVersion(t *testing.T) { diff --git a/pkg/cmd/server/config/config.go b/pkg/cmd/server/config/config.go index e19086217..b2802edb1 100644 --- a/pkg/cmd/server/config/config.go +++ b/pkg/cmd/server/config/config.go @@ -5,18 +5,18 @@ import ( "strings" "time" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" "github.com/sirupsen/logrus" "github.com/spf13/pflag" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/constant" - podvolumeconfigs "github.com/vmware-tanzu/velero/pkg/podvolume/configs" - "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/constant" + podvolumeconfigs "github.com/velero-io/velero/pkg/podvolume/configs" + "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/logging" ) const ( diff --git a/pkg/cmd/server/plugin/plugin.go b/pkg/cmd/server/plugin/plugin.go index 071f0bbe5..d706bde07 100644 --- a/pkg/cmd/server/plugin/plugin.go +++ b/pkg/cmd/server/plugin/plugin.go @@ -21,22 +21,22 @@ import ( "github.com/spf13/cobra" apiextensions "k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/datamover" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/datamover" - dia "github.com/vmware-tanzu/velero/internal/delete/actions/csi" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - bia "github.com/vmware-tanzu/velero/pkg/backup/actions" - csibia "github.com/vmware-tanzu/velero/pkg/backup/actions/csi" - "github.com/vmware-tanzu/velero/pkg/client" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - iba "github.com/vmware-tanzu/velero/pkg/itemblock/actions" - veleroplugin "github.com/vmware-tanzu/velero/pkg/plugin/framework" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - ria "github.com/vmware-tanzu/velero/pkg/restore/actions" - csiria "github.com/vmware-tanzu/velero/pkg/restore/actions/csi" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + dia "github.com/velero-io/velero/internal/delete/actions/csi" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + bia "github.com/velero-io/velero/pkg/backup/actions" + csibia "github.com/velero-io/velero/pkg/backup/actions/csi" + "github.com/velero-io/velero/pkg/client" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + iba "github.com/velero-io/velero/pkg/itemblock/actions" + veleroplugin "github.com/velero-io/velero/pkg/plugin/framework" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + ria "github.com/velero-io/velero/pkg/restore/actions" + csiria "github.com/velero-io/velero/pkg/restore/actions/csi" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/server/server.go b/pkg/cmd/server/server.go index 44c88b980..ffcf6c7b4 100644 --- a/pkg/cmd/server/server.go +++ b/pkg/cmd/server/server.go @@ -55,38 +55,38 @@ import ( ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/manager" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/backup" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd" - "github.com/vmware-tanzu/velero/pkg/cmd/server/config" - "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/controller" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/podexec" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/repository" - repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" - "github.com/vmware-tanzu/velero/pkg/restore" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/storage" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/backup" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd" + "github.com/velero-io/velero/pkg/cmd/server/config" + "github.com/velero-io/velero/pkg/cmd/util/signals" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/controller" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/podexec" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/repository" + repokey "github.com/velero-io/velero/pkg/repository/keys" + repomanager "github.com/velero-io/velero/pkg/repository/manager" + "github.com/velero-io/velero/pkg/restore" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/server/server_test.go b/pkg/cmd/server/server_test.go index c602f7c9e..5ffacb436 100644 --- a/pkg/cmd/server/server_test.go +++ b/pkg/cmd/server/server_test.go @@ -31,15 +31,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/cmd/server/config" - "github.com/vmware-tanzu/velero/pkg/constant" - discovery_mocks "github.com/vmware-tanzu/velero/pkg/discovery/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/cmd/server/config" + "github.com/velero-io/velero/pkg/constant" + discovery_mocks "github.com/velero-io/velero/pkg/discovery/mocks" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" ) func TestVeleroResourcesExist(t *testing.T) { diff --git a/pkg/cmd/util/cacert/bsl_cacert.go b/pkg/cmd/util/cacert/bsl_cacert.go index d11729945..fe202bb84 100644 --- a/pkg/cmd/util/cacert/bsl_cacert.go +++ b/pkg/cmd/util/cacert/bsl_cacert.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/types" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // GetCACertFromBackup fetches the BackupStorageLocation for a backup and returns its cacert diff --git a/pkg/cmd/util/cacert/bsl_cacert_test.go b/pkg/cmd/util/cacert/bsl_cacert_test.go index 03e14b724..ac2f936ff 100644 --- a/pkg/cmd/util/cacert/bsl_cacert_test.go +++ b/pkg/cmd/util/cacert/bsl_cacert_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/util" ) func TestGetCACertFromBackup(t *testing.T) { diff --git a/pkg/cmd/util/downloadrequest/downloadrequest.go b/pkg/cmd/util/downloadrequest/downloadrequest.go index 6e1d30c37..8cdf6fbb7 100644 --- a/pkg/cmd/util/downloadrequest/downloadrequest.go +++ b/pkg/cmd/util/downloadrequest/downloadrequest.go @@ -32,8 +32,8 @@ import ( "github.com/pkg/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroV1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" + veleroV1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" ) // ErrNotFound is exported for external packages to check for when a file is diff --git a/pkg/cmd/util/downloadrequest/downloadrequest_test.go b/pkg/cmd/util/downloadrequest/downloadrequest_test.go index 995e83dc6..40372b614 100644 --- a/pkg/cmd/util/downloadrequest/downloadrequest_test.go +++ b/pkg/cmd/util/downloadrequest/downloadrequest_test.go @@ -39,10 +39,10 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/util" ) // createSelfSignedCertificate creates a self-signed certificate for testing. diff --git a/pkg/cmd/util/output/backup_describer.go b/pkg/cmd/util/output/backup_describer.go index e0637a4bd..24f4410be 100644 --- a/pkg/cmd/util/output/backup_describer.go +++ b/pkg/cmd/util/output/backup_describer.go @@ -34,15 +34,15 @@ import ( "github.com/fatih/color" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" - "github.com/vmware-tanzu/velero/pkg/itemoperation" + veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + "github.com/velero-io/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/internal/volume" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/volume" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/results" ) // DescribeBackup describes a backup in human-readable format. diff --git a/pkg/cmd/util/output/backup_describer_test.go b/pkg/cmd/util/output/backup_describer_test.go index 0de03bdaa..9b4923404 100644 --- a/pkg/cmd/util/output/backup_describer_test.go +++ b/pkg/cmd/util/output/backup_describer_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" ) func TestDescribeUploaderConfig(t *testing.T) { diff --git a/pkg/cmd/util/output/backup_printer.go b/pkg/cmd/util/output/backup_printer.go index 873bc9fc3..4ffb8c929 100644 --- a/pkg/cmd/util/output/backup_printer.go +++ b/pkg/cmd/util/output/backup_printer.go @@ -27,7 +27,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/util/duration" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/backup_printer_test.go b/pkg/cmd/util/output/backup_printer_test.go index 1a00bf6c1..6495e1058 100644 --- a/pkg/cmd/util/output/backup_printer_test.go +++ b/pkg/cmd/util/output/backup_printer_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestSortBackups(t *testing.T) { diff --git a/pkg/cmd/util/output/backup_repo_printer.go b/pkg/cmd/util/output/backup_repo_printer.go index 1e68cb949..4da5b25ad 100644 --- a/pkg/cmd/util/output/backup_repo_printer.go +++ b/pkg/cmd/util/output/backup_repo_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/backup_storage_location_printer.go b/pkg/cmd/util/output/backup_storage_location_printer.go index 90960ca52..6cb5cc010 100644 --- a/pkg/cmd/util/output/backup_storage_location_printer.go +++ b/pkg/cmd/util/output/backup_storage_location_printer.go @@ -20,8 +20,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd" ) var ( diff --git a/pkg/cmd/util/output/backup_structured_describer.go b/pkg/cmd/util/output/backup_structured_describer.go index 904afa34e..d65560328 100644 --- a/pkg/cmd/util/output/backup_structured_describer.go +++ b/pkg/cmd/util/output/backup_structured_describer.go @@ -28,11 +28,11 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + "github.com/velero-io/velero/pkg/util/results" ) // DescribeBackupInSF describes a backup in structured format. diff --git a/pkg/cmd/util/output/backup_structured_describer_test.go b/pkg/cmd/util/output/backup_structured_describer_test.go index c5ede1b36..de7fa3278 100644 --- a/pkg/cmd/util/output/backup_structured_describer_test.go +++ b/pkg/cmd/util/output/backup_structured_describer_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/util/results" ) func TestDescribeBackupInSF(t *testing.T) { diff --git a/pkg/cmd/util/output/output.go b/pkg/cmd/util/output/output.go index a0f8ce704..7b1c02dcf 100644 --- a/pkg/cmd/util/output/output.go +++ b/pkg/cmd/util/output/output.go @@ -29,9 +29,9 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/cli-runtime/pkg/printers" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/util/encode" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/util/encode" ) const ( diff --git a/pkg/cmd/util/output/output_test.go b/pkg/cmd/util/output/output_test.go index 1d3d67ae3..12fb5e74a 100644 --- a/pkg/cmd/util/output/output_test.go +++ b/pkg/cmd/util/output/output_test.go @@ -6,7 +6,7 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" "testing" ) diff --git a/pkg/cmd/util/output/plugin_printer.go b/pkg/cmd/util/output/plugin_printer.go index faa957314..3566e777a 100644 --- a/pkg/cmd/util/output/plugin_printer.go +++ b/pkg/cmd/util/output/plugin_printer.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/restore_describer.go b/pkg/cmd/util/output/restore_describer.go index a89943e74..b67fab071 100644 --- a/pkg/cmd/util/output/restore_describer.go +++ b/pkg/cmd/util/output/restore_describer.go @@ -25,7 +25,7 @@ import ( "sort" "strings" - "github.com/vmware-tanzu/velero/internal/volume" + "github.com/velero-io/velero/internal/volume" corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" @@ -33,12 +33,12 @@ import ( "github.com/fatih/color" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" - "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/results" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd/util/cacert" + "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/results" ) func DescribeRestore( diff --git a/pkg/cmd/util/output/restore_describer_test.go b/pkg/cmd/util/output/restore_describer_test.go index 6348dfaf0..3b92fc025 100644 --- a/pkg/cmd/util/output/restore_describer_test.go +++ b/pkg/cmd/util/output/restore_describer_test.go @@ -11,12 +11,12 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/results" ) func TestDescribeResult(t *testing.T) { diff --git a/pkg/cmd/util/output/restore_printer.go b/pkg/cmd/util/output/restore_printer.go index 782eb3485..331388a6a 100644 --- a/pkg/cmd/util/output/restore_printer.go +++ b/pkg/cmd/util/output/restore_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/schedule_describe_test.go b/pkg/cmd/util/output/schedule_describe_test.go index 12e8c5858..68f92e221 100644 --- a/pkg/cmd/util/output/schedule_describe_test.go +++ b/pkg/cmd/util/output/schedule_describe_test.go @@ -5,8 +5,8 @@ import ( "github.com/stretchr/testify/assert" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" ) func TestDescribeSchedule(t *testing.T) { diff --git a/pkg/cmd/util/output/schedule_describer.go b/pkg/cmd/util/output/schedule_describer.go index 73abb51a1..ceb66aefb 100644 --- a/pkg/cmd/util/output/schedule_describer.go +++ b/pkg/cmd/util/output/schedule_describer.go @@ -21,7 +21,7 @@ import ( "github.com/fatih/color" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func DescribeSchedule(schedule *v1.Schedule) string { diff --git a/pkg/cmd/util/output/schedule_printer.go b/pkg/cmd/util/output/schedule_printer.go index e39ee9069..c1c5ce7dd 100644 --- a/pkg/cmd/util/output/schedule_printer.go +++ b/pkg/cmd/util/output/schedule_printer.go @@ -22,7 +22,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/volume_snapshot_location_printer.go b/pkg/cmd/util/output/volume_snapshot_location_printer.go index d6168818c..46ec1cb69 100644 --- a/pkg/cmd/util/output/volume_snapshot_location_printer.go +++ b/pkg/cmd/util/output/volume_snapshot_location_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/velero/velero.go b/pkg/cmd/velero/velero.go index 42f07b03a..4487aacdc 100644 --- a/pkg/cmd/velero/velero.go +++ b/pkg/cmd/velero/velero.go @@ -25,35 +25,35 @@ import ( "github.com/spf13/cobra" "k8s.io/klog/v2" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/debug" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/podvolume" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/repomantenance" + "github.com/velero-io/velero/pkg/cmd/cli/debug" + "github.com/velero-io/velero/pkg/cmd/cli/podvolume" + "github.com/velero-io/velero/pkg/cmd/cli/repomantenance" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/bug" - cliclient "github.com/vmware-tanzu/velero/pkg/cmd/cli/client" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/completion" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/create" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/delete" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/describe" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/get" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/plugin" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/repo" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/uninstall" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/version" - "github.com/vmware-tanzu/velero/pkg/cmd/server" - runplugin "github.com/vmware-tanzu/velero/pkg/cmd/server/plugin" - veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/pkg/features" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/cmd/cli/backup" + "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" + "github.com/velero-io/velero/pkg/cmd/cli/bug" + cliclient "github.com/velero-io/velero/pkg/cmd/cli/client" + "github.com/velero-io/velero/pkg/cmd/cli/completion" + "github.com/velero-io/velero/pkg/cmd/cli/create" + "github.com/velero-io/velero/pkg/cmd/cli/delete" + "github.com/velero-io/velero/pkg/cmd/cli/describe" + "github.com/velero-io/velero/pkg/cmd/cli/get" + "github.com/velero-io/velero/pkg/cmd/cli/install" + "github.com/velero-io/velero/pkg/cmd/cli/plugin" + "github.com/velero-io/velero/pkg/cmd/cli/repo" + "github.com/velero-io/velero/pkg/cmd/cli/restore" + "github.com/velero-io/velero/pkg/cmd/cli/schedule" + "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" + "github.com/velero-io/velero/pkg/cmd/cli/uninstall" + "github.com/velero-io/velero/pkg/cmd/cli/version" + "github.com/velero-io/velero/pkg/cmd/server" + runplugin "github.com/velero-io/velero/pkg/cmd/server/plugin" + veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/nodeagent" + "github.com/velero-io/velero/pkg/cmd/cli/datamover" + "github.com/velero-io/velero/pkg/cmd/cli/nodeagent" ) func NewCommand(name string) *cobra.Command { diff --git a/pkg/controller/backup_controller.go b/pkg/controller/backup_controller.go index 496875bbf..acb292416 100644 --- a/pkg/controller/backup_controller.go +++ b/pkg/controller/backup_controller.go @@ -42,27 +42,27 @@ import ( "sigs.k8s.io/controller-runtime/pkg/event" "sigs.k8s.io/controller-runtime/pkg/predicate" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/internal/storage" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/encode" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" - "github.com/vmware-tanzu/velero/pkg/util/results" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/storage" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + pkgbackup "github.com/velero-io/velero/pkg/backup" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/encode" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/results" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ) const ( @@ -766,7 +766,7 @@ func (b *backupReconciler) runBackup(backup *pkgbackup.Request) error { } // native snapshots phase will either be failed or completed right away - // https://github.com/vmware-tanzu/velero/blob/de3ea52f0cc478e99efa7b9524c7f353514261a4/pkg/backup/item_backupper.go#L632-L639 + // https://github.com/velero-io/velero/blob/de3ea52f0cc478e99efa7b9524c7f353514261a4/pkg/backup/item_backupper.go#L632-L639 backup.Status.VolumeSnapshotsAttempted = len(backup.VolumeSnapshots.Get()) for _, snap := range backup.VolumeSnapshots.Get() { if snap.Status.Phase == volume.SnapshotPhaseCompleted { diff --git a/pkg/controller/backup_controller_test.go b/pkg/controller/backup_controller_test.go index 7b646edcf..2b4fd3e9a 100644 --- a/pkg/controller/backup_controller_test.go +++ b/pkg/controller/backup_controller_test.go @@ -44,24 +44,24 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" fakeClient "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + pkgbackup "github.com/velero-io/velero/pkg/backup" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ) type fakeBackupper struct { diff --git a/pkg/controller/backup_deletion_controller.go b/pkg/controller/backup_deletion_controller.go index 5fe29c5f1..33379b219 100644 --- a/pkg/controller/backup_deletion_controller.go +++ b/pkg/controller/backup_deletion_controller.go @@ -37,27 +37,27 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/delete" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/repository" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" - repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/delete" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/repository" + repomanager "github.com/velero-io/velero/pkg/repository/manager" + repotypes "github.com/velero-io/velero/pkg/repository/types" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ) const ( diff --git a/pkg/controller/backup_deletion_controller_test.go b/pkg/controller/backup_deletion_controller_test.go index 24cc65846..f6df13af1 100644 --- a/pkg/controller/backup_deletion_controller_test.go +++ b/pkg/controller/backup_deletion_controller_test.go @@ -44,21 +44,21 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/metrics" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" - "github.com/vmware-tanzu/velero/pkg/repository" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" - repomocks "github.com/vmware-tanzu/velero/pkg/repository/mocks" - repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + pkgbackup "github.com/velero-io/velero/pkg/backup" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/metrics" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero/mocks" + "github.com/velero-io/velero/pkg/repository" + repomanager "github.com/velero-io/velero/pkg/repository/manager" + repomocks "github.com/velero-io/velero/pkg/repository/mocks" + repotypes "github.com/velero-io/velero/pkg/repository/types" + velerotest "github.com/velero-io/velero/pkg/test" ) type backupDeletionControllerTestData struct { @@ -292,7 +292,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/vmware-tanzu/velero/issues/1546) + // (https://github.com/velero-io/velero/issues/1546) input.Labels = nil backup := builder.ForBackup(velerov1api.DefaultNamespace, "foo").Result() @@ -527,7 +527,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { input := defaultTestDbr() // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/vmware-tanzu/velero/issues/1546) + // (https://github.com/velero-io/velero/issues/1546) input.Labels = nil location := &velerov1api.BackupStorageLocation{ @@ -612,7 +612,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { input := defaultTestDbr() // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/vmware-tanzu/velero/issues/1546) + // (https://github.com/velero-io/velero/issues/1546) input.Labels = nil location := &velerov1api.BackupStorageLocation{ diff --git a/pkg/controller/backup_finalizer_controller.go b/pkg/controller/backup_finalizer_controller.go index b24c132fa..827089010 100644 --- a/pkg/controller/backup_finalizer_controller.go +++ b/pkg/controller/backup_finalizer_controller.go @@ -30,17 +30,17 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/util/encode" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + pkgbackup "github.com/velero-io/velero/pkg/backup" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/util/encode" ) // backupFinalizerReconciler reconciles a Backup object diff --git a/pkg/controller/backup_finalizer_controller_test.go b/pkg/controller/backup_finalizer_controller_test.go index ade3ce2cd..1ac8474c3 100644 --- a/pkg/controller/backup_finalizer_controller_test.go +++ b/pkg/controller/backup_finalizer_controller_test.go @@ -33,16 +33,16 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func mockBackupFinalizerReconciler(fakeClient kbclient.Client, fakeGlobalClient kbclient.Client, fakeClock *testclocks.FakeClock) (*backupFinalizerReconciler, *fakeBackupper) { diff --git a/pkg/controller/backup_operations_controller.go b/pkg/controller/backup_operations_controller.go index 1a5b49c0b..dd138ca52 100644 --- a/pkg/controller/backup_operations_controller.go +++ b/pkg/controller/backup_operations_controller.go @@ -22,7 +22,7 @@ import ( "fmt" "time" - v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -34,15 +34,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/util/encode" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/util/encode" + "github.com/velero-io/velero/pkg/util/kube" ) const ( @@ -229,7 +229,7 @@ func (c *backupOperationsReconciler) updateBackupAndOperationsJSON( if len(operations.ErrsSinceUpdate) > 0 { c.metrics.RegisterBackupItemsErrorsGauge(backupScheduleName, backup.Status.Errors) - // FIXME: download/upload results once https://github.com/vmware-tanzu/velero/pull/5576 is merged + // FIXME: download/upload results once https://github.com/velero-io/velero/pull/5576 is merged } removeIfComplete := true defer func() { diff --git a/pkg/controller/backup_operations_controller_test.go b/pkg/controller/backup_operations_controller_test.go index 0a25676d3..2b90571ce 100644 --- a/pkg/controller/backup_operations_controller_test.go +++ b/pkg/controller/backup_operations_controller_test.go @@ -20,7 +20,7 @@ import ( "testing" "time" - v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" @@ -33,18 +33,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/metrics" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/metrics" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + velerotest "github.com/velero-io/velero/pkg/test" ) var ( diff --git a/pkg/controller/backup_queue_controller.go b/pkg/controller/backup_queue_controller.go index c5cdc9461..97d21de9a 100644 --- a/pkg/controller/backup_queue_controller.go +++ b/pkg/controller/backup_queue_controller.go @@ -35,10 +35,10 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/util/collections" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/kube" ) // backupQueueReconciler reconciles a Backup object diff --git a/pkg/controller/backup_queue_controller_test.go b/pkg/controller/backup_queue_controller_test.go index 2b479ed7e..4b3064d4c 100644 --- a/pkg/controller/backup_queue_controller_test.go +++ b/pkg/controller/backup_queue_controller_test.go @@ -30,9 +30,9 @@ import ( //"sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBackupQueueReconciler(t *testing.T) { diff --git a/pkg/controller/backup_repository_controller.go b/pkg/controller/backup_repository_controller.go index 11ebb5aec..3cdc8252a 100644 --- a/pkg/controller/backup_repository_controller.go +++ b/pkg/controller/backup_repository_controller.go @@ -39,14 +39,14 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/repository/maintenance" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/repository/maintenance" + repomanager "github.com/velero-io/velero/pkg/repository/manager" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ) const ( diff --git a/pkg/controller/backup_repository_controller_test.go b/pkg/controller/backup_repository_controller_test.go index ed952f4ae..cd9cd6a01 100644 --- a/pkg/controller/backup_repository_controller_test.go +++ b/pkg/controller/backup_repository_controller_test.go @@ -32,17 +32,17 @@ import ( "k8s.io/utils/clock" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/repository/maintenance" - repomaintenance "github.com/vmware-tanzu/velero/pkg/repository/maintenance" - repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" - repomokes "github.com/vmware-tanzu/velero/pkg/repository/mocks" - repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/repository/maintenance" + repomaintenance "github.com/velero-io/velero/pkg/repository/maintenance" + repomanager "github.com/velero-io/velero/pkg/repository/manager" + repomokes "github.com/velero-io/velero/pkg/repository/mocks" + repotypes "github.com/velero-io/velero/pkg/repository/types" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/logging" "sigs.k8s.io/controller-runtime/pkg/client" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" diff --git a/pkg/controller/backup_storage_location_controller.go b/pkg/controller/backup_storage_location_controller.go index abcd1e59e..e65b883b6 100644 --- a/pkg/controller/backup_storage_location_controller.go +++ b/pkg/controller/backup_storage_location_controller.go @@ -22,7 +22,7 @@ import ( "strings" "time" - "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/metrics" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -32,12 +32,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/storage" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/backup_storage_location_controller_test.go b/pkg/controller/backup_storage_location_controller_test.go index 8a5dc4a4a..4eddeeed0 100644 --- a/pkg/controller/backup_storage_location_controller_test.go +++ b/pkg/controller/backup_storage_location_controller_test.go @@ -20,7 +20,7 @@ import ( "testing" "time" - "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/metrics" . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" @@ -35,13 +35,13 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/client-go/kubernetes/scheme" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/storage" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) var _ = Describe("Backup Storage Location Reconciler", func() { diff --git a/pkg/controller/backup_sync_controller.go b/pkg/controller/backup_sync_controller.go index b84ae6f0b..99d4ca3ed 100644 --- a/pkg/controller/backup_sync_controller.go +++ b/pkg/controller/backup_sync_controller.go @@ -33,13 +33,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/builder" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/util/kube" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/util/kube" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/controller/backup_sync_controller_test.go b/pkg/controller/backup_sync_controller_test.go index fe440ff09..8c88da72f 100644 --- a/pkg/controller/backup_sync_controller_test.go +++ b/pkg/controller/backup_sync_controller_test.go @@ -37,13 +37,13 @@ import ( ctrlClient "sigs.k8s.io/controller-runtime/pkg/client" ctrlfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/label" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/label" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) func defaultLocation(namespace string) *velerov1api.BackupStorageLocation { diff --git a/pkg/controller/data_download_controller.go b/pkg/controller/data_download_controller.go index 36fec450b..c69dfdf5a 100644 --- a/pkg/controller/data_download_controller.go +++ b/pkg/controller/data_download_controller.go @@ -40,20 +40,20 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/constant" - datamover "github.com/vmware-tanzu/velero/pkg/datamover" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - repository "github.com/vmware-tanzu/velero/pkg/repository/manager" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/constant" + datamover "github.com/velero-io/velero/pkg/datamover" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/nodeagent" + repository "github.com/velero-io/velero/pkg/repository/manager" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/kube" ) // DataDownloadReconciler reconciles a DataDownload object diff --git a/pkg/controller/data_download_controller_test.go b/pkg/controller/data_download_controller_test.go index 397f931c0..f49bfd3f0 100644 --- a/pkg/controller/data_download_controller_test.go +++ b/pkg/controller/data_download_controller_test.go @@ -40,18 +40,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" - "github.com/vmware-tanzu/velero/pkg/exposer" - exposermockes "github.com/vmware-tanzu/velero/pkg/exposer/mocks" - "github.com/vmware-tanzu/velero/pkg/metrics" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + "github.com/velero-io/velero/pkg/exposer" + exposermockes "github.com/velero-io/velero/pkg/exposer/mocks" + "github.com/velero-io/velero/pkg/metrics" + velerotest "github.com/velero-io/velero/pkg/test" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" ) const dataDownloadName string = "datadownload-1" diff --git a/pkg/controller/data_upload_controller.go b/pkg/controller/data_upload_controller.go index 13be03994..35c37f691 100644 --- a/pkg/controller/data_upload_controller.go +++ b/pkg/controller/data_upload_controller.go @@ -41,19 +41,19 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/datamover" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/datamover" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/nodeagent" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/data_upload_controller_test.go b/pkg/controller/data_upload_controller_test.go index a73e3de94..ec6b90711 100644 --- a/pkg/controller/data_upload_controller_test.go +++ b/pkg/controller/data_upload_controller_test.go @@ -46,18 +46,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - datapathmocks "github.com/vmware-tanzu/velero/pkg/datapath/mocks" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + datapathmocks "github.com/velero-io/velero/pkg/datapath/mocks" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + velerotest "github.com/velero-io/velero/pkg/test" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) const dataUploadName = "dataupload-1" diff --git a/pkg/controller/download_request_controller.go b/pkg/controller/download_request_controller.go index bd9565895..0c817d4be 100644 --- a/pkg/controller/download_request_controller.go +++ b/pkg/controller/download_request_controller.go @@ -29,12 +29,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/download_request_controller_test.go b/pkg/controller/download_request_controller_test.go index 81bdbab83..d57bca316 100644 --- a/pkg/controller/download_request_controller_test.go +++ b/pkg/controller/download_request_controller_test.go @@ -32,12 +32,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) var _ = Describe("Download Request Reconciler", func() { diff --git a/pkg/controller/gc_controller.go b/pkg/controller/gc_controller.go index bb3c60ae5..c9141face 100644 --- a/pkg/controller/gc_controller.go +++ b/pkg/controller/gc_controller.go @@ -31,13 +31,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/event" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/util/kube" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + pkgbackup "github.com/velero-io/velero/pkg/backup" + veleroclient "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/util/kube" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ) const ( diff --git a/pkg/controller/gc_controller_test.go b/pkg/controller/gc_controller_test.go index 754b46e0a..04c8b9c1c 100644 --- a/pkg/controller/gc_controller_test.go +++ b/pkg/controller/gc_controller_test.go @@ -28,9 +28,9 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) func mockGCReconciler(fakeClient kbclient.Client, fakeClock *testclocks.FakeClock, freq time.Duration) *gcReconciler { diff --git a/pkg/controller/pod_volume_backup_controller.go b/pkg/controller/pod_volume_backup_controller.go index 0bcbfa6d2..907aca868 100644 --- a/pkg/controller/pod_volume_backup_controller.go +++ b/pkg/controller/pod_volume_backup_controller.go @@ -40,16 +40,16 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/pod_volume_backup_controller_test.go b/pkg/controller/pod_volume_backup_controller_test.go index b49d7eb5b..3806e4e99 100644 --- a/pkg/controller/pod_volume_backup_controller_test.go +++ b/pkg/controller/pod_volume_backup_controller_test.go @@ -43,16 +43,16 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - datapathmocks "github.com/vmware-tanzu/velero/pkg/datapath/mocks" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/metrics" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + datapathmocks "github.com/velero-io/velero/pkg/datapath/mocks" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/metrics" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" ) const pvbName = "pvb-1" diff --git a/pkg/controller/pod_volume_restore_controller.go b/pkg/controller/pod_volume_restore_controller.go index f40de528b..62a6d793d 100644 --- a/pkg/controller/pod_volume_restore_controller.go +++ b/pkg/controller/pod_volume_restore_controller.go @@ -42,18 +42,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/exposer" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - repository "github.com/vmware-tanzu/velero/pkg/repository/manager" - "github.com/vmware-tanzu/velero/pkg/restorehelper" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/nodeagent" + repository "github.com/velero-io/velero/pkg/repository/manager" + "github.com/velero-io/velero/pkg/restorehelper" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/kube" ) func NewPodVolumeRestoreReconciler( diff --git a/pkg/controller/pod_volume_restore_controller_test.go b/pkg/controller/pod_volume_restore_controller_test.go index 1819cbc32..87a17e639 100644 --- a/pkg/controller/pod_volume_restore_controller_test.go +++ b/pkg/controller/pod_volume_restore_controller_test.go @@ -43,18 +43,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" - "github.com/vmware-tanzu/velero/pkg/exposer" - exposermockes "github.com/vmware-tanzu/velero/pkg/exposer/mocks" - "github.com/vmware-tanzu/velero/pkg/restorehelper" - "github.com/vmware-tanzu/velero/pkg/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + "github.com/velero-io/velero/pkg/exposer" + exposermockes "github.com/velero-io/velero/pkg/exposer/mocks" + "github.com/velero-io/velero/pkg/restorehelper" + "github.com/velero-io/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) func TestShouldProcess(t *testing.T) { diff --git a/pkg/controller/restore_controller.go b/pkg/controller/restore_controller.go index 469951f27..9dca400f1 100644 --- a/pkg/controller/restore_controller.go +++ b/pkg/controller/restore_controller.go @@ -42,24 +42,24 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller/controllerutil" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/resourcemodifiers" - "github.com/vmware-tanzu/velero/internal/volume" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - pkgrestore "github.com/vmware-tanzu/velero/pkg/restore" - "github.com/vmware-tanzu/velero/pkg/util/collections" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" - "github.com/vmware-tanzu/velero/pkg/util/results" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" - pkgrestoreUtil "github.com/vmware-tanzu/velero/pkg/util/velero/restore" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/resourcemodifiers" + "github.com/velero-io/velero/internal/volume" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + pkgrestore "github.com/velero-io/velero/pkg/restore" + "github.com/velero-io/velero/pkg/util/collections" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/results" + veleroutil "github.com/velero-io/velero/pkg/util/velero" + pkgrestoreUtil "github.com/velero-io/velero/pkg/util/velero/restore" ) // nonRestorableResources is an exclusion list for the restoration process. Any resources @@ -70,22 +70,22 @@ var nonRestorableResources = []string{ "events.events.k8s.io", // Don't ever restore backups - if appropriate, they'll be synced in from object storage. - // https://github.com/vmware-tanzu/velero/issues/622 + // https://github.com/velero-io/velero/issues/622 "backups.velero.io", // Restores are cluster-specific, and don't have value moving across clusters. - // https://github.com/vmware-tanzu/velero/issues/622 + // https://github.com/velero-io/velero/issues/622 "restores.velero.io", // TODO: Remove this in v1.11 or v1.12 // Restic repositories are automatically managed by Velero and will be automatically // created as needed if they don't exist. - // https://github.com/vmware-tanzu/velero/issues/1113 + // https://github.com/velero-io/velero/issues/1113 "resticrepositories.velero.io", // CSINode delegates cluster node for CSI operation. // VolumeAttachement records PV mounts to which node. - // https://github.com/vmware-tanzu/velero/issues/4823 + // https://github.com/velero-io/velero/issues/4823 "csinodes.storage.k8s.io", "volumeattachments.storage.k8s.io", diff --git a/pkg/controller/restore_controller_test.go b/pkg/controller/restore_controller_test.go index b013ee64d..1219cf1e9 100644 --- a/pkg/controller/restore_controller_test.go +++ b/pkg/controller/restore_controller_test.go @@ -35,20 +35,20 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/resourcemodifiers" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/metrics" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - pkgrestore "github.com/vmware-tanzu/velero/pkg/restore" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/logging" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/resourcemodifiers" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/metrics" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/framework" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + pkgrestore "github.com/velero-io/velero/pkg/restore" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/results" ) func TestFetchBackupInfo(t *testing.T) { diff --git a/pkg/controller/restore_finalizer_controller.go b/pkg/controller/restore_finalizer_controller.go index f82216bc3..00aa9db45 100644 --- a/pkg/controller/restore_finalizer_controller.go +++ b/pkg/controller/restore_finalizer_controller.go @@ -36,18 +36,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/boolptr" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/results" ) type restoreFinalizerReconciler struct { diff --git a/pkg/controller/restore_finalizer_controller_test.go b/pkg/controller/restore_finalizer_controller_test.go index 6fb5ba303..6bf3f7c84 100644 --- a/pkg/controller/restore_finalizer_controller_test.go +++ b/pkg/controller/restore_finalizer_controller_test.go @@ -36,20 +36,20 @@ import ( ctrl "sigs.k8s.io/controller-runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/metrics" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - pkgUtilKubeMocks "github.com/vmware-tanzu/velero/pkg/util/kube/mocks" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/metrics" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" + pkgUtilKubeMocks "github.com/velero-io/velero/pkg/util/kube/mocks" + "github.com/velero-io/velero/pkg/util/results" ) func TestRestoreFinalizerReconcile(t *testing.T) { diff --git a/pkg/controller/restore_operations_controller.go b/pkg/controller/restore_operations_controller.go index 0539e21a4..c5b6c00e8 100644 --- a/pkg/controller/restore_operations_controller.go +++ b/pkg/controller/restore_operations_controller.go @@ -30,14 +30,14 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/restore_operations_controller_test.go b/pkg/controller/restore_operations_controller_test.go index a1ec0f792..aa50dd3e7 100644 --- a/pkg/controller/restore_operations_controller_test.go +++ b/pkg/controller/restore_operations_controller_test.go @@ -31,18 +31,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/itemoperationmap" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/metrics" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/itemoperationmap" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/metrics" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" + velerotest "github.com/velero-io/velero/pkg/test" ) var ( diff --git a/pkg/controller/schedule_controller.go b/pkg/controller/schedule_controller.go index 443b3c08b..f811ae81f 100644 --- a/pkg/controller/schedule_controller.go +++ b/pkg/controller/schedule_controller.go @@ -33,11 +33,11 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/metrics" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/metrics" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/schedule_controller_test.go b/pkg/controller/schedule_controller_test.go index f4585763c..153e82889 100644 --- a/pkg/controller/schedule_controller_test.go +++ b/pkg/controller/schedule_controller_test.go @@ -31,10 +31,10 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/metrics" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/metrics" + velerotest "github.com/velero-io/velero/pkg/test" ) // Test reconcile function of schedule controller. Pause is not covered as event filter will not allow it through @@ -334,7 +334,7 @@ func TestGetNextRunTime(t *testing.T) { } func TestParseCronSchedule(t *testing.T) { - // From https://github.com/vmware-tanzu/velero/issues/30, where we originally were using cron.Parse(), + // From https://github.com/velero-io/velero/issues/30, where we originally were using cron.Parse(), // which treats the first field as seconds, and not minutes. We want to use cron.ParseStandard() // instead, which has the first field as minutes. diff --git a/pkg/controller/server_status_request_controller.go b/pkg/controller/server_status_request_controller.go index 3fb1af80b..15f7a9176 100644 --- a/pkg/controller/server_status_request_controller.go +++ b/pkg/controller/server_status_request_controller.go @@ -29,12 +29,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller" - "github.com/vmware-tanzu/velero/internal/velero" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/constant" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/internal/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/constant" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" ) const ( diff --git a/pkg/controller/server_status_request_controller_test.go b/pkg/controller/server_status_request_controller_test.go index eb95c7e87..cc2ca223d 100644 --- a/pkg/controller/server_status_request_controller_test.go +++ b/pkg/controller/server_status_request_controller_test.go @@ -30,12 +30,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" + velerotest "github.com/velero-io/velero/pkg/test" ) func statusRequestBuilder(resourceVersion string) *builder.ServerStatusRequestBuilder { diff --git a/pkg/controller/suite_test.go b/pkg/controller/suite_test.go index 1e5e90717..2c221d22c 100644 --- a/pkg/controller/suite_test.go +++ b/pkg/controller/suite_test.go @@ -25,8 +25,8 @@ import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/persistence" - persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/velero-io/velero/pkg/persistence" + persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" "k8s.io/klog/v2" "sigs.k8s.io/controller-runtime/pkg/envtest" @@ -35,8 +35,8 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" "k8s.io/client-go/kubernetes/scheme" "k8s.io/client-go/rest" diff --git a/pkg/datamover/backup_micro_service.go b/pkg/datamover/backup_micro_service.go index 61c308f15..36e5d844d 100644 --- a/pkg/datamover/backup_micro_service.go +++ b/pkg/datamover/backup_micro_service.go @@ -31,13 +31,13 @@ import ( cachetool "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/cache" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/datamover/backup_micro_service_test.go b/pkg/datamover/backup_micro_service_test.go index c5a9a4487..ead9e53fd 100644 --- a/pkg/datamover/backup_micro_service_test.go +++ b/pkg/datamover/backup_micro_service_test.go @@ -30,20 +30,20 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/uploader" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerotest "github.com/velero-io/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" ) type backupMsTestHelper struct { diff --git a/pkg/datamover/dataupload_delete_action.go b/pkg/datamover/dataupload_delete_action.go index 6b36e1068..e0b1e7abc 100644 --- a/pkg/datamover/dataupload_delete_action.go +++ b/pkg/datamover/dataupload_delete_action.go @@ -12,11 +12,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/velero" + repotypes "github.com/velero-io/velero/pkg/repository/types" ) type DataUploadDeleteAction struct { diff --git a/pkg/datamover/dataupload_delete_action_test.go b/pkg/datamover/dataupload_delete_action_test.go index cdbf4b006..8ec70a0f7 100644 --- a/pkg/datamover/dataupload_delete_action_test.go +++ b/pkg/datamover/dataupload_delete_action_test.go @@ -32,11 +32,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func toUnstructured(t *testing.T, du *velerov2alpha1.DataUpload) runtime.Unstructured { diff --git a/pkg/datamover/restore_micro_service.go b/pkg/datamover/restore_micro_service.go index 0cb5f18ec..0f8b26792 100644 --- a/pkg/datamover/restore_micro_service.go +++ b/pkg/datamover/restore_micro_service.go @@ -29,13 +29,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" cachetool "k8s.io/client-go/tools/cache" ) diff --git a/pkg/datamover/restore_micro_service_test.go b/pkg/datamover/restore_micro_service_test.go index a53e4d6d5..5927f6996 100644 --- a/pkg/datamover/restore_micro_service_test.go +++ b/pkg/datamover/restore_micro_service_test.go @@ -31,15 +31,15 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + "github.com/velero-io/velero/pkg/uploader" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestOnDataDownloadFailed(t *testing.T) { diff --git a/pkg/datapath/file_system.go b/pkg/datapath/file_system.go index 67db98fbe..48a8d9e21 100644 --- a/pkg/datapath/file_system.go +++ b/pkg/datapath/file_system.go @@ -24,14 +24,14 @@ import ( "github.com/sirupsen/logrus" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" - repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" - repoProvider "github.com/vmware-tanzu/velero/pkg/repository/provider" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/uploader/provider" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" + repokey "github.com/velero-io/velero/pkg/repository/keys" + repoProvider "github.com/velero-io/velero/pkg/repository/provider" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader/provider" + "github.com/velero-io/velero/pkg/util/filesystem" ) // FSBRInitParam define the input param for FSBR init diff --git a/pkg/datapath/file_system_test.go b/pkg/datapath/file_system_test.go index c605311d2..3898793cd 100644 --- a/pkg/datapath/file_system_test.go +++ b/pkg/datapath/file_system_test.go @@ -25,9 +25,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader/provider" - providerMock "github.com/vmware-tanzu/velero/pkg/uploader/provider/mocks" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader/provider" + providerMock "github.com/velero-io/velero/pkg/uploader/provider/mocks" ) func TestAsyncBackup(t *testing.T) { diff --git a/pkg/datapath/micro_service_watcher.go b/pkg/datapath/micro_service_watcher.go index 665b84b81..ae523c05b 100644 --- a/pkg/datapath/micro_service_watcher.go +++ b/pkg/datapath/micro_service_watcher.go @@ -32,13 +32,13 @@ import ( "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/manager" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/logging" ) const ( diff --git a/pkg/datapath/micro_service_watcher_test.go b/pkg/datapath/micro_service_watcher_test.go index 6724c290c..2687a323a 100644 --- a/pkg/datapath/micro_service_watcher_test.go +++ b/pkg/datapath/micro_service_watcher_test.go @@ -36,10 +36,10 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/logging" ) func TestReEnsureThisPod(t *testing.T) { diff --git a/pkg/datapath/mocks/asyncBR.go b/pkg/datapath/mocks/asyncBR.go index ef87fde83..05a75b4c1 100644 --- a/pkg/datapath/mocks/asyncBR.go +++ b/pkg/datapath/mocks/asyncBR.go @@ -6,7 +6,7 @@ import ( context "context" mock "github.com/stretchr/testify/mock" - datapath "github.com/vmware-tanzu/velero/pkg/datapath" + datapath "github.com/velero-io/velero/pkg/datapath" ) // AsyncBR is an autogenerated mock type for the AsyncBR type diff --git a/pkg/datapath/types.go b/pkg/datapath/types.go index a9c2331a6..ebd4f14d6 100644 --- a/pkg/datapath/types.go +++ b/pkg/datapath/types.go @@ -19,7 +19,7 @@ package datapath import ( "context" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader" ) // Result represents the result of a backup/restore diff --git a/pkg/discovery/helper.go b/pkg/discovery/helper.go index 11c2d623b..282c91bf6 100644 --- a/pkg/discovery/helper.go +++ b/pkg/discovery/helper.go @@ -30,9 +30,9 @@ import ( "k8s.io/client-go/discovery" "k8s.io/client-go/restmapper" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/features" - kcmdutil "github.com/vmware-tanzu/velero/third_party/kubernetes/pkg/kubectl/cmd/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/features" + kcmdutil "github.com/velero-io/velero/third_party/kubernetes/pkg/kubectl/cmd/util" ) //go:generate mockery --name Helper diff --git a/pkg/discovery/helper_test.go b/pkg/discovery/helper_test.go index d70c10438..c8af4f62e 100644 --- a/pkg/discovery/helper_test.go +++ b/pkg/discovery/helper_test.go @@ -30,10 +30,10 @@ import ( "k8s.io/client-go/discovery/fake" clientgotesting "k8s.io/client-go/testing" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/features" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/features" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/logging" ) func TestSortResources(t *testing.T) { diff --git a/pkg/exposer/cache_volume.go b/pkg/exposer/cache_volume.go index 85571c243..e914c191c 100644 --- a/pkg/exposer/cache_volume.go +++ b/pkg/exposer/cache_volume.go @@ -24,8 +24,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) type CacheConfigs struct { diff --git a/pkg/exposer/csi_snapshot.go b/pkg/exposer/csi_snapshot.go index 079a4b527..316b2ae75 100644 --- a/pkg/exposer/csi_snapshot.go +++ b/pkg/exposer/csi_snapshot.go @@ -33,12 +33,12 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/nodeagent" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" + "github.com/velero-io/velero/pkg/util/kube" ) // CSISnapshotExposeParam define the input param for Expose of CSI snapshots diff --git a/pkg/exposer/csi_snapshot_priority_test.go b/pkg/exposer/csi_snapshot_priority_test.go index d1ffa4700..bb1ce9ea0 100644 --- a/pkg/exposer/csi_snapshot_priority_test.go +++ b/pkg/exposer/csi_snapshot_priority_test.go @@ -28,9 +28,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/client-go/kubernetes/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/kube" ) func TestCreateBackupPodWithPriorityClass(t *testing.T) { diff --git a/pkg/exposer/csi_snapshot_test.go b/pkg/exposer/csi_snapshot_test.go index e1a9860eb..2e91f28ab 100644 --- a/pkg/exposer/csi_snapshot_test.go +++ b/pkg/exposer/csi_snapshot_test.go @@ -36,12 +36,12 @@ import ( "k8s.io/utils/pointer" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" storagev1api "k8s.io/api/storage/v1" ) diff --git a/pkg/exposer/generic_restore.go b/pkg/exposer/generic_restore.go index b711e7364..adfe89f9f 100644 --- a/pkg/exposer/generic_restore.go +++ b/pkg/exposer/generic_restore.go @@ -30,10 +30,10 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/nodeagent" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) // GenericRestoreExposeParam define the input param for Generic Restore Expose diff --git a/pkg/exposer/generic_restore_priority_test.go b/pkg/exposer/generic_restore_priority_test.go index 642e0cc43..c0c2d677e 100644 --- a/pkg/exposer/generic_restore_priority_test.go +++ b/pkg/exposer/generic_restore_priority_test.go @@ -27,9 +27,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/client-go/kubernetes/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/kube" ) // TestCreateRestorePodWithPriorityClass verifies that the priority class name is properly set in the restore pod diff --git a/pkg/exposer/generic_restore_test.go b/pkg/exposer/generic_restore_test.go index 799719a50..397a8871f 100644 --- a/pkg/exposer/generic_restore_test.go +++ b/pkg/exposer/generic_restore_test.go @@ -32,9 +32,9 @@ import ( "k8s.io/client-go/kubernetes/fake" clientTesting "k8s.io/client-go/testing" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/kube" ) func TestRestoreExpose(t *testing.T) { diff --git a/pkg/exposer/host_path.go b/pkg/exposer/host_path.go index e51178711..0ba791454 100644 --- a/pkg/exposer/host_path.go +++ b/pkg/exposer/host_path.go @@ -26,11 +26,11 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" ) var getVolumeDirectory = kube.GetVolumeDirectory diff --git a/pkg/exposer/host_path_test.go b/pkg/exposer/host_path_test.go index e751afe0d..7089fcbb3 100644 --- a/pkg/exposer/host_path_test.go +++ b/pkg/exposer/host_path_test.go @@ -28,13 +28,13 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/nodeagent" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" ) func TestGetPodVolumeHostPath(t *testing.T) { diff --git a/pkg/exposer/image.go b/pkg/exposer/image.go index 58658e1b7..8bdc7634b 100644 --- a/pkg/exposer/image.go +++ b/pkg/exposer/image.go @@ -24,7 +24,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/nodeagent" ) type inheritedPodInfo struct { diff --git a/pkg/exposer/image_test.go b/pkg/exposer/image_test.go index 5c47f5c04..0edadf823 100644 --- a/pkg/exposer/image_test.go +++ b/pkg/exposer/image_test.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/kube" appsv1api "k8s.io/api/apps/v1" corev1api "k8s.io/api/core/v1" diff --git a/pkg/exposer/mocks/GenericRestoreExposer.go b/pkg/exposer/mocks/GenericRestoreExposer.go index 7daae6d6d..e3214ad2a 100644 --- a/pkg/exposer/mocks/GenericRestoreExposer.go +++ b/pkg/exposer/mocks/GenericRestoreExposer.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/exposer" "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" ) diff --git a/pkg/exposer/mocks/PodVolumeExposer.go b/pkg/exposer/mocks/PodVolumeExposer.go index d601e5c5b..be0a20486 100644 --- a/pkg/exposer/mocks/PodVolumeExposer.go +++ b/pkg/exposer/mocks/PodVolumeExposer.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/velero-io/velero/pkg/exposer" "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" ) diff --git a/pkg/exposer/pod_volume.go b/pkg/exposer/pod_volume.go index aeb6f1903..4de0fba57 100644 --- a/pkg/exposer/pod_volume.go +++ b/pkg/exposer/pod_volume.go @@ -31,10 +31,10 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/exposer/pod_volume_test.go b/pkg/exposer/pod_volume_test.go index d65030e22..48b7d1480 100644 --- a/pkg/exposer/pod_volume_test.go +++ b/pkg/exposer/pod_volume_test.go @@ -19,11 +19,11 @@ import ( clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/filesystem" ) func TestPodVolumeExpose(t *testing.T) { diff --git a/pkg/exposer/vgdp_counter.go b/pkg/exposer/vgdp_counter.go index cf6737c14..b0c9f94d1 100644 --- a/pkg/exposer/vgdp_counter.go +++ b/pkg/exposer/vgdp_counter.go @@ -9,8 +9,8 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/client-go/tools/cache" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" "sigs.k8s.io/controller-runtime/pkg/manager" diff --git a/pkg/exposer/vgdp_counter_test.go b/pkg/exposer/vgdp_counter_test.go index 725b5f8d6..b67f61f55 100644 --- a/pkg/exposer/vgdp_counter_test.go +++ b/pkg/exposer/vgdp_counter_test.go @@ -9,11 +9,11 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) func TestIsConstrained(t *testing.T) { diff --git a/pkg/install/daemonset.go b/pkg/install/daemonset.go index 10d2764e6..616b8b5fe 100644 --- a/pkg/install/daemonset.go +++ b/pkg/install/daemonset.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/utils/ptr" - "github.com/vmware-tanzu/velero/internal/velero" - "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/velero-io/velero/internal/velero" + "github.com/velero-io/velero/pkg/nodeagent" ) func DaemonSet(namespace string, opts ...podTemplateOption) *appsv1api.DaemonSet { diff --git a/pkg/install/deployment.go b/pkg/install/deployment.go index 7af17bc53..a33c597f6 100644 --- a/pkg/install/deployment.go +++ b/pkg/install/deployment.go @@ -26,9 +26,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/utils/ptr" - "github.com/vmware-tanzu/velero/internal/velero" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/velero" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/util/kube" ) type podTemplateOption func(*podTemplateConfig) diff --git a/pkg/install/deployment_test.go b/pkg/install/deployment_test.go index 53b696f72..decd38295 100644 --- a/pkg/install/deployment_test.go +++ b/pkg/install/deployment_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/kube" ) func TestDeployment(t *testing.T) { diff --git a/pkg/install/import_test.go b/pkg/install/import_test.go index e77befe46..dfee28291 100644 --- a/pkg/install/import_test.go +++ b/pkg/install/import_test.go @@ -13,7 +13,7 @@ import ( // test that this package do not import cloud provider -// Prevent https://github.com/vmware-tanzu/velero/issues/8207 and https://github.com/vmware-tanzu/velero/issues/8157 +// Prevent https://github.com/velero-io/velero/issues/8207 and https://github.com/velero-io/velero/issues/8157 func TestPkgImportNoCloudProvider(t *testing.T) { _, filename, _, ok := runtime.Caller(0) if !ok { diff --git a/pkg/install/install.go b/pkg/install/install.go index b60c4f9aa..862405ef3 100644 --- a/pkg/install/install.go +++ b/pkg/install/install.go @@ -36,8 +36,8 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/util/kube" ) // kindToResource translates a Kind (mixed case, singular) to a Resource (lowercase, plural) string. diff --git a/pkg/install/install_test.go b/pkg/install/install_test.go index 47a9aa273..5f2045ae5 100644 --- a/pkg/install/install_test.go +++ b/pkg/install/install_test.go @@ -21,8 +21,8 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "sigs.k8s.io/controller-runtime/pkg/client/fake" - v1crds "github.com/vmware-tanzu/velero/config/crd/v1/crds" - "github.com/vmware-tanzu/velero/pkg/test" + v1crds "github.com/velero-io/velero/config/crd/v1/crds" + "github.com/velero-io/velero/pkg/test" ) func TestInstall(t *testing.T) { diff --git a/pkg/install/resources.go b/pkg/install/resources.go index 5c7534774..89eba79ba 100644 --- a/pkg/install/resources.go +++ b/pkg/install/resources.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1crds "github.com/vmware-tanzu/velero/config/crd/v1/crds" - v2alpha1crds "github.com/vmware-tanzu/velero/config/crd/v2alpha1/crds" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/kube" + v1crds "github.com/velero-io/velero/config/crd/v1/crds" + v2alpha1crds "github.com/velero-io/velero/config/crd/v2alpha1/crds" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/itemblock/actions/pod_action.go b/pkg/itemblock/actions/pod_action.go index 2596e78a2..421e4a7c1 100644 --- a/pkg/itemblock/actions/pod_action.go +++ b/pkg/itemblock/actions/pod_action.go @@ -22,9 +22,9 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) // PodAction implements ItemBlockAction. diff --git a/pkg/itemblock/actions/pod_action_test.go b/pkg/itemblock/actions/pod_action_test.go index 645feeee2..c6cc34799 100644 --- a/pkg/itemblock/actions/pod_action_test.go +++ b/pkg/itemblock/actions/pod_action_test.go @@ -23,9 +23,9 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestPodActionAppliesTo(t *testing.T) { diff --git a/pkg/itemblock/actions/pvc_action.go b/pkg/itemblock/actions/pvc_action.go index 6777ef566..0b95307f5 100644 --- a/pkg/itemblock/actions/pvc_action.go +++ b/pkg/itemblock/actions/pvc_action.go @@ -25,13 +25,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" - "github.com/vmware-tanzu/velero/pkg/util/kube" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/kuberesource" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" + "github.com/velero-io/velero/pkg/util/kube" ) // PVCAction inspects a PersistentVolumeClaim for the PersistentVolume diff --git a/pkg/itemblock/actions/pvc_action_test.go b/pkg/itemblock/actions/pvc_action_test.go index 8b3cf58d5..4e4f16ec4 100644 --- a/pkg/itemblock/actions/pvc_action_test.go +++ b/pkg/itemblock/actions/pvc_action_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBackupPVAction(t *testing.T) { diff --git a/pkg/itemblock/actions/service_account_action.go b/pkg/itemblock/actions/service_account_action.go index 91cdbbe59..743299f95 100644 --- a/pkg/itemblock/actions/service_account_action.go +++ b/pkg/itemblock/actions/service_account_action.go @@ -22,10 +22,10 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) // ServiceAccountAction implements ItemBlockAction. diff --git a/pkg/itemblock/actions/service_account_action_test.go b/pkg/itemblock/actions/service_account_action_test.go index 01106b215..d357c9df3 100644 --- a/pkg/itemblock/actions/service_account_action_test.go +++ b/pkg/itemblock/actions/service_account_action_test.go @@ -28,10 +28,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/actionhelpers" ) func newV1ClusterRoleBindingList(rbacCRBList []rbacv1.ClusterRoleBinding) []actionhelpers.ClusterRoleBinding { diff --git a/pkg/itemoperation/backup_operation.go b/pkg/itemoperation/backup_operation.go index 84b207a3b..14ee9e88d 100644 --- a/pkg/itemoperation/backup_operation.go +++ b/pkg/itemoperation/backup_operation.go @@ -17,7 +17,7 @@ limitations under the License. package itemoperation import ( - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // BackupOperation stores information about an async item operation diff --git a/pkg/itemoperation/restore_operation.go b/pkg/itemoperation/restore_operation.go index d639d4b23..f2162d166 100644 --- a/pkg/itemoperation/restore_operation.go +++ b/pkg/itemoperation/restore_operation.go @@ -17,7 +17,7 @@ limitations under the License. package itemoperation import ( - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // RestoreOperation stores information about an async item operation diff --git a/pkg/itemoperationmap/backup_operation_map.go b/pkg/itemoperationmap/backup_operation_map.go index 47cdcac81..47663d64d 100644 --- a/pkg/itemoperationmap/backup_operation_map.go +++ b/pkg/itemoperationmap/backup_operation_map.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/util/encode" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/util/encode" ) type BackupItemOperationsMap struct { diff --git a/pkg/itemoperationmap/restore_operation_map.go b/pkg/itemoperationmap/restore_operation_map.go index 4256591bc..5bc35bb67 100644 --- a/pkg/itemoperationmap/restore_operation_map.go +++ b/pkg/itemoperationmap/restore_operation_map.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/persistence" - "github.com/vmware-tanzu/velero/pkg/util/encode" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/persistence" + "github.com/velero-io/velero/pkg/util/encode" ) type RestoreItemOperationsMap struct { diff --git a/pkg/kopia/kopia_log_test.go b/pkg/kopia/kopia_log_test.go index bb03a89cc..efc8e9fc9 100644 --- a/pkg/kopia/kopia_log_test.go +++ b/pkg/kopia/kopia_log_test.go @@ -24,7 +24,7 @@ import ( "github.com/stretchr/testify/require" "go.uber.org/zap/zapcore" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/test" ) func TestEnabled(t *testing.T) { diff --git a/pkg/label/label.go b/pkg/label/label.go index bfd28b836..2b97060aa 100644 --- a/pkg/label/label.go +++ b/pkg/label/label.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/apimachinery/pkg/util/validation" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // GetValidName converts an input string to valid Kubernetes label string in accordance to rfc1035 DNS Label spec diff --git a/pkg/nodeagent/node_agent.go b/pkg/nodeagent/node_agent.go index 87efb896a..23ecaec01 100644 --- a/pkg/nodeagent/node_agent.go +++ b/pkg/nodeagent/node_agent.go @@ -29,8 +29,8 @@ import ( "k8s.io/client-go/kubernetes" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/nodeagent/node_agent_test.go b/pkg/nodeagent/node_agent_test.go index 168e91de1..704c92876 100644 --- a/pkg/nodeagent/node_agent_test.go +++ b/pkg/nodeagent/node_agent_test.go @@ -30,9 +30,9 @@ import ( clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/builder" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/kube" ) type reactor struct { diff --git a/pkg/persistence/mocks/backup_store.go b/pkg/persistence/mocks/backup_store.go index b9c4184c3..b8392c242 100644 --- a/pkg/persistence/mocks/backup_store.go +++ b/pkg/persistence/mocks/backup_store.go @@ -21,15 +21,15 @@ import ( io "io" mock "github.com/stretchr/testify/mock" - itemoperation "github.com/vmware-tanzu/velero/pkg/itemoperation" + itemoperation "github.com/velero-io/velero/pkg/itemoperation" - persistence "github.com/vmware-tanzu/velero/pkg/persistence" + persistence "github.com/velero-io/velero/pkg/persistence" - results "github.com/vmware-tanzu/velero/pkg/util/results" + results "github.com/velero-io/velero/pkg/util/results" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - volume "github.com/vmware-tanzu/velero/internal/volume" + volume "github.com/velero-io/velero/internal/volume" volumesnapshotv1 "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumesnapshot/v1" ) diff --git a/pkg/persistence/object_store.go b/pkg/persistence/object_store.go index fd441e943..22a91b3b5 100644 --- a/pkg/persistence/object_store.go +++ b/pkg/persistence/object_store.go @@ -30,13 +30,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/serializer" kerrors "k8s.io/apimachinery/pkg/util/errors" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/results" ) type BackupInfo struct { diff --git a/pkg/persistence/object_store_test.go b/pkg/persistence/object_store_test.go index e9a3bde36..5f08d4cd7 100644 --- a/pkg/persistence/object_store_test.go +++ b/pkg/persistence/object_store_test.go @@ -33,17 +33,17 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/encode" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/encode" + "github.com/velero-io/velero/pkg/util/results" ) type objectBackupStoreTestHarness struct { diff --git a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go index 4bc28e487..457eff760 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go @@ -20,11 +20,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" ) // AdaptedBackupItemAction is a backup item action adapted to the v1 BackupItemAction API diff --git a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go index 8dc113df5..75711d401 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/internal/restartabletest" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v1" + "github.com/velero-io/velero/internal/restartabletest" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v1" ) func TestRestartableGetBackupItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go index 84ddb54b2..d3f2dd35e 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go @@ -20,12 +20,12 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" ) // AdaptedBackupItemAction is a v1 BackupItemAction adapted to implement the v2 API diff --git a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go index bd1ee0ec2..649ee0fcb 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/internal/restartabletest" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocksv2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + "github.com/velero-io/velero/internal/restartabletest" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + mocksv2 "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" ) func TestRestartableGetBackupItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go index 83742978f..9d69330c2 100644 --- a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go +++ b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go @@ -20,11 +20,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" ) // AdaptedItemBlockAction is an ItemBlock action adapted to the v1 ItemBlockAction API diff --git a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go index 04dd60652..a4c18c3fd 100644 --- a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go +++ b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/internal/restartabletest" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/itemblockaction/v1" + "github.com/velero-io/velero/internal/restartabletest" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/itemblockaction/v1" ) func TestRestartableGetItemBlockAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/manager.go b/pkg/plugin/clientmgmt/manager.go index 1c895d86e..747591c18 100644 --- a/pkg/plugin/clientmgmt/manager.go +++ b/pkg/plugin/clientmgmt/manager.go @@ -24,21 +24,21 @@ import ( "github.com/sirupsen/logrus" - biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - biav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v2" - ibav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/itemblockaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - riav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" - vsv1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + biav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v2" + ibav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + riav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" + vsv1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // Manager manages the lifecycles of plugins. diff --git a/pkg/plugin/clientmgmt/manager_test.go b/pkg/plugin/clientmgmt/manager_test.go index 7576c42c5..296bfa21f 100644 --- a/pkg/plugin/clientmgmt/manager_test.go +++ b/pkg/plugin/clientmgmt/manager_test.go @@ -26,17 +26,17 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/internal/restartabletest" - biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - biav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v2" - ibav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/itemblockaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - riav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" - vsv1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/restartabletest" + biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + biav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v2" + ibav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + riav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" + vsv1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/test" ) type mockRegistry struct { diff --git a/pkg/plugin/clientmgmt/process/client_builder.go b/pkg/plugin/clientmgmt/process/client_builder.go index ceeac8db7..3e86c2862 100644 --- a/pkg/plugin/clientmgmt/process/client_builder.go +++ b/pkg/plugin/clientmgmt/process/client_builder.go @@ -26,11 +26,11 @@ import ( hcplugin "github.com/hashicorp/go-plugin" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework" + biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework/common" + ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" ) // clientBuilder builds go-plugin Clients. diff --git a/pkg/plugin/clientmgmt/process/client_builder_test.go b/pkg/plugin/clientmgmt/process/client_builder_test.go index 14278ae8f..daf1de42f 100644 --- a/pkg/plugin/clientmgmt/process/client_builder_test.go +++ b/pkg/plugin/clientmgmt/process/client_builder_test.go @@ -25,12 +25,12 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/framework" + biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework/common" + ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/test" ) func TestNewClientBuilder(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/process/process.go b/pkg/plugin/clientmgmt/process/process.go index 4d20a1784..e21221f06 100644 --- a/pkg/plugin/clientmgmt/process/process.go +++ b/pkg/plugin/clientmgmt/process/process.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/framework/common" ) type Factory interface { diff --git a/pkg/plugin/clientmgmt/process/process_test.go b/pkg/plugin/clientmgmt/process/process_test.go index e67de8db9..ef4138b08 100644 --- a/pkg/plugin/clientmgmt/process/process_test.go +++ b/pkg/plugin/clientmgmt/process/process_test.go @@ -23,8 +23,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" ) type mockClientProtocol struct { diff --git a/pkg/plugin/clientmgmt/process/registry.go b/pkg/plugin/clientmgmt/process/registry.go index 744048690..4e2e36cf7 100644 --- a/pkg/plugin/clientmgmt/process/registry.go +++ b/pkg/plugin/clientmgmt/process/registry.go @@ -25,9 +25,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/util/filesystem" ) // Registry manages information about available plugins. diff --git a/pkg/plugin/clientmgmt/process/registry_test.go b/pkg/plugin/clientmgmt/process/registry_test.go index e188419b2..02330fbd3 100644 --- a/pkg/plugin/clientmgmt/process/registry_test.go +++ b/pkg/plugin/clientmgmt/process/registry_test.go @@ -25,7 +25,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/test" ) func TestNewRegistry(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restartable_delete_item_action.go b/pkg/plugin/clientmgmt/restartable_delete_item_action.go index b566ede6f..c2a68a77f 100644 --- a/pkg/plugin/clientmgmt/restartable_delete_item_action.go +++ b/pkg/plugin/clientmgmt/restartable_delete_item_action.go @@ -19,9 +19,9 @@ package clientmgmt import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" ) // restartableDeleteItemAction is a delete item action for a given implementation (such as "pod"). It is associated with diff --git a/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go b/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go index 52edf7ffb..20722d2e8 100644 --- a/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go +++ b/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/restartabletest" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" + "github.com/velero-io/velero/internal/restartabletest" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero/mocks" ) func TestRestartableGetDeleteItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restartable_object_store.go b/pkg/plugin/clientmgmt/restartable_object_store.go index 6e66d4b3e..a37f4c47c 100644 --- a/pkg/plugin/clientmgmt/restartable_object_store.go +++ b/pkg/plugin/clientmgmt/restartable_object_store.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" ) // restartableObjectStore is an object store for a given implementation (such as "aws"). It is associated with diff --git a/pkg/plugin/clientmgmt/restartable_object_store_test.go b/pkg/plugin/clientmgmt/restartable_object_store_test.go index 0b25e02d8..a334f70f5 100644 --- a/pkg/plugin/clientmgmt/restartable_object_store_test.go +++ b/pkg/plugin/clientmgmt/restartable_object_store_test.go @@ -26,10 +26,10 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/internal/restartabletest" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" + "github.com/velero-io/velero/internal/restartabletest" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks" ) func TestRestartableGetObjectStore(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go index a03ccecd2..4e07fa1cb 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go @@ -19,10 +19,10 @@ package v1 import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" ) // AdaptedRestoreItemAction is a restore item action adapted to the v1 RestoreItemAction API diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go index 08239fc93..f2554fd92 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/restartabletest" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v1" + "github.com/velero-io/velero/internal/restartabletest" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v1" ) func TestRestartableGetRestoreItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go index c23787cfb..9989f0d70 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go @@ -19,12 +19,12 @@ package v2 import ( "github.com/pkg/errors" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" ) // AdaptedRestoreItemAction is a v1 RestoreItemAction adapted to implement the v2 API diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go index af6521e43..bde2eb2ed 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/restartabletest" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" + "github.com/velero-io/velero/internal/restartabletest" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" ) func TestRestartableGetRestoreItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go index 7aec39872..dd26aa7f2 100644 --- a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go +++ b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go @@ -20,9 +20,9 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // AdaptedVolumeSnapshotter is a volume snapshotter adapted to the v1 VolumeSnapshotter API diff --git a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go index 8a2efe04c..4ff59d66f 100644 --- a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go +++ b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/restartabletest" - "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" + "github.com/velero-io/velero/internal/restartabletest" + "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + "github.com/velero-io/velero/pkg/plugin/framework/common" + providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" ) func TestRestartableGetVolumeSnapshotter(t *testing.T) { diff --git a/pkg/plugin/framework/action_resolver.go b/pkg/plugin/framework/action_resolver.go index ac8a0b1d0..b3db6a12c 100644 --- a/pkg/plugin/framework/action_resolver.go +++ b/pkg/plugin/framework/action_resolver.go @@ -23,14 +23,14 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/plugin/velero" + biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/util/collections" ) /* diff --git a/pkg/plugin/framework/action_resolver_test.go b/pkg/plugin/framework/action_resolver_test.go index cf0e411da..104682bd4 100644 --- a/pkg/plugin/framework/action_resolver_test.go +++ b/pkg/plugin/framework/action_resolver_test.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) type mockApplicable struct { diff --git a/pkg/plugin/framework/backup_item_action.go b/pkg/plugin/framework/backup_item_action.go index 9c1a5665d..ea17b0639 100644 --- a/pkg/plugin/framework/backup_item_action.go +++ b/pkg/plugin/framework/backup_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protobiav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protobiav1 "github.com/velero-io/velero/pkg/plugin/generated" ) // BackupItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/backup_item_action_client.go b/pkg/plugin/framework/backup_item_action_client.go index 724737d01..1ea17fc8d 100644 --- a/pkg/plugin/framework/backup_item_action_client.go +++ b/pkg/plugin/framework/backup_item_action_client.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protobiav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protobiav1 "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" ) // NewBackupItemActionPlugin constructs a BackupItemActionPlugin. diff --git a/pkg/plugin/framework/backup_item_action_server.go b/pkg/plugin/framework/backup_item_action_server.go index 7c18b4ef6..047e49abb 100644 --- a/pkg/plugin/framework/backup_item_action_server.go +++ b/pkg/plugin/framework/backup_item_action_server.go @@ -24,11 +24,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" + biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" ) // BackupItemActionGRPCServer implements the proto-generated BackupItemAction interface, and accepts diff --git a/pkg/plugin/framework/backup_item_action_test.go b/pkg/plugin/framework/backup_item_action_test.go index 1472eb115..982a47c8e 100644 --- a/pkg/plugin/framework/backup_item_action_test.go +++ b/pkg/plugin/framework/backup_item_action_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBackupItemActionGRPCServerExecute(t *testing.T) { diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go index 903ec378c..68d969b62 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" ) // BackupItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go index 64695dbe3..9dd4090de 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/velero" ) // NewBackupItemActionPlugin constructs a BackupItemActionPlugin. diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go index f8c894eba..b95168968 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go @@ -27,12 +27,12 @@ import ( timestamppb "google.golang.org/protobuf/types/known/timestamppb" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/velero" + biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" ) // BackupItemActionGRPCServer implements the proto-generated BackupItemAction interface, and accepts diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go index 502c37502..ba630554d 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go @@ -27,13 +27,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestBackupItemActionGRPCServerExecute(t *testing.T) { diff --git a/pkg/plugin/framework/common/client_dispenser_test.go b/pkg/plugin/framework/common/client_dispenser_test.go index 3aa0cd299..3441cc648 100644 --- a/pkg/plugin/framework/common/client_dispenser_test.go +++ b/pkg/plugin/framework/common/client_dispenser_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/require" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/test" ) type fakeClient struct { diff --git a/pkg/plugin/framework/common/client_errors.go b/pkg/plugin/framework/common/client_errors.go index 1d9e6c22f..7a452ec5b 100644 --- a/pkg/plugin/framework/common/client_errors.go +++ b/pkg/plugin/framework/common/client_errors.go @@ -19,7 +19,7 @@ package common import ( "google.golang.org/grpc/status" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // FromGRPCError takes a gRPC status error, extracts a stack trace diff --git a/pkg/plugin/framework/common/plugin_base_test.go b/pkg/plugin/framework/common/plugin_base_test.go index e9d5ec2e2..f4d48de9c 100644 --- a/pkg/plugin/framework/common/plugin_base_test.go +++ b/pkg/plugin/framework/common/plugin_base_test.go @@ -20,7 +20,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/test" ) func TestClientLogger(t *testing.T) { diff --git a/pkg/plugin/framework/common/plugin_config_test.go b/pkg/plugin/framework/common/plugin_config_test.go index 53cb0fb8f..ec5ef9ef5 100644 --- a/pkg/plugin/framework/common/plugin_config_test.go +++ b/pkg/plugin/framework/common/plugin_config_test.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestGetPluginConfig(t *testing.T) { diff --git a/pkg/plugin/framework/common/server_errors.go b/pkg/plugin/framework/common/server_errors.go index 60eff50f4..20ea63893 100644 --- a/pkg/plugin/framework/common/server_errors.go +++ b/pkg/plugin/framework/common/server_errors.go @@ -22,8 +22,8 @@ import ( "google.golang.org/grpc/status" "google.golang.org/protobuf/protoadapt" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/util/logging" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/util/logging" ) // NewGRPCErrorWithCode wraps err in a gRPC status error with the error's stack trace diff --git a/pkg/plugin/framework/delete_item_action.go b/pkg/plugin/framework/delete_item_action.go index db4329b7f..8ef51f06d 100644 --- a/pkg/plugin/framework/delete_item_action.go +++ b/pkg/plugin/framework/delete_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // DeleteItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/delete_item_action_client.go b/pkg/plugin/framework/delete_item_action_client.go index bec5088db..b8ca2d7b8 100644 --- a/pkg/plugin/framework/delete_item_action_client.go +++ b/pkg/plugin/framework/delete_item_action_client.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" ) var _ velero.DeleteItemAction = &DeleteItemActionGRPCClient{} diff --git a/pkg/plugin/framework/delete_item_action_server.go b/pkg/plugin/framework/delete_item_action_server.go index 01abe8dc3..154ec3452 100644 --- a/pkg/plugin/framework/delete_item_action_server.go +++ b/pkg/plugin/framework/delete_item_action_server.go @@ -24,10 +24,10 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" ) // DeleteItemActionGRPCServer implements the proto-generated DeleteItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/examples_test.go b/pkg/plugin/framework/examples_test.go index 41bb8395e..e750be8f4 100644 --- a/pkg/plugin/framework/examples_test.go +++ b/pkg/plugin/framework/examples_test.go @@ -20,7 +20,7 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) func ExampleNewServer_volumeSnapshotter() { diff --git a/pkg/plugin/framework/import_test.go b/pkg/plugin/framework/import_test.go index ee1439329..18aa0db91 100644 --- a/pkg/plugin/framework/import_test.go +++ b/pkg/plugin/framework/import_test.go @@ -13,7 +13,7 @@ import ( // test that this package do not import cloud provider -// Prevent https://github.com/vmware-tanzu/velero/issues/8207 and https://github.com/vmware-tanzu/velero/issues/8157 +// Prevent https://github.com/velero-io/velero/issues/8207 and https://github.com/velero-io/velero/issues/8157 func TestPkgImportNoCloudProvider(t *testing.T) { _, filename, _, ok := runtime.Caller(0) if !ok { diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action.go index 2115d2ecf..8e7852126 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" ) // ItemBlockActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go index aa597c4af..f1a056f93 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // NewItemBlockActionPlugin constructs a ItemBlockActionPlugin. diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go index 2d940550c..51c5e429e 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go @@ -24,12 +24,12 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" ) // ItemBlockActionGRPCServer implements the proto-generated ItemBlockAction interface, and accepts diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go index 6e2a0e4d5..045e8d5a7 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go @@ -26,13 +26,13 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/itemblockaction/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/itemblockaction/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestItemBlockActionGRPCServerGetRelatedItems(t *testing.T) { diff --git a/pkg/plugin/framework/logger.go b/pkg/plugin/framework/logger.go index b7f13e4af..22ac4f187 100644 --- a/pkg/plugin/framework/logger.go +++ b/pkg/plugin/framework/logger.go @@ -19,7 +19,7 @@ package framework import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/logging" ) // newLogger returns a logger that is suitable for use within an diff --git a/pkg/plugin/framework/logger_test.go b/pkg/plugin/framework/logger_test.go index 7e9ba7bf2..7899da35e 100644 --- a/pkg/plugin/framework/logger_test.go +++ b/pkg/plugin/framework/logger_test.go @@ -21,7 +21,7 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/logging" ) func TestNewLogger(t *testing.T) { diff --git a/pkg/plugin/framework/object_store.go b/pkg/plugin/framework/object_store.go index ea624da42..647295a4a 100644 --- a/pkg/plugin/framework/object_store.go +++ b/pkg/plugin/framework/object_store.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // ObjectStorePlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/object_store_client.go b/pkg/plugin/framework/object_store_client.go index b59f3d1b0..b44c06668 100644 --- a/pkg/plugin/framework/object_store_client.go +++ b/pkg/plugin/framework/object_store_client.go @@ -25,8 +25,8 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) const byteChunkSize = 16384 diff --git a/pkg/plugin/framework/object_store_server.go b/pkg/plugin/framework/object_store_server.go index fbed21ecf..1dc54688d 100644 --- a/pkg/plugin/framework/object_store_server.go +++ b/pkg/plugin/framework/object_store_server.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" ) // ObjectStoreGRPCServer implements the proto-generated ObjectStoreServer interface, and accepts diff --git a/pkg/plugin/framework/plugin_lister.go b/pkg/plugin/framework/plugin_lister.go index 6db81c66d..d58b802d6 100644 --- a/pkg/plugin/framework/plugin_lister.go +++ b/pkg/plugin/framework/plugin_lister.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // PluginIdentifier uniquely identifies a plugin by command, kind, and name. diff --git a/pkg/plugin/framework/restore_item_action.go b/pkg/plugin/framework/restore_item_action.go index 26cef3728..a0cfa0b0f 100644 --- a/pkg/plugin/framework/restore_item_action.go +++ b/pkg/plugin/framework/restore_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // RestoreItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/restore_item_action_client.go b/pkg/plugin/framework/restore_item_action_client.go index 3a5a633f3..a902417a1 100644 --- a/pkg/plugin/framework/restore_item_action_client.go +++ b/pkg/plugin/framework/restore_item_action_client.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" + riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" ) var _ riav1.RestoreItemAction = &RestoreItemActionGRPCClient{} diff --git a/pkg/plugin/framework/restore_item_action_server.go b/pkg/plugin/framework/restore_item_action_server.go index 175a941bd..14a90f02e 100644 --- a/pkg/plugin/framework/restore_item_action_server.go +++ b/pkg/plugin/framework/restore_item_action_server.go @@ -24,11 +24,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/velero" + riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" ) // RestoreItemActionGRPCServer implements the proto-generated RestoreItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go index 00bb825b8..606f04cdf 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" ) // RestoreItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go index 5e2f01c37..40668d4c3 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" ) var _ riav2.RestoreItemAction = &RestoreItemActionGRPCClient{} diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go index 115961656..6a9302080 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go @@ -28,12 +28,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" ) // RestoreItemActionGRPCServer implements the proto-generated RestoreItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/server.go b/pkg/plugin/framework/server.go index 923210d55..58d184709 100644 --- a/pkg/plugin/framework/server.go +++ b/pkg/plugin/framework/server.go @@ -24,11 +24,11 @@ import ( "github.com/sirupsen/logrus" "github.com/spf13/pflag" - "github.com/vmware-tanzu/velero/pkg/cmd/server/config" - biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/velero-io/velero/pkg/cmd/server/config" + biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/velero-io/velero/pkg/plugin/framework/common" + ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" ) // Server serves registered plugin implementations. diff --git a/pkg/plugin/framework/volume_snapshotter.go b/pkg/plugin/framework/volume_snapshotter.go index 8cbb48fa4..b54955c11 100644 --- a/pkg/plugin/framework/volume_snapshotter.go +++ b/pkg/plugin/framework/volume_snapshotter.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // VolumeSnapshotterPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/volume_snapshotter_client.go b/pkg/plugin/framework/volume_snapshotter_client.go index f7af07ce4..6af01e37d 100644 --- a/pkg/plugin/framework/volume_snapshotter_client.go +++ b/pkg/plugin/framework/volume_snapshotter_client.go @@ -26,8 +26,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" ) // NewVolumeSnapshotterPlugin constructs a VolumeSnapshotterPlugin. diff --git a/pkg/plugin/framework/volume_snapshotter_server.go b/pkg/plugin/framework/volume_snapshotter_server.go index de30c823f..95050afb8 100644 --- a/pkg/plugin/framework/volume_snapshotter_server.go +++ b/pkg/plugin/framework/volume_snapshotter_server.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/plugin/framework/common" + proto "github.com/velero-io/velero/pkg/plugin/generated" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // VolumeSnapshotterGRPCServer implements the proto-generated VolumeSnapshotterServer interface, and accepts diff --git a/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go b/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go index 5eb2c852b..3c8f740d1 100644 --- a/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go +++ b/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go @@ -7,7 +7,7 @@ package v2 import ( - generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" + generated "github.com/velero-io/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" emptypb "google.golang.org/protobuf/types/known/emptypb" diff --git a/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go b/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go index cec604477..ffa395a39 100644 --- a/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go +++ b/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go @@ -7,7 +7,7 @@ package v1 import ( - generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" + generated "github.com/velero-io/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" reflect "reflect" diff --git a/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go b/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go index a7bbc421e..0063e6158 100644 --- a/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go +++ b/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go @@ -7,7 +7,7 @@ package v2 import ( - generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" + generated "github.com/velero-io/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" durationpb "google.golang.org/protobuf/types/known/durationpb" diff --git a/pkg/plugin/mocks/manager.go b/pkg/plugin/mocks/manager.go index c12510fdd..0c2219dc0 100644 --- a/pkg/plugin/mocks/manager.go +++ b/pkg/plugin/mocks/manager.go @@ -4,19 +4,19 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - itemblockactionv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + itemblockactionv1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - restoreitemactionv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + restoreitemactionv1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" - restoreitemactionv2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + restoreitemactionv2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - v1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" + v1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" - v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" - volumesnapshotterv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + volumesnapshotterv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // Manager is an autogenerated mock type for the Manager type diff --git a/pkg/plugin/mocks/process_factory.go b/pkg/plugin/mocks/process_factory.go index 586e31121..5325a6a9f 100644 --- a/pkg/plugin/mocks/process_factory.go +++ b/pkg/plugin/mocks/process_factory.go @@ -21,7 +21,7 @@ import ( logrus "github.com/sirupsen/logrus" mock "github.com/stretchr/testify/mock" - process "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + process "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" ) // ProcessFactory is an autogenerated mock type for the ProcessFactory type diff --git a/pkg/plugin/proto/BackupItemAction.proto b/pkg/plugin/proto/BackupItemAction.proto index 66111300a..5d89e2a87 100644 --- a/pkg/plugin/proto/BackupItemAction.proto +++ b/pkg/plugin/proto/BackupItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/DeleteItemAction.proto b/pkg/plugin/proto/DeleteItemAction.proto index f2838fe0c..34c1924c9 100644 --- a/pkg/plugin/proto/DeleteItemAction.proto +++ b/pkg/plugin/proto/DeleteItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/ObjectStore.proto b/pkg/plugin/proto/ObjectStore.proto index 4487a0cef..49e493789 100644 --- a/pkg/plugin/proto/ObjectStore.proto +++ b/pkg/plugin/proto/ObjectStore.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/PluginLister.proto b/pkg/plugin/proto/PluginLister.proto index 55cfe62de..d2300924d 100644 --- a/pkg/plugin/proto/PluginLister.proto +++ b/pkg/plugin/proto/PluginLister.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/RestoreItemAction.proto b/pkg/plugin/proto/RestoreItemAction.proto index ae9c3ddd9..57ca235a4 100644 --- a/pkg/plugin/proto/RestoreItemAction.proto +++ b/pkg/plugin/proto/RestoreItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/Shared.proto b/pkg/plugin/proto/Shared.proto index dd12a7ee7..d59f548af 100644 --- a/pkg/plugin/proto/Shared.proto +++ b/pkg/plugin/proto/Shared.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "google/protobuf/timestamp.proto"; diff --git a/pkg/plugin/proto/VolumeSnapshotter.proto b/pkg/plugin/proto/VolumeSnapshotter.proto index affb762bc..36da5b704 100644 --- a/pkg/plugin/proto/VolumeSnapshotter.proto +++ b/pkg/plugin/proto/VolumeSnapshotter.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto b/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto index 36f067fe2..8479d7f42 100644 --- a/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto +++ b/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v2; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2"; import "Shared.proto"; import "google/protobuf/empty.proto"; diff --git a/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto b/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto index 5c0f86a3d..71b350044 100644 --- a/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto +++ b/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v1; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1"; import "Shared.proto"; diff --git a/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto b/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto index a3e969114..614544025 100644 --- a/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto +++ b/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v2; -option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2"; +option go_package = "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2"; import "Shared.proto"; import "google/protobuf/empty.proto"; diff --git a/pkg/plugin/utils/volumehelper/volume_policy_helper.go b/pkg/plugin/utils/volumehelper/volume_policy_helper.go index 843c23b06..84675cafb 100644 --- a/pkg/plugin/utils/volumehelper/volume_policy_helper.go +++ b/pkg/plugin/utils/volumehelper/volume_policy_helper.go @@ -22,12 +22,12 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - "github.com/vmware-tanzu/velero/internal/volumehelper" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" - vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" + "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/volumehelper" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/boolptr" + podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" + vhutil "github.com/velero-io/velero/pkg/util/volumehelper" ) // ShouldPerformSnapshotWithBackup is used for third-party plugins. diff --git a/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go b/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go index 08b23ae04..cebc4641e 100644 --- a/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go +++ b/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/internal/volumehelper" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/volumehelper" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestShouldPerformSnapshotWithBackup(t *testing.T) { diff --git a/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go b/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go index 35566d98a..0a823e3ca 100644 --- a/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go +++ b/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go @@ -19,8 +19,8 @@ package v1 import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // BackupItemAction is an actor that performs an operation on an individual item being backed up. diff --git a/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go b/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go index 3c23802f2..4566eafd6 100644 --- a/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go +++ b/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // BackupItemAction is an actor that performs an operation on an individual item being backed up. diff --git a/pkg/plugin/velero/delete_item_action.go b/pkg/plugin/velero/delete_item_action.go index e3e7d9259..afd8ebbb2 100644 --- a/pkg/plugin/velero/delete_item_action.go +++ b/pkg/plugin/velero/delete_item_action.go @@ -19,7 +19,7 @@ package velero import ( "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // DeleteItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/plugin/velero/itemblockaction/v1/item_block_action.go b/pkg/plugin/velero/itemblockaction/v1/item_block_action.go index 6d0133700..c8d6e020c 100644 --- a/pkg/plugin/velero/itemblockaction/v1/item_block_action.go +++ b/pkg/plugin/velero/itemblockaction/v1/item_block_action.go @@ -19,8 +19,8 @@ package v1 import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // ItemBlockAction is an action that returns a list of related items that must be backed up diff --git a/pkg/plugin/velero/mocks/DeleteItemAction.go b/pkg/plugin/velero/mocks/DeleteItemAction.go index 101e04fde..c75eb32e9 100644 --- a/pkg/plugin/velero/mocks/DeleteItemAction.go +++ b/pkg/plugin/velero/mocks/DeleteItemAction.go @@ -4,7 +4,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" ) // DeleteItemAction is an autogenerated mock type for the DeleteItemAction type diff --git a/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go b/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go index cfca2ef6d..d6fba5904 100644 --- a/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go +++ b/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) // BackupItemAction is an autogenerated mock type for the BackupItemAction type diff --git a/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go b/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go index 426442477..e30ffeb67 100644 --- a/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go +++ b/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" ) // BackupItemAction is an autogenerated mock type for the BackupItemAction type diff --git a/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go b/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go index 95a8d960a..b07bb63f4 100644 --- a/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go +++ b/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) // ItemBlockAction is an autogenerated mock type for the ItemBlockAction type diff --git a/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go b/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go index 1bacf7b16..bd4b7d56d 100644 --- a/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go +++ b/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go @@ -19,7 +19,7 @@ package v1 import ( mock "github.com/stretchr/testify/mock" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" ) // RestoreItemAction is an autogenerated mock type for the RestoreItemAction type diff --git a/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go b/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go index 647e8b6dc..18b4af19d 100644 --- a/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go +++ b/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go @@ -19,9 +19,9 @@ package v2 import ( mock "github.com/stretchr/testify/mock" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velero "github.com/velero-io/velero/pkg/plugin/velero" ) // RestoreItemAction is an autogenerated mock type for the RestoreItemAction type diff --git a/pkg/plugin/velero/restore_item_action_shared.go b/pkg/plugin/velero/restore_item_action_shared.go index a8e285b0c..27f3d0622 100644 --- a/pkg/plugin/velero/restore_item_action_shared.go +++ b/pkg/plugin/velero/restore_item_action_shared.go @@ -21,7 +21,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // RestoreItemActionExecuteInput contains the input parameters for the ItemAction's Execute function. diff --git a/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go b/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go index 3398af9e1..ec316e789 100644 --- a/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go +++ b/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go @@ -17,7 +17,7 @@ limitations under the License. package v1 import ( - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // RestoreItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go b/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go index dfc35428f..8d66b6ef4 100644 --- a/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go +++ b/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go @@ -21,8 +21,8 @@ import ( "github.com/pkg/errors" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" ) // RestoreItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/podexec/pod_command_executor.go b/pkg/podexec/pod_command_executor.go index 0dbc28e95..94cda5ac3 100644 --- a/pkg/podexec/pod_command_executor.go +++ b/pkg/podexec/pod_command_executor.go @@ -31,7 +31,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/remotecommand" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" ) const defaultTimeout = 30 * time.Second diff --git a/pkg/podexec/pod_command_executor_test.go b/pkg/podexec/pod_command_executor_test.go index 3286ba42d..34878df70 100644 --- a/pkg/podexec/pod_command_executor_test.go +++ b/pkg/podexec/pod_command_executor_test.go @@ -37,8 +37,8 @@ import ( "k8s.io/client-go/tools/remotecommand" "k8s.io/utils/ptr" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestNewPodCommandExecutor(t *testing.T) { diff --git a/pkg/podvolume/backup_micro_service.go b/pkg/podvolume/backup_micro_service.go index 11ca66676..737f09255 100644 --- a/pkg/podvolume/backup_micro_service.go +++ b/pkg/podvolume/backup_micro_service.go @@ -31,12 +31,12 @@ import ( cachetool "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/cache" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/podvolume/backup_micro_service_test.go b/pkg/podvolume/backup_micro_service_test.go index a5b6cd1f4..98712874e 100644 --- a/pkg/podvolume/backup_micro_service_test.go +++ b/pkg/podvolume/backup_micro_service_test.go @@ -30,19 +30,19 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/uploader" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" ) type backupMsTestHelper struct { diff --git a/pkg/podvolume/backupper.go b/pkg/podvolume/backupper.go index 6b534d5ed..b680b79fc 100644 --- a/pkg/podvolume/backupper.go +++ b/pkg/podvolume/backupper.go @@ -30,17 +30,17 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/podvolume/configs" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/resourcepolicies" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + veleroclient "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/podvolume/configs" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + uploaderutil "github.com/velero-io/velero/pkg/uploader/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) const ( @@ -371,7 +371,7 @@ func (b *backupper) BackupPodVolumes(backup *velerov1api.Backup, pod *corev1api. continue } // similar with above: the PVB may be handled very quickly by the controller and the informer handler will call "b.wg.Done()" before "b.wg.Add(1)" runs which causes panic - // see https://github.com/vmware-tanzu/velero/issues/8657 + // see https://github.com/velero-io/velero/issues/8657 b.wg.Add(1) if err := veleroclient.CreateRetryGenerateName(b.crClient, b.ctx, volumeBackup); err != nil { b.wg.Done() @@ -397,7 +397,7 @@ func (b *backupper) WaitAllPodVolumesProcessed(log logrus.FieldLogger) []*velero var podVolumeBackups []*velerov1api.PodVolumeBackup // if no pod volume backups are tracked, return directly to avoid issue mentioned in - // https://github.com/vmware-tanzu/velero/issues/8723 + // https://github.com/velero-io/velero/issues/8723 if len(b.pvbIndexer.List()) == 0 { return podVolumeBackups } diff --git a/pkg/podvolume/backupper_factory.go b/pkg/podvolume/backupper_factory.go index f75f1d30b..64bdbeb60 100644 --- a/pkg/podvolume/backupper_factory.go +++ b/pkg/podvolume/backupper_factory.go @@ -25,8 +25,8 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" ) // BackupperFactory can construct pod volumes backuppers. diff --git a/pkg/podvolume/backupper_test.go b/pkg/podvolume/backupper_test.go index e6042ede1..45a32225a 100644 --- a/pkg/podvolume/backupper_test.go +++ b/pkg/podvolume/backupper_test.go @@ -36,11 +36,11 @@ import ( clientTesting "k8s.io/client-go/testing" "k8s.io/client-go/tools/cache" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/repository" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/resourcepolicies" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/repository" + velerotest "github.com/velero-io/velero/pkg/test" ) type fakeInformerRegistration struct{} diff --git a/pkg/podvolume/mocks/restorer.go b/pkg/podvolume/mocks/restorer.go index 56de97f44..eb0fd9f2e 100644 --- a/pkg/podvolume/mocks/restorer.go +++ b/pkg/podvolume/mocks/restorer.go @@ -4,9 +4,9 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - podvolume "github.com/vmware-tanzu/velero/pkg/podvolume" + podvolume "github.com/velero-io/velero/pkg/podvolume" - volume "github.com/vmware-tanzu/velero/internal/volume" + volume "github.com/velero-io/velero/internal/volume" ) // Restorer is an autogenerated mock type for the Restorer type diff --git a/pkg/podvolume/restore_micro_service.go b/pkg/podvolume/restore_micro_service.go index decf94b1b..8321158e0 100644 --- a/pkg/podvolume/restore_micro_service.go +++ b/pkg/podvolume/restore_micro_service.go @@ -32,12 +32,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/kube" cachetool "k8s.io/client-go/tools/cache" ) diff --git a/pkg/podvolume/restore_micro_service_test.go b/pkg/podvolume/restore_micro_service_test.go index 2c94ddf46..fbd9a4241 100644 --- a/pkg/podvolume/restore_micro_service_test.go +++ b/pkg/podvolume/restore_micro_service_test.go @@ -31,19 +31,19 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/datapath" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/datapath" + "github.com/velero-io/velero/pkg/uploader" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" ) diff --git a/pkg/podvolume/restorer.go b/pkg/podvolume/restorer.go index ce662d5de..89b054dc8 100644 --- a/pkg/podvolume/restorer.go +++ b/pkg/podvolume/restorer.go @@ -21,7 +21,7 @@ import ( "sync" "time" - "github.com/vmware-tanzu/velero/internal/volume" + "github.com/velero-io/velero/internal/volume" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -33,14 +33,14 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/nodeagent" - "github.com/vmware-tanzu/velero/pkg/repository" - uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + veleroclient "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/nodeagent" + "github.com/velero-io/velero/pkg/repository" + uploaderutil "github.com/velero-io/velero/pkg/uploader/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" ) type RestoreData struct { diff --git a/pkg/podvolume/restorer_factory.go b/pkg/podvolume/restorer_factory.go index 178d720c8..963230900 100644 --- a/pkg/podvolume/restorer_factory.go +++ b/pkg/podvolume/restorer_factory.go @@ -26,8 +26,8 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" ) // RestorerFactory can construct pod volumes restorers. diff --git a/pkg/podvolume/restorer_test.go b/pkg/podvolume/restorer_test.go index bd67e8480..687152ae7 100644 --- a/pkg/podvolume/restorer_test.go +++ b/pkg/podvolume/restorer_test.go @@ -33,11 +33,11 @@ import ( kubefake "k8s.io/client-go/kubernetes/fake" "k8s.io/client-go/tools/cache" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/repository" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/repository" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestGetVolumesRepositoryType(t *testing.T) { diff --git a/pkg/podvolume/snaphost_tracker_test.go b/pkg/podvolume/snaphost_tracker_test.go index 0f89eb903..973d1503b 100644 --- a/pkg/podvolume/snaphost_tracker_test.go +++ b/pkg/podvolume/snaphost_tracker_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/velero-io/velero/pkg/builder" ) func TestOptoutVolume(t *testing.T) { diff --git a/pkg/podvolume/util.go b/pkg/podvolume/util.go index bb827c732..0f1fd5ad7 100644 --- a/pkg/podvolume/util.go +++ b/pkg/podvolume/util.go @@ -23,10 +23,10 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/podvolume/configs" - repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" - "github.com/vmware-tanzu/velero/pkg/uploader" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/podvolume/configs" + repotypes "github.com/velero-io/velero/pkg/repository/types" + "github.com/velero-io/velero/pkg/uploader" ) const ( @@ -87,8 +87,8 @@ func getVolumeBackupInfoForPod(podVolumeBackups []*velerov1api.PodVolumeBackup, } // If the volume came from a projected or DownwardAPI source, skip its restore. - // This allows backups affected by https://github.com/vmware-tanzu/velero/issues/3863 - // or https://github.com/vmware-tanzu/velero/issues/4053 to be restored successfully. + // This allows backups affected by https://github.com/velero-io/velero/issues/3863 + // or https://github.com/velero-io/velero/issues/4053 to be restored successfully. if volumeHasNonRestorableSource(pvb.Spec.Volume, pod.Spec.Volumes) { continue } diff --git a/pkg/podvolume/util_test.go b/pkg/podvolume/util_test.go index bfd33e55e..6fd86bee6 100644 --- a/pkg/podvolume/util_test.go +++ b/pkg/podvolume/util_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" ) func TestGetVolumeBackupsForPod(t *testing.T) { diff --git a/pkg/repository/backup_repo_op.go b/pkg/repository/backup_repo_op.go index 36356e7af..011abffd0 100644 --- a/pkg/repository/backup_repo_op.go +++ b/pkg/repository/backup_repo_op.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/labels" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/label" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/label" ) // A BackupRepositoryKey uniquely identify a backup repository diff --git a/pkg/repository/backup_repo_op_test.go b/pkg/repository/backup_repo_op_test.go index de53cfbe7..b50e26e4e 100644 --- a/pkg/repository/backup_repo_op_test.go +++ b/pkg/repository/backup_repo_op_test.go @@ -29,9 +29,9 @@ import ( "github.com/stretchr/testify/require" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func buildBackupRepo(key BackupRepositoryKey, phase velerov1api.BackupRepositoryPhase, seqNum string) velerov1api.BackupRepository { diff --git a/pkg/repository/config/azure.go b/pkg/repository/config/azure.go index 6662d13c6..044700f31 100644 --- a/pkg/repository/config/azure.go +++ b/pkg/repository/config/azure.go @@ -19,7 +19,7 @@ package config import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/util/azure" + "github.com/velero-io/velero/pkg/util/azure" ) // GetAzureResticEnvVars gets the environment variables that restic diff --git a/pkg/repository/config/azure_test.go b/pkg/repository/config/azure_test.go index 605987d37..b76b22edb 100644 --- a/pkg/repository/config/azure_test.go +++ b/pkg/repository/config/azure_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/util/azure" + "github.com/velero-io/velero/pkg/util/azure" ) func TestGetAzureResticEnvVars(t *testing.T) { diff --git a/pkg/repository/ensurer.go b/pkg/repository/ensurer.go index 91cdb0d9e..f399b2437 100644 --- a/pkg/repository/ensurer.go +++ b/pkg/repository/ensurer.go @@ -27,7 +27,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/repository/ensurer_test.go b/pkg/repository/ensurer_test.go index b2d60eb21..8b8b4b81d 100644 --- a/pkg/repository/ensurer_test.go +++ b/pkg/repository/ensurer_test.go @@ -26,8 +26,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestEnsureRepo(t *testing.T) { diff --git a/pkg/repository/keys/keys.go b/pkg/repository/keys/keys.go index 21423afe0..eebd10613 100644 --- a/pkg/repository/keys/keys.go +++ b/pkg/repository/keys/keys.go @@ -26,7 +26,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/velero-io/velero/pkg/builder" ) const ( diff --git a/pkg/repository/maintenance/maintenance.go b/pkg/repository/maintenance/maintenance.go index 747d89f52..9a6b118db 100644 --- a/pkg/repository/maintenance/maintenance.go +++ b/pkg/repository/maintenance/maintenance.go @@ -37,14 +37,14 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/constant" - velerolabel "github.com/vmware-tanzu/velero/pkg/label" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/constant" + velerolabel "github.com/velero-io/velero/pkg/label" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ) const ( diff --git a/pkg/repository/maintenance/maintenance_test.go b/pkg/repository/maintenance/maintenance_test.go index 97eee1148..d501e241d 100644 --- a/pkg/repository/maintenance/maintenance_test.go +++ b/pkg/repository/maintenance/maintenance_test.go @@ -38,15 +38,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerolabel "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/repository/provider" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/logging" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerolabel "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/repository/provider" + velerotest "github.com/velero-io/velero/pkg/test" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/logging" ) func TestGenerateJobName(t *testing.T) { diff --git a/pkg/repository/manager/manager.go b/pkg/repository/manager/manager.go index 4d03931c0..d22288e85 100644 --- a/pkg/repository/manager/manager.go +++ b/pkg/repository/manager/manager.go @@ -25,11 +25,11 @@ import ( "github.com/sirupsen/logrus" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/repository/provider" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/repository/provider" + "github.com/velero-io/velero/pkg/util/filesystem" ) // Manager manages backup repositories. diff --git a/pkg/repository/manager/manager_test.go b/pkg/repository/manager/manager_test.go index 88d8db481..b3312a636 100644 --- a/pkg/repository/manager/manager_test.go +++ b/pkg/repository/manager/manager_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestGetRepositoryProvider(t *testing.T) { diff --git a/pkg/repository/mocks/Manager.go b/pkg/repository/mocks/Manager.go index 954967adc..9ef8ea889 100644 --- a/pkg/repository/mocks/Manager.go +++ b/pkg/repository/mocks/Manager.go @@ -9,7 +9,7 @@ import ( time "time" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) // Manager is an autogenerated mock type for the Manager type diff --git a/pkg/repository/provider/provider.go b/pkg/repository/provider/provider.go index 7681d830b..301c45834 100644 --- a/pkg/repository/provider/provider.go +++ b/pkg/repository/provider/provider.go @@ -20,7 +20,7 @@ import ( "context" "time" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // RepoParam includes the parameters to manipulate a backup repository diff --git a/pkg/repository/provider/unified_repo.go b/pkg/repository/provider/unified_repo.go index 2af59f190..27e20cae7 100644 --- a/pkg/repository/provider/unified_repo.go +++ b/pkg/repository/provider/unified_repo.go @@ -30,12 +30,12 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - repoconfig "github.com/vmware-tanzu/velero/pkg/repository/config" - repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - reposervice "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/service" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + repoconfig "github.com/velero-io/velero/pkg/repository/config" + repokey "github.com/velero-io/velero/pkg/repository/keys" + "github.com/velero-io/velero/pkg/repository/udmrepo" + reposervice "github.com/velero-io/velero/pkg/repository/udmrepo/service" ) type unifiedRepoProvider struct { diff --git a/pkg/repository/provider/unified_repo_test.go b/pkg/repository/provider/unified_repo_test.go index e0e0a8b8f..d8f5b1975 100644 --- a/pkg/repository/provider/unified_repo_test.go +++ b/pkg/repository/provider/unified_repo_test.go @@ -30,12 +30,12 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerocredentials "github.com/vmware-tanzu/velero/internal/credentials" - credmock "github.com/vmware-tanzu/velero/internal/credentials/mocks" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - reposervicenmocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerocredentials "github.com/velero-io/velero/internal/credentials" + credmock "github.com/velero-io/velero/internal/credentials/mocks" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository/udmrepo" + reposervicenmocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestGetStorageCredentials(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/azure.go b/pkg/repository/udmrepo/kopialib/backend/azure.go index 79bf1bbc2..55bb79e43 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure.go @@ -23,9 +23,9 @@ import ( "github.com/kopia/kopia/repo/blob" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/azure" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/azure" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type AzureBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go b/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go index 5e2443a42..541b7c82d 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go @@ -23,9 +23,9 @@ import ( "github.com/kopia/kopia/repo/blob/azure" "github.com/kopia/kopia/repo/blob/throttling" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" - azureutil "github.com/vmware-tanzu/velero/pkg/util/azure" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" + azureutil "github.com/velero-io/velero/pkg/util/azure" ) const ( diff --git a/pkg/repository/udmrepo/kopialib/backend/azure_test.go b/pkg/repository/udmrepo/kopialib/backend/azure_test.go index b4504986e..e10517997 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" "github.com/kopia/kopia/repo/blob/throttling" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) func TestAzureSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/common.go b/pkg/repository/udmrepo/kopialib/backend/common.go index 7af061204..900857946 100644 --- a/pkg/repository/udmrepo/kopialib/backend/common.go +++ b/pkg/repository/udmrepo/kopialib/backend/common.go @@ -29,7 +29,7 @@ import ( "github.com/kopia/kopia/repo/hashing" "github.com/kopia/kopia/repo/splitter" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) const ( diff --git a/pkg/repository/udmrepo/kopialib/backend/common_test.go b/pkg/repository/udmrepo/kopialib/backend/common_test.go index 1083bca9a..2f9773e73 100644 --- a/pkg/repository/udmrepo/kopialib/backend/common_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/common_test.go @@ -28,7 +28,7 @@ import ( "github.com/kopia/kopia/repo/splitter" "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) func TestSetupNewRepositoryOptions(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/file_system.go b/pkg/repository/udmrepo/kopialib/backend/file_system.go index f0999e832..9680fa8bd 100644 --- a/pkg/repository/udmrepo/kopialib/backend/file_system.go +++ b/pkg/repository/udmrepo/kopialib/backend/file_system.go @@ -27,8 +27,8 @@ import ( "github.com/kopia/kopia/repo/blob/filesystem" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type FsBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/file_system_test.go b/pkg/repository/udmrepo/kopialib/backend/file_system_test.go index 33e608efd..92fca43ae 100644 --- a/pkg/repository/udmrepo/kopialib/backend/file_system_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/file_system_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" "github.com/kopia/kopia/repo/blob/filesystem" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) func TestFSSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/gcs.go b/pkg/repository/udmrepo/kopialib/backend/gcs.go index 2c46609a4..6a10b6010 100644 --- a/pkg/repository/udmrepo/kopialib/backend/gcs.go +++ b/pkg/repository/udmrepo/kopialib/backend/gcs.go @@ -24,8 +24,8 @@ import ( "github.com/kopia/kopia/repo/blob" "github.com/kopia/kopia/repo/blob/gcs" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type GCSBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/gcs_test.go b/pkg/repository/udmrepo/kopialib/backend/gcs_test.go index 3398c35c2..a782e0375 100644 --- a/pkg/repository/udmrepo/kopialib/backend/gcs_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/gcs_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" "github.com/kopia/kopia/repo/blob/gcs" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) func TestGcsSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/s3.go b/pkg/repository/udmrepo/kopialib/backend/s3.go index 202c3c449..25e27dddc 100644 --- a/pkg/repository/udmrepo/kopialib/backend/s3.go +++ b/pkg/repository/udmrepo/kopialib/backend/s3.go @@ -24,8 +24,8 @@ import ( "github.com/kopia/kopia/repo/blob" "github.com/kopia/kopia/repo/blob/s3" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type S3Backend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/s3_test.go b/pkg/repository/udmrepo/kopialib/backend/s3_test.go index 3e1b045c4..58a2d4d6d 100644 --- a/pkg/repository/udmrepo/kopialib/backend/s3_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/s3_test.go @@ -19,12 +19,12 @@ package backend import ( "testing" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" "github.com/kopia/kopia/repo/blob/s3" "github.com/stretchr/testify/assert" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) func TestS3Setup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/utils_test.go b/pkg/repository/udmrepo/kopialib/backend/utils_test.go index 24923e447..4e57bafd0 100644 --- a/pkg/repository/udmrepo/kopialib/backend/utils_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/utils_test.go @@ -25,7 +25,7 @@ import ( "go.uber.org/zap" "go.uber.org/zap/zapcore" - storagemocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + storagemocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" ) func TestOptionalHaveBool(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/lib_repo.go b/pkg/repository/udmrepo/kopialib/lib_repo.go index 2131baa5c..fc1e50d63 100644 --- a/pkg/repository/udmrepo/kopialib/lib_repo.go +++ b/pkg/repository/udmrepo/kopialib/lib_repo.go @@ -38,9 +38,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/kopia" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" + "github.com/velero-io/velero/pkg/kopia" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" ) type kopiaRepoService struct { diff --git a/pkg/repository/udmrepo/kopialib/lib_repo_test.go b/pkg/repository/udmrepo/kopialib/lib_repo_test.go index 1776f9be0..c3c778f66 100644 --- a/pkg/repository/udmrepo/kopialib/lib_repo_test.go +++ b/pkg/repository/udmrepo/kopialib/lib_repo_test.go @@ -36,10 +36,10 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - repomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + "github.com/velero-io/velero/pkg/repository/udmrepo" + repomocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestOpen(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/repo_init.go b/pkg/repository/udmrepo/kopialib/repo_init.go index ade9039d7..da6fe022d 100644 --- a/pkg/repository/udmrepo/kopialib/repo_init.go +++ b/pkg/repository/udmrepo/kopialib/repo_init.go @@ -32,9 +32,9 @@ import ( "github.com/kopia/kopia/repo/maintenance" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/kopia" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" + "github.com/velero-io/velero/pkg/kopia" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" ) type kopiaBackendStore struct { diff --git a/pkg/repository/udmrepo/kopialib/repo_init_test.go b/pkg/repository/udmrepo/kopialib/repo_init_test.go index 3b8a52be2..a71089d75 100644 --- a/pkg/repository/udmrepo/kopialib/repo_init_test.go +++ b/pkg/repository/udmrepo/kopialib/repo_init_test.go @@ -27,16 +27,16 @@ import ( "github.com/kopia/kopia/repo/maintenance" "github.com/kopia/kopia/repo/manifest" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" - repomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" - storagemocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" + repomocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + storagemocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" "github.com/pkg/errors" ) diff --git a/pkg/repository/udmrepo/mocks/BackupRepo.go b/pkg/repository/udmrepo/mocks/BackupRepo.go index 623c4d70d..6ca2648bc 100644 --- a/pkg/repository/udmrepo/mocks/BackupRepo.go +++ b/pkg/repository/udmrepo/mocks/BackupRepo.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) // NewBackupRepo creates a new instance of BackupRepo. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/mocks/BackupRepoService.go b/pkg/repository/udmrepo/mocks/BackupRepoService.go index 34a24ef97..b5be1d866 100644 --- a/pkg/repository/udmrepo/mocks/BackupRepoService.go +++ b/pkg/repository/udmrepo/mocks/BackupRepoService.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) // NewBackupRepoService creates a new instance of BackupRepoService. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/mocks/ObjectWriter.go b/pkg/repository/udmrepo/mocks/ObjectWriter.go index d50a3ce76..26d38eba0 100644 --- a/pkg/repository/udmrepo/mocks/ObjectWriter.go +++ b/pkg/repository/udmrepo/mocks/ObjectWriter.go @@ -6,7 +6,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" ) // NewObjectWriter creates a new instance of ObjectWriter. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/service/service.go b/pkg/repository/udmrepo/service/service.go index 195b67b11..1f76c7c38 100644 --- a/pkg/repository/udmrepo/service/service.go +++ b/pkg/repository/udmrepo/service/service.go @@ -19,8 +19,8 @@ package service import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib" ) // Create creates an instance of BackupRepoService diff --git a/pkg/restic/common.go b/pkg/restic/common.go index a5bf05c44..572c0f7ad 100644 --- a/pkg/restic/common.go +++ b/pkg/restic/common.go @@ -26,10 +26,10 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - repoconfig "github.com/vmware-tanzu/velero/pkg/repository/config" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + repoconfig "github.com/velero-io/velero/pkg/repository/config" + "github.com/velero-io/velero/pkg/util/filesystem" ) const ( diff --git a/pkg/restic/common_test.go b/pkg/restic/common_test.go index 97363340c..590152fa9 100644 --- a/pkg/restic/common_test.go +++ b/pkg/restic/common_test.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestTempCACertFile(t *testing.T) { diff --git a/pkg/restic/exec_commands.go b/pkg/restic/exec_commands.go index 94c17c04a..ed5e2274d 100644 --- a/pkg/restic/exec_commands.go +++ b/pkg/restic/exec_commands.go @@ -26,9 +26,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/exec" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/util/filesystem" ) const restoreProgressCheckInterval = 10 * time.Second diff --git a/pkg/restic/exec_commands_test.go b/pkg/restic/exec_commands_test.go index 370f6653c..5994c948c 100644 --- a/pkg/restic/exec_commands_test.go +++ b/pkg/restic/exec_commands_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/filesystem" ) func Test_getSummaryLine(t *testing.T) { diff --git a/pkg/restore/actions/add_pvc_from_pod_action.go b/pkg/restore/actions/add_pvc_from_pod_action.go index 3e88f796a..3ae6ee804 100644 --- a/pkg/restore/actions/add_pvc_from_pod_action.go +++ b/pkg/restore/actions/add_pvc_from_pod_action.go @@ -22,8 +22,8 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) type AddPVCFromPodAction struct { diff --git a/pkg/restore/actions/add_pvc_from_pod_action_test.go b/pkg/restore/actions/add_pvc_from_pod_action_test.go index 5d27e1582..b94c82e70 100644 --- a/pkg/restore/actions/add_pvc_from_pod_action_test.go +++ b/pkg/restore/actions/add_pvc_from_pod_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestAddPVCFromPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/admissionwebhook_config_action.go b/pkg/restore/actions/admissionwebhook_config_action.go index 82599dc62..e2bd07257 100644 --- a/pkg/restore/actions/admissionwebhook_config_action.go +++ b/pkg/restore/actions/admissionwebhook_config_action.go @@ -22,12 +22,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // AdmissionWebhookConfigurationAction is a RestoreItemAction plugin applicable to mutatingwebhookconfiguration and // validatingwebhookconfiguration to reset the invalid value for "sideEffects" of the webhooks. -// More background please refer to https://github.com/vmware-tanzu/velero/issues/3516 +// More background please refer to https://github.com/velero-io/velero/issues/3516 type AdmissionWebhookConfigurationAction struct { logger logrus.FieldLogger } diff --git a/pkg/restore/actions/admissionwebhook_config_action_test.go b/pkg/restore/actions/admissionwebhook_config_action_test.go index f1257cb9f..f83e9b8b6 100644 --- a/pkg/restore/actions/admissionwebhook_config_action_test.go +++ b/pkg/restore/actions/admissionwebhook_config_action_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestNewAdmissionWebhookConfigurationActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/apiservice_action.go b/pkg/restore/actions/apiservice_action.go index f2433352b..69b94e8e1 100644 --- a/pkg/restore/actions/apiservice_action.go +++ b/pkg/restore/actions/apiservice_action.go @@ -20,7 +20,7 @@ import ( "github.com/sirupsen/logrus" "k8s.io/kube-aggregator/pkg/controllers/autoregister" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) type APIServiceAction struct { diff --git a/pkg/restore/actions/apiservice_action_test.go b/pkg/restore/actions/apiservice_action_test.go index 9058259c1..ef52733b0 100644 --- a/pkg/restore/actions/apiservice_action_test.go +++ b/pkg/restore/actions/apiservice_action_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" apiregistrationv1 "k8s.io/kube-aggregator/pkg/apis/apiregistration/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestAPIServiceActionExecuteSkipsRestore(t *testing.T) { diff --git a/pkg/restore/actions/change_image_name_action.go b/pkg/restore/actions/change_image_name_action.go index 828da40d6..356675c04 100644 --- a/pkg/restore/actions/change_image_name_action.go +++ b/pkg/restore/actions/change_image_name_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" ) const ( diff --git a/pkg/restore/actions/change_image_name_action_test.go b/pkg/restore/actions/change_image_name_action_test.go index 530c8453d..d29c1d9c9 100644 --- a/pkg/restore/actions/change_image_name_action_test.go +++ b/pkg/restore/actions/change_image_name_action_test.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/plugin/velero" ) // TestChangeImageRepositoryActionExecute runs the ChangeImageNameAction's Execute diff --git a/pkg/restore/actions/change_storageclass_action.go b/pkg/restore/actions/change_storageclass_action.go index f9f031fe3..bebb236b9 100644 --- a/pkg/restore/actions/change_storageclass_action.go +++ b/pkg/restore/actions/change_storageclass_action.go @@ -29,8 +29,8 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" storagev1client "k8s.io/client-go/kubernetes/typed/storage/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" ) // ChangeStorageClassAction updates a PV or PVC's storage class name diff --git a/pkg/restore/actions/change_storageclass_action_test.go b/pkg/restore/actions/change_storageclass_action_test.go index 13bbcdcc4..6e89f8baf 100644 --- a/pkg/restore/actions/change_storageclass_action_test.go +++ b/pkg/restore/actions/change_storageclass_action_test.go @@ -30,8 +30,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/plugin/velero" ) // TestChangeStorageClassActionExecute runs the ChangeStorageClassAction's Execute diff --git a/pkg/restore/actions/clusterrolebinding_action.go b/pkg/restore/actions/clusterrolebinding_action.go index a11665c1a..28534ed6f 100644 --- a/pkg/restore/actions/clusterrolebinding_action.go +++ b/pkg/restore/actions/clusterrolebinding_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // ClusterRoleBindingAction handle namespace remappings for role bindings diff --git a/pkg/restore/actions/clusterrolebinding_action_test.go b/pkg/restore/actions/clusterrolebinding_action_test.go index 0829221db..8ada6dc93 100644 --- a/pkg/restore/actions/clusterrolebinding_action_test.go +++ b/pkg/restore/actions/clusterrolebinding_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" ) func TestClusterRoleBindingActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go index 9e4cf7e2f..8a77af5c5 100644 --- a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go +++ b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // CRDV1PreserveUnknownFieldsAction will take a CRD and inspect it for the API version and the PreserveUnknownFields value. diff --git a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go index 329cfb433..2c136059d 100644 --- a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go +++ b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go @@ -23,13 +23,13 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" ) func TestExecuteForACRDWithAnIntOnAFloat64FieldShouldWork(t *testing.T) { - // ref. reopen of https://github.com/vmware-tanzu/velero/issues/2319 + // ref. reopen of https://github.com/velero-io/velero/issues/2319 b := builder.ForV1CustomResourceDefinition("test.velero.io") // 5 here is just an int value, it could be any other whole number. diff --git a/pkg/restore/actions/csi/pvc_action.go b/pkg/restore/actions/csi/pvc_action.go index dee23cf70..e89a2b0c3 100644 --- a/pkg/restore/actions/csi/pvc_action.go +++ b/pkg/restore/actions/csi/pvc_action.go @@ -33,17 +33,17 @@ import ( utilrand "k8s.io/apimachinery/pkg/util/rand" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/client" - kuberesource "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/label" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - uploaderUtil "github.com/vmware-tanzu/velero/pkg/uploader/util" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/client" + kuberesource "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/label" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + uploaderUtil "github.com/velero-io/velero/pkg/uploader/util" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" ) const ( diff --git a/pkg/restore/actions/csi/pvc_action_test.go b/pkg/restore/actions/csi/pvc_action_test.go index 4da3bec50..ae858b6ff 100644 --- a/pkg/restore/actions/csi/pvc_action_test.go +++ b/pkg/restore/actions/csi/pvc_action_test.go @@ -36,16 +36,16 @@ import ( "k8s.io/apimachinery/pkg/util/validation" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/apis/velero/shared" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" ) func TestResetPVCSpec(t *testing.T) { diff --git a/pkg/restore/actions/csi/volumesnapshot_action.go b/pkg/restore/actions/csi/volumesnapshot_action.go index dec33d4ef..38bed87a2 100644 --- a/pkg/restore/actions/csi/volumesnapshot_action.go +++ b/pkg/restore/actions/csi/volumesnapshot_action.go @@ -31,13 +31,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/kuberesource" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" ) // volumeSnapshotRestoreItemAction is a Velero restore item diff --git a/pkg/restore/actions/csi/volumesnapshot_action_test.go b/pkg/restore/actions/csi/volumesnapshot_action_test.go index de3e592c0..b7f128255 100644 --- a/pkg/restore/actions/csi/volumesnapshot_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshot_action_test.go @@ -31,12 +31,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util" ) var ( diff --git a/pkg/restore/actions/csi/volumesnapshotclass_action.go b/pkg/restore/actions/csi/volumesnapshotclass_action.go index c906a04b2..911e97430 100644 --- a/pkg/restore/actions/csi/volumesnapshotclass_action.go +++ b/pkg/restore/actions/csi/volumesnapshotclass_action.go @@ -23,10 +23,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" ) // volumeSnapshotClassRestoreItemAction is a Velero restore diff --git a/pkg/restore/actions/csi/volumesnapshotclass_action_test.go b/pkg/restore/actions/csi/volumesnapshotclass_action_test.go index 73d86a109..5ad757452 100644 --- a/pkg/restore/actions/csi/volumesnapshotclass_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshotclass_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" - //"github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + //"github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) func TestVSClassExecute(t *testing.T) { diff --git a/pkg/restore/actions/csi/volumesnapshotcontent_action.go b/pkg/restore/actions/csi/volumesnapshotcontent_action.go index 00a25c86f..d13adc994 100644 --- a/pkg/restore/actions/csi/volumesnapshotcontent_action.go +++ b/pkg/restore/actions/csi/volumesnapshotcontent_action.go @@ -27,13 +27,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/client" - plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/csi" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/client" + plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/csi" ) // volumeSnapshotContentRestoreItemAction is a restore item action diff --git a/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go b/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go index 83b79bd5b..5b9b75b57 100644 --- a/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go @@ -26,13 +26,13 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + factorymocks "github.com/velero-io/velero/pkg/client/mocks" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util" ) func TestVSCExecute(t *testing.T) { diff --git a/pkg/restore/actions/dataupload_retrieve_action.go b/pkg/restore/actions/dataupload_retrieve_action.go index a7efdc5f7..e72fda8ba 100644 --- a/pkg/restore/actions/dataupload_retrieve_action.go +++ b/pkg/restore/actions/dataupload_retrieve_action.go @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/types" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - veleroclient "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + veleroclient "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/velero" ) type DataUploadRetrieveAction struct { diff --git a/pkg/restore/actions/dataupload_retrieve_action_test.go b/pkg/restore/actions/dataupload_retrieve_action_test.go index 64be241bf..572d3ff1c 100644 --- a/pkg/restore/actions/dataupload_retrieve_action_test.go +++ b/pkg/restore/actions/dataupload_retrieve_action_test.go @@ -27,12 +27,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestDataUploadRetrieveActionExectue(t *testing.T) { diff --git a/pkg/restore/actions/init_restorehook_pod_action.go b/pkg/restore/actions/init_restorehook_pod_action.go index 7614ef085..c147860ee 100644 --- a/pkg/restore/actions/init_restorehook_pod_action.go +++ b/pkg/restore/actions/init_restorehook_pod_action.go @@ -21,9 +21,9 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) // InitRestoreHookPodAction is a RestoreItemAction plugin applicable to pods that runs diff --git a/pkg/restore/actions/init_restorehook_pod_action_test.go b/pkg/restore/actions/init_restorehook_pod_action_test.go index 52da2011b..66d307d3c 100644 --- a/pkg/restore/actions/init_restorehook_pod_action_test.go +++ b/pkg/restore/actions/init_restorehook_pod_action_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestInitContainerRestoreHookPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/job_action.go b/pkg/restore/actions/job_action.go index 1eabc208c..d0a8cdde9 100644 --- a/pkg/restore/actions/job_action.go +++ b/pkg/restore/actions/job_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) const ( diff --git a/pkg/restore/actions/job_action_test.go b/pkg/restore/actions/job_action_test.go index e3578bb60..a78ecd8a6 100644 --- a/pkg/restore/actions/job_action_test.go +++ b/pkg/restore/actions/job_action_test.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestJobActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/pod_action.go b/pkg/restore/actions/pod_action.go index a9db3ed7e..3dfa33857 100644 --- a/pkg/restore/actions/pod_action.go +++ b/pkg/restore/actions/pod_action.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) type PodAction struct { diff --git a/pkg/restore/actions/pod_action_test.go b/pkg/restore/actions/pod_action_test.go index dae455a5b..418346ff7 100644 --- a/pkg/restore/actions/pod_action_test.go +++ b/pkg/restore/actions/pod_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/pod_volume_restore_action.go b/pkg/restore/actions/pod_volume_restore_action.go index e26a53034..831ca390a 100644 --- a/pkg/restore/actions/pod_volume_restore_action.go +++ b/pkg/restore/actions/pod_volume_restore_action.go @@ -21,7 +21,7 @@ import ( "fmt" "strings" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/boolptr" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -33,16 +33,16 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroimage "github.com/vmware-tanzu/velero/internal/velero" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/restorehelper" - "github.com/vmware-tanzu/velero/pkg/util/kube" - veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + veleroimage "github.com/velero-io/velero/internal/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/restorehelper" + "github.com/velero-io/velero/pkg/util/kube" + veleroutil "github.com/velero-io/velero/pkg/util/velero" ) const ( diff --git a/pkg/restore/actions/pod_volume_restore_action_test.go b/pkg/restore/actions/pod_volume_restore_action_test.go index bc9662ab7..8faa80f43 100644 --- a/pkg/restore/actions/pod_volume_restore_action_test.go +++ b/pkg/restore/actions/pod_volume_restore_action_test.go @@ -20,7 +20,7 @@ import ( "sort" "testing" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/boolptr" "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" @@ -33,16 +33,16 @@ import ( "k8s.io/client-go/kubernetes/fake" crfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/buildinfo" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/kube" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/kube" "k8s.io/client-go/kubernetes/scheme" - "github.com/vmware-tanzu/velero/pkg/restorehelper" + "github.com/velero-io/velero/pkg/restorehelper" ) func TestGetImage(t *testing.T) { diff --git a/pkg/restore/actions/pvc_action.go b/pkg/restore/actions/pvc_action.go index a4a63374d..4ecfa9ead 100644 --- a/pkg/restore/actions/pvc_action.go +++ b/pkg/restore/actions/pvc_action.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util" ) const ( diff --git a/pkg/restore/actions/pvc_action_test.go b/pkg/restore/actions/pvc_action_test.go index aa2ddeeef..d143342c3 100644 --- a/pkg/restore/actions/pvc_action_test.go +++ b/pkg/restore/actions/pvc_action_test.go @@ -28,10 +28,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) // TestPVCActionExecute runs the PVCAction's Execute diff --git a/pkg/restore/actions/rolebinding_action.go b/pkg/restore/actions/rolebinding_action.go index 05e463587..92f712a48 100644 --- a/pkg/restore/actions/rolebinding_action.go +++ b/pkg/restore/actions/rolebinding_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/plugin/velero" ) // RoleBindingAction handle namespace remappings for role bindings diff --git a/pkg/restore/actions/rolebinding_action_test.go b/pkg/restore/actions/rolebinding_action_test.go index f2867e8a5..bf29cf0cd 100644 --- a/pkg/restore/actions/rolebinding_action_test.go +++ b/pkg/restore/actions/rolebinding_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" ) func TestRoleBindingActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/secret_action.go b/pkg/restore/actions/secret_action.go index 2ec9fb4ff..e339018a9 100644 --- a/pkg/restore/actions/secret_action.go +++ b/pkg/restore/actions/secret_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/kube" ) // SecretAction is a restore item action for secrets diff --git a/pkg/restore/actions/secret_action_test.go b/pkg/restore/actions/secret_action_test.go index 575b7634e..92c4349a2 100644 --- a/pkg/restore/actions/secret_action_test.go +++ b/pkg/restore/actions/secret_action_test.go @@ -28,8 +28,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" ) func TestSecretActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/service_account_action.go b/pkg/restore/actions/service_account_action.go index 429c21949..52e3c3095 100644 --- a/pkg/restore/actions/service_account_action.go +++ b/pkg/restore/actions/service_account_action.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/kube" ) type ServiceAccountAction struct { diff --git a/pkg/restore/actions/service_account_action_test.go b/pkg/restore/actions/service_account_action_test.go index 6a2f74ead..a6cc389f7 100644 --- a/pkg/restore/actions/service_account_action_test.go +++ b/pkg/restore/actions/service_account_action_test.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/test" ) func TestServiceAccountActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/service_action.go b/pkg/restore/actions/service_action.go index 47147a31f..9db2ae600 100644 --- a/pkg/restore/actions/service_action.go +++ b/pkg/restore/actions/service_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/util/sets" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/util/boolptr" ) const annotationLastAppliedConfig = "kubectl.kubernetes.io/last-applied-configuration" diff --git a/pkg/restore/actions/service_action_test.go b/pkg/restore/actions/service_action_test.go index f9a01d5d4..a94675c3b 100644 --- a/pkg/restore/actions/service_action_test.go +++ b/pkg/restore/actions/service_action_test.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/plugin/velero" + velerotest "github.com/velero-io/velero/pkg/test" ) func svcJSON(ports ...corev1api.ServicePort) string { diff --git a/pkg/restore/merge_service_account_test.go b/pkg/restore/merge_service_account_test.go index 4322ae003..13e77bddd 100644 --- a/pkg/restore/merge_service_account_test.go +++ b/pkg/restore/merge_service_account_test.go @@ -25,7 +25,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) var mergedServiceAccountsBenchmarkResult *unstructured.Unstructured diff --git a/pkg/restore/prioritize_group_version.go b/pkg/restore/prioritize_group_version.go index 5d7ab15d5..cd52d1cfc 100644 --- a/pkg/restore/prioritize_group_version.go +++ b/pkg/restore/prioritize_group_version.go @@ -27,9 +27,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/version" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" - "github.com/vmware-tanzu/velero/pkg/client" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" + "github.com/velero-io/velero/pkg/client" ) // ChosenGroupVersion is the API Group version that was selected to restore diff --git a/pkg/restore/prioritize_group_version_test.go b/pkg/restore/prioritize_group_version_test.go index e87fb13ba..fa6300162 100644 --- a/pkg/restore/prioritize_group_version_test.go +++ b/pkg/restore/prioritize_group_version_test.go @@ -23,8 +23,8 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/test" ) func TestK8sPrioritySort(t *testing.T) { diff --git a/pkg/restore/pv_restorer.go b/pkg/restore/pv_restorer.go index 53fbd0126..6f4a7bcb7 100644 --- a/pkg/restore/pv_restorer.go +++ b/pkg/restore/pv_restorer.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/types" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/volume" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/volume" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/boolptr" ) type PVRestorer interface { diff --git a/pkg/restore/pv_restorer_test.go b/pkg/restore/pv_restorer_test.go index 09c6dd0ad..b7a956fbb 100644 --- a/pkg/restore/pv_restorer_test.go +++ b/pkg/restore/pv_restorer_test.go @@ -27,12 +27,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/vmware-tanzu/velero/internal/volume" - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/internal/volume" + api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func defaultBackup() *builder.BackupBuilder { diff --git a/pkg/restore/request.go b/pkg/restore/request.go index 239d65df9..e451f61c0 100644 --- a/pkg/restore/request.go +++ b/pkg/restore/request.go @@ -25,11 +25,11 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/internal/resourcemodifiers" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/internal/resourcemodifiers" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/util/kube" ) const ( diff --git a/pkg/restore/restore.go b/pkg/restore/restore.go index 5287eec21..378633f20 100644 --- a/pkg/restore/restore.go +++ b/pkg/restore/restore.go @@ -52,33 +52,33 @@ import ( "k8s.io/client-go/util/retry" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/hook" - "github.com/vmware-tanzu/velero/internal/resourcemodifiers" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/plugin/framework" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podexec" - "github.com/vmware-tanzu/velero/pkg/podvolume" - "github.com/vmware-tanzu/velero/pkg/podvolume/configs" - "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" - csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/pkg/util/results" - "github.com/vmware-tanzu/velero/pkg/util/wildcard" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/hook" + "github.com/velero-io/velero/internal/resourcemodifiers" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podexec" + "github.com/velero-io/velero/pkg/podvolume" + "github.com/velero-io/velero/pkg/podvolume/configs" + "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" + csiutil "github.com/velero-io/velero/pkg/util/csi" + "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/results" + "github.com/velero-io/velero/pkg/util/wildcard" ) const ObjectStatusRestoreAnnotationKey = "velero.io/restore-status" @@ -1789,7 +1789,7 @@ func isAlreadyExistsError(ctx *restoreContext, obj *unstructured.Unstructured, e // 1. For NodePort service, the service has nodePort preservation while the same nodePort service already exists. - Get invalid value error // 2. For LoadBalancer service, the "healthCheckNodePort" already exists. - Get internal error // If this is the case, the function returns true to avoid reporting error. - // Refer to https://github.com/vmware-tanzu/velero/issues/2308 for more details + // Refer to https://github.com/velero-io/velero/issues/2308 for more details if obj.GetKind() != "Service" { return false, nil } diff --git a/pkg/restore/restore_test.go b/pkg/restore/restore_test.go index 95b283cbe..9efd2eef1 100644 --- a/pkg/restore/restore_test.go +++ b/pkg/restore/restore_test.go @@ -25,8 +25,8 @@ import ( "testing" "time" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/collections" snapshotv1api "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumesnapshot/v1" "github.com/pkg/errors" @@ -45,25 +45,25 @@ import ( "k8s.io/client-go/dynamic" kubetesting "k8s.io/client-go/testing" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/client" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/features" - "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" - riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/vmware-tanzu/velero/pkg/podvolume" - uploadermocks "github.com/vmware-tanzu/velero/pkg/podvolume/mocks" - "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/kube" - kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - . "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/client" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/features" + "github.com/velero-io/velero/pkg/itemoperation" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" + riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/velero-io/velero/pkg/podvolume" + uploadermocks "github.com/velero-io/velero/pkg/podvolume/mocks" + "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/kube" + kubeutil "github.com/velero-io/velero/pkg/util/kube" + . "github.com/velero-io/velero/pkg/util/results" ) func TestRestorePVWithVolumeInfo(t *testing.T) { diff --git a/pkg/restore/restore_wildcard_test.go b/pkg/restore/restore_wildcard_test.go index c38ad7dd9..257eec785 100644 --- a/pkg/restore/restore_wildcard_test.go +++ b/pkg/restore/restore_wildcard_test.go @@ -23,8 +23,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/archive" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/archive" ) func TestExpandNamespaceWildcards(t *testing.T) { diff --git a/pkg/test/fake_controller_runtime_client.go b/pkg/test/fake_controller_runtime_client.go index 90ee95d11..383c7d0b8 100644 --- a/pkg/test/fake_controller_runtime_client.go +++ b/pkg/test/fake_controller_runtime_client.go @@ -31,8 +31,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" k8sfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) func NewFakeControllerRuntimeClientBuilder(t *testing.T) *k8sfake.ClientBuilder { diff --git a/pkg/test/fake_dynamic.go b/pkg/test/fake_dynamic.go index 996e8cfd1..ee5021801 100644 --- a/pkg/test/fake_dynamic.go +++ b/pkg/test/fake_dynamic.go @@ -24,7 +24,7 @@ import ( "k8s.io/apimachinery/pkg/watch" "k8s.io/client-go/dynamic/dynamicinformer" - "github.com/vmware-tanzu/velero/pkg/client" + "github.com/velero-io/velero/pkg/client" ) type FakeDynamicFactory struct { diff --git a/pkg/test/fake_file_system.go b/pkg/test/fake_file_system.go index 7a744647b..2beae0644 100644 --- a/pkg/test/fake_file_system.go +++ b/pkg/test/fake_file_system.go @@ -23,7 +23,7 @@ import ( "github.com/spf13/afero" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/velero-io/velero/pkg/util/filesystem" ) type FakeFileSystem struct { diff --git a/pkg/test/mock_pod_command_executor.go b/pkg/test/mock_pod_command_executor.go index b8ace0c6e..ff4019a77 100644 --- a/pkg/test/mock_pod_command_executor.go +++ b/pkg/test/mock_pod_command_executor.go @@ -22,7 +22,7 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/mock" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) type MockPodCommandExecutor struct { diff --git a/pkg/test/tar_writer.go b/pkg/test/tar_writer.go index 20706766c..a51079655 100644 --- a/pkg/test/tar_writer.go +++ b/pkg/test/tar_writer.go @@ -29,7 +29,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/util/encode" + "github.com/velero-io/velero/pkg/util/encode" ) type TarWriter struct { diff --git a/pkg/types/node_agent.go b/pkg/types/node_agent.go index f456bbf55..b7743bac2 100644 --- a/pkg/types/node_agent.go +++ b/pkg/types/node_agent.go @@ -19,7 +19,7 @@ package types import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/velero-io/velero/pkg/util/kube" ) type LoadConcurrency struct { diff --git a/pkg/types/repo_maintenance.go b/pkg/types/repo_maintenance.go index a5115ff92..ae3b1d484 100644 --- a/pkg/types/repo_maintenance.go +++ b/pkg/types/repo_maintenance.go @@ -16,7 +16,7 @@ limitations under the License. package types -import "github.com/vmware-tanzu/velero/pkg/util/kube" +import "github.com/velero-io/velero/pkg/util/kube" type JobConfigs struct { // LoadAffinities is the config for repository maintenance job load affinity. diff --git a/pkg/uploader/cbt/bitmap.go b/pkg/uploader/cbt/bitmap.go index f26cb22b7..731096cfd 100644 --- a/pkg/uploader/cbt/bitmap.go +++ b/pkg/uploader/cbt/bitmap.go @@ -21,7 +21,7 @@ import ( "github.com/RoaringBitmap/roaring" - "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" + "github.com/velero-io/velero/pkg/uploader/cbt/types" ) const ( diff --git a/pkg/uploader/cbt/set.go b/pkg/uploader/cbt/set.go index 5919419e6..3c82eff74 100644 --- a/pkg/uploader/cbt/set.go +++ b/pkg/uploader/cbt/set.go @@ -21,8 +21,8 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/cbtservice" - "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" + "github.com/velero-io/velero/pkg/cbtservice" + "github.com/velero-io/velero/pkg/uploader/cbt/types" ) // SetBitmapOrFull translates the allocated/changed blocks from CBT service to the given bitmap or set the bitmap to full when error happens diff --git a/pkg/uploader/cbt/set_test.go b/pkg/uploader/cbt/set_test.go index 55701dedd..93bd93171 100644 --- a/pkg/uploader/cbt/set_test.go +++ b/pkg/uploader/cbt/set_test.go @@ -24,9 +24,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/cbtservice" - cbtservicemocks "github.com/vmware-tanzu/velero/pkg/cbtservice/mocks" - cbtmocks "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types/mocks" + "github.com/velero-io/velero/pkg/cbtservice" + cbtservicemocks "github.com/velero-io/velero/pkg/cbtservice/mocks" + cbtmocks "github.com/velero-io/velero/pkg/uploader/cbt/types/mocks" ) func TestSetBitmapOrFull(t *testing.T) { diff --git a/pkg/uploader/cbt/types/mocks/Bitmap.go b/pkg/uploader/cbt/types/mocks/Bitmap.go index faa4ee242..b382e995e 100644 --- a/pkg/uploader/cbt/types/mocks/Bitmap.go +++ b/pkg/uploader/cbt/types/mocks/Bitmap.go @@ -6,7 +6,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" + "github.com/velero-io/velero/pkg/uploader/cbt/types" ) // NewBitmap creates a new instance of Bitmap. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/uploader/kopia/progress.go b/pkg/uploader/kopia/progress.go index 5071398d0..62a98efce 100644 --- a/pkg/uploader/kopia/progress.go +++ b/pkg/uploader/kopia/progress.go @@ -22,7 +22,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader" "github.com/kopia/kopia/snapshot/upload" ) diff --git a/pkg/uploader/kopia/progress_test.go b/pkg/uploader/kopia/progress_test.go index 8c18bb85b..8b811f854 100644 --- a/pkg/uploader/kopia/progress_test.go +++ b/pkg/uploader/kopia/progress_test.go @@ -23,7 +23,7 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader" ) type fakeProgressUpdater struct{} diff --git a/pkg/uploader/kopia/shim.go b/pkg/uploader/kopia/shim.go index f146348fa..d6c888e11 100644 --- a/pkg/uploader/kopia/shim.go +++ b/pkg/uploader/kopia/shim.go @@ -23,7 +23,7 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo" "github.com/kopia/kopia/repo" "github.com/kopia/kopia/repo/content" diff --git a/pkg/uploader/kopia/shim_test.go b/pkg/uploader/kopia/shim_test.go index 7933ec6b8..cbeada746 100644 --- a/pkg/uploader/kopia/shim_test.go +++ b/pkg/uploader/kopia/shim_test.go @@ -30,8 +30,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" ) func TestShimRepo(t *testing.T) { diff --git a/pkg/uploader/kopia/snapshot.go b/pkg/uploader/kopia/snapshot.go index 1924ed35b..3549fe45d 100644 --- a/pkg/uploader/kopia/snapshot.go +++ b/pkg/uploader/kopia/snapshot.go @@ -38,10 +38,10 @@ import ( "github.com/kopia/kopia/snapshot/snapshotfs" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/kopia" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/uploader" - uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" + "github.com/velero-io/velero/pkg/kopia" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/uploader" + uploaderutil "github.com/velero-io/velero/pkg/uploader/util" ) // All function mainly used to make testing more convenient diff --git a/pkg/uploader/kopia/snapshot_test.go b/pkg/uploader/kopia/snapshot_test.go index 984b92af5..9944ec06c 100644 --- a/pkg/uploader/kopia/snapshot_test.go +++ b/pkg/uploader/kopia/snapshot_test.go @@ -36,9 +36,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - repomocks "github.com/vmware-tanzu/velero/pkg/repository/mocks" - "github.com/vmware-tanzu/velero/pkg/uploader" - uploadermocks "github.com/vmware-tanzu/velero/pkg/uploader/mocks" + repomocks "github.com/velero-io/velero/pkg/repository/mocks" + "github.com/velero-io/velero/pkg/uploader" + uploadermocks "github.com/velero-io/velero/pkg/uploader/mocks" ) type snapshotMockes struct { diff --git a/pkg/uploader/provider/block.go b/pkg/uploader/provider/block.go index b1eed428a..1b42e5391 100644 --- a/pkg/uploader/provider/block.go +++ b/pkg/uploader/provider/block.go @@ -23,11 +23,11 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - repokeys "github.com/vmware-tanzu/velero/pkg/repository/keys" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + repokeys "github.com/velero-io/velero/pkg/repository/keys" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/uploader" ) type blockProvider struct { diff --git a/pkg/uploader/provider/block_test.go b/pkg/uploader/provider/block_test.go index a48b0a862..f6834c82c 100644 --- a/pkg/uploader/provider/block_test.go +++ b/pkg/uploader/provider/block_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/credentials/mocks" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - udmrepomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/credentials/mocks" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" + "github.com/velero-io/velero/pkg/repository/udmrepo" + udmrepomocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" ) func TestNewBlockUploaderProvider(t *testing.T) { diff --git a/pkg/uploader/provider/kopia.go b/pkg/uploader/provider/kopia.go index 51615fd2a..a806fe1d7 100644 --- a/pkg/uploader/provider/kopia.go +++ b/pkg/uploader/provider/kopia.go @@ -26,14 +26,14 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/uploader/kopia" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader/kopia" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - repokeys "github.com/vmware-tanzu/velero/pkg/repository/keys" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/service" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + repokeys "github.com/velero-io/velero/pkg/repository/keys" + "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/velero-io/velero/pkg/repository/udmrepo/service" ) // BackupFunc mainly used to make testing more convenient diff --git a/pkg/uploader/provider/kopia_test.go b/pkg/uploader/provider/kopia_test.go index 183a65d26..fbe5ea307 100644 --- a/pkg/uploader/provider/kopia_test.go +++ b/pkg/uploader/provider/kopia_test.go @@ -33,15 +33,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/credentials/mocks" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/repository" - udmrepo "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" - udmrepomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/uploader/kopia" - "github.com/vmware-tanzu/velero/pkg/util" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/credentials/mocks" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/repository" + udmrepo "github.com/velero-io/velero/pkg/repository/udmrepo" + udmrepomocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader/kopia" + "github.com/velero-io/velero/pkg/util" ) type FakeBackupProgressUpdater struct { diff --git a/pkg/uploader/provider/mocks/Provider.go b/pkg/uploader/provider/mocks/Provider.go index 71e60b84e..d84850129 100644 --- a/pkg/uploader/provider/mocks/Provider.go +++ b/pkg/uploader/provider/mocks/Provider.go @@ -8,8 +8,8 @@ import ( "context" mock "github.com/stretchr/testify/mock" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/uploader/provider" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/uploader/provider" ) // NewProvider creates a new instance of Provider. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/uploader/provider/provider.go b/pkg/uploader/provider/provider.go index 0c1caaffe..146f89e91 100644 --- a/pkg/uploader/provider/provider.go +++ b/pkg/uploader/provider/provider.go @@ -27,10 +27,10 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/credentials" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cbtservice" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/internal/credentials" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cbtservice" + "github.com/velero-io/velero/pkg/uploader" ) const restoreProgressCheckInterval = 10 * time.Second diff --git a/pkg/uploader/provider/provider_test.go b/pkg/uploader/provider/provider_test.go index 8f447725b..91a35c274 100644 --- a/pkg/uploader/provider/provider_test.go +++ b/pkg/uploader/provider/provider_test.go @@ -25,10 +25,10 @@ import ( corev1api "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/vmware-tanzu/velero/internal/credentials" - "github.com/vmware-tanzu/velero/internal/credentials/mocks" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util" + "github.com/velero-io/velero/internal/credentials" + "github.com/velero-io/velero/internal/credentials/mocks" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util" ) type NewUploaderProviderTestCase struct { diff --git a/pkg/uploader/util/uploader_config.go b/pkg/uploader/util/uploader_config.go index 5584ffbce..51499129e 100644 --- a/pkg/uploader/util/uploader_config.go +++ b/pkg/uploader/util/uploader_config.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) const ( diff --git a/pkg/uploader/util/uploader_config_test.go b/pkg/uploader/util/uploader_config_test.go index 593bce4f0..f03538116 100644 --- a/pkg/uploader/util/uploader_config_test.go +++ b/pkg/uploader/util/uploader_config_test.go @@ -22,7 +22,7 @@ import ( "github.com/pkg/errors" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestStoreBackupConfig(t *testing.T) { diff --git a/pkg/util/actionhelpers/pod_helper.go b/pkg/util/actionhelpers/pod_helper.go index 72c42936c..6d9514bdc 100644 --- a/pkg/util/actionhelpers/pod_helper.go +++ b/pkg/util/actionhelpers/pod_helper.go @@ -20,8 +20,8 @@ import ( "github.com/sirupsen/logrus" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) func RelatedItemsForPod(pod *corev1api.Pod, log logrus.FieldLogger) []velero.ResourceIdentifier { diff --git a/pkg/util/actionhelpers/pvc_helper.go b/pkg/util/actionhelpers/pvc_helper.go index f6a72eeaa..e496d5a1e 100644 --- a/pkg/util/actionhelpers/pvc_helper.go +++ b/pkg/util/actionhelpers/pvc_helper.go @@ -20,8 +20,8 @@ import ( "github.com/sirupsen/logrus" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) func RelatedItemsForPVC(pvc *corev1api.PersistentVolumeClaim, log logrus.FieldLogger) []velero.ResourceIdentifier { diff --git a/pkg/util/actionhelpers/service_account_helper.go b/pkg/util/actionhelpers/service_account_helper.go index 0474e1a9b..7f529f121 100644 --- a/pkg/util/actionhelpers/service_account_helper.go +++ b/pkg/util/actionhelpers/service_account_helper.go @@ -22,9 +22,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/util/sets" - velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerodiscovery "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/plugin/velero" ) func ClusterRoleBindingsForAction(clusterRoleBindingListers map[string]ClusterRoleBindingLister, discoveryHelper velerodiscovery.Helper) ([]ClusterRoleBinding, error) { diff --git a/pkg/util/azure/storage.go b/pkg/util/azure/storage.go index 49943a3f9..c5ba18c3a 100644 --- a/pkg/util/azure/storage.go +++ b/pkg/util/azure/storage.go @@ -33,7 +33,7 @@ import ( const ( // the keys of Azure BSL config: - // https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md + // https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md BSLConfigResourceGroup = "resourceGroup" BSLConfigStorageAccount = "storageAccount" BSLConfigStorageAccountAccessKeyName = "storageAccountKeyEnvVar" @@ -162,7 +162,7 @@ func GetStorageAccountCredentials(bslCfg map[string]string, creds map[string]str // getStorageAccountURI returns the storage account URI by the following order: // 1. Return the storage account URI directly if it is specified in BSL config -// 2. Try to call Azure API to get the storage account URI if possible(Background: https://github.com/vmware-tanzu/velero/issues/6163) +// 2. Try to call Azure API to get the storage account URI if possible(Background: https://github.com/velero-io/velero/issues/6163) // 3. Fall back to return the default URI func getStorageAccountURI(log logrus.FieldLogger, bslCfg map[string]string, creds map[string]string) (string, error) { // if the URI is specified in the BSL, return it directly diff --git a/pkg/util/collections/includes_excludes.go b/pkg/util/collections/includes_excludes.go index f326a4124..d5efd6c15 100644 --- a/pkg/util/collections/includes_excludes.go +++ b/pkg/util/collections/includes_excludes.go @@ -19,7 +19,7 @@ package collections import ( "strings" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/resourcepolicies" "github.com/gobwas/glob" "github.com/pkg/errors" @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/discovery" - "github.com/vmware-tanzu/velero/pkg/kuberesource" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/wildcard" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/discovery" + "github.com/velero-io/velero/pkg/kuberesource" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/wildcard" ) type globStringSet struct { @@ -274,7 +274,7 @@ func GetResourceIncludesExcludes(helper discovery.Helper, includes, excludes []s if err != nil { // If we can't resolve it, return it as-is. This prevents the generated // includes-excludes list from including *everything*, if none of the includes - // can be resolved. ref. https://github.com/vmware-tanzu/velero/issues/2461 + // can be resolved. ref. https://github.com/velero-io/velero/issues/2461 return item } diff --git a/pkg/util/collections/includes_excludes_test.go b/pkg/util/collections/includes_excludes_test.go index 1d700a729..7b260e4b5 100644 --- a/pkg/util/collections/includes_excludes_test.go +++ b/pkg/util/collections/includes_excludes_test.go @@ -19,7 +19,7 @@ package collections import ( "testing" - "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/velero-io/velero/internal/resourcepolicies" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -29,9 +29,9 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/test" ) func TestShouldInclude(t *testing.T) { diff --git a/pkg/util/csi/util.go b/pkg/util/csi/util.go index bcc424d1b..d1b151a1e 100644 --- a/pkg/util/csi/util.go +++ b/pkg/util/csi/util.go @@ -19,8 +19,8 @@ package csi import ( "strings" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/features" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/features" ) const ( diff --git a/pkg/util/csi/util_test.go b/pkg/util/csi/util_test.go index 8a3ea3cc1..e2f548189 100644 --- a/pkg/util/csi/util_test.go +++ b/pkg/util/csi/util_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/features" + "github.com/velero-io/velero/pkg/features" ) func TestCSIFeatureNotEnabledAndPluginIsFromCSI(t *testing.T) { diff --git a/pkg/util/csi/volume_snapshot.go b/pkg/util/csi/volume_snapshot.go index ed6371f7b..5fbc1e7fb 100644 --- a/pkg/util/csi/volume_snapshot.go +++ b/pkg/util/csi/volume_snapshot.go @@ -36,10 +36,10 @@ import ( "k8s.io/apimachinery/pkg/util/wait" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/stringptr" - "github.com/vmware-tanzu/velero/pkg/util/stringslice" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/stringptr" + "github.com/velero-io/velero/pkg/util/stringslice" ) const ( diff --git a/pkg/util/csi/volume_snapshot_test.go b/pkg/util/csi/volume_snapshot_test.go index 67a07d135..f00a09480 100644 --- a/pkg/util/csi/volume_snapshot_test.go +++ b/pkg/util/csi/volume_snapshot_test.go @@ -36,13 +36,13 @@ import ( clientTesting "k8s.io/client-go/testing" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/test" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - "github.com/vmware-tanzu/velero/pkg/util/logging" - "github.com/vmware-tanzu/velero/pkg/util/stringptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/logging" + "github.com/velero-io/velero/pkg/util/stringptr" ) type reactor struct { diff --git a/pkg/util/encode/encode.go b/pkg/util/encode/encode.go index b7cbdc1c7..1f783f823 100644 --- a/pkg/util/encode/encode.go +++ b/pkg/util/encode/encode.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/serializer" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util" ) // Encode converts the provided object to the specified format diff --git a/pkg/util/kube/client.go b/pkg/util/kube/client.go index 801f7ab33..fc2f1eff1 100644 --- a/pkg/util/kube/client.go +++ b/pkg/util/kube/client.go @@ -22,7 +22,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - veleroPkgClient "github.com/vmware-tanzu/velero/pkg/client" + veleroPkgClient "github.com/velero-io/velero/pkg/client" ) func PatchResource(original, updated client.Object, kbClient client.Client) error { diff --git a/pkg/util/kube/event_test.go b/pkg/util/kube/event_test.go index 645d1da2d..76969a12f 100644 --- a/pkg/util/kube/event_test.go +++ b/pkg/util/kube/event_test.go @@ -30,7 +30,7 @@ import ( corev1api "k8s.io/api/core/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestEvent(t *testing.T) { diff --git a/pkg/util/kube/list_watch_test.go b/pkg/util/kube/list_watch_test.go index a0ed9760e..64521b6df 100644 --- a/pkg/util/kube/list_watch_test.go +++ b/pkg/util/kube/list_watch_test.go @@ -24,8 +24,8 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestInternalLW(t *testing.T) { diff --git a/pkg/util/kube/node_test.go b/pkg/util/kube/node_test.go index 9f14c380b..c9a929891 100644 --- a/pkg/util/kube/node_test.go +++ b/pkg/util/kube/node_test.go @@ -24,13 +24,13 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/velero-io/velero/pkg/builder" kubeClientFake "k8s.io/client-go/kubernetes/fake" clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestIsLinuxNode(t *testing.T) { diff --git a/pkg/util/kube/periodical_enqueue_source_test.go b/pkg/util/kube/periodical_enqueue_source_test.go index b5e97321a..b4a2e4f9d 100644 --- a/pkg/util/kube/periodical_enqueue_source_test.go +++ b/pkg/util/kube/periodical_enqueue_source_test.go @@ -33,8 +33,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/vmware-tanzu/velero/internal/storage" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/internal/storage" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestStart(t *testing.T) { diff --git a/pkg/util/kube/pod_test.go b/pkg/util/kube/pod_test.go index aa8d4db99..90301c62c 100644 --- a/pkg/util/kube/pod_test.go +++ b/pkg/util/kube/pod_test.go @@ -39,7 +39,7 @@ import ( clientTesting "k8s.io/client-go/testing" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" ) diff --git a/pkg/util/kube/predicate_test.go b/pkg/util/kube/predicate_test.go index eb00e2fed..2cc956a75 100644 --- a/pkg/util/kube/predicate_test.go +++ b/pkg/util/kube/predicate_test.go @@ -26,7 +26,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/event" - velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestSpecChangePredicate(t *testing.T) { diff --git a/pkg/util/kube/priority_class_test.go b/pkg/util/kube/priority_class_test.go index 9d6a52599..d552f76d1 100644 --- a/pkg/util/kube/priority_class_test.go +++ b/pkg/util/kube/priority_class_test.go @@ -27,7 +27,7 @@ import ( "k8s.io/client-go/kubernetes/fake" k8stesting "k8s.io/client-go/testing" - velerotesting "github.com/vmware-tanzu/velero/pkg/test" + velerotesting "github.com/velero-io/velero/pkg/test" ) func TestValidatePriorityClass(t *testing.T) { diff --git a/pkg/util/kube/pvc_pv_test.go b/pkg/util/kube/pvc_pv_test.go index 63b8e1edd..8ba298c52 100644 --- a/pkg/util/kube/pvc_pv_test.go +++ b/pkg/util/kube/pvc_pv_test.go @@ -33,8 +33,8 @@ import ( clientTesting "k8s.io/client-go/testing" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) type reactor struct { diff --git a/pkg/util/kube/resource_requirements.go b/pkg/util/kube/resource_requirements.go index 12cf7a79c..5e385254c 100644 --- a/pkg/util/kube/resource_requirements.go +++ b/pkg/util/kube/resource_requirements.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/api/resource" - "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/velero-io/velero/pkg/constant" ) // ParseCPUAndMemoryResources is a helper function that parses CPU and memory requests and limits, diff --git a/pkg/util/kube/secrets_test.go b/pkg/util/kube/secrets_test.go index 8707c9be3..120a9c457 100644 --- a/pkg/util/kube/secrets_test.go +++ b/pkg/util/kube/secrets_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestGetSecretKey(t *testing.T) { diff --git a/pkg/util/kube/security_context_test.go b/pkg/util/kube/security_context_test.go index 6ba857bc7..4153b37ee 100644 --- a/pkg/util/kube/security_context_test.go +++ b/pkg/util/kube/security_context_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/velero-io/velero/pkg/util/boolptr" ) func TestParseSecurityContext(t *testing.T) { diff --git a/pkg/util/kube/utils.go b/pkg/util/kube/utils.go index 5e5e97603..89c838615 100644 --- a/pkg/util/kube/utils.go +++ b/pkg/util/kube/utils.go @@ -37,10 +37,10 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/label" - "github.com/vmware-tanzu/velero/pkg/uploader" - "github.com/vmware-tanzu/velero/pkg/util/filesystem" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/label" + "github.com/velero-io/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/util/filesystem" ) // These annotations are taken from the Kubernetes persistent volume/persistent volume claim controller. @@ -244,7 +244,7 @@ func isProvisionedByCSI(log logrus.FieldLogger, pv *corev1api.PersistentVolume, return true, nil } // Although the pv.Spec.CSI is nil, the volume could be provisioned by a CSI driver when enabling the CSI migration - // Refer to https://github.com/vmware-tanzu/velero/issues/4496 for more details + // Refer to https://github.com/velero-io/velero/issues/4496 for more details if pv.Annotations != nil { driverName := pv.Annotations[KubeAnnDynamicallyProvisioned] migratedDriver := pv.Annotations[KubeAnnMigratedTo] diff --git a/pkg/util/kube/utils_test.go b/pkg/util/kube/utils_test.go index df23903a0..04de4e0a2 100644 --- a/pkg/util/kube/utils_test.go +++ b/pkg/util/kube/utils_test.go @@ -35,9 +35,9 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/client-go/kubernetes/fake" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotest "github.com/vmware-tanzu/velero/pkg/test" - "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/velero-io/velero/pkg/builder" + velerotest "github.com/velero-io/velero/pkg/test" + "github.com/velero-io/velero/pkg/uploader" ) func TestNamespaceAndName(t *testing.T) { diff --git a/pkg/util/logging/dual_mode_logger_test.go b/pkg/util/logging/dual_mode_logger_test.go index c22d19dca..c96ed5a8c 100644 --- a/pkg/util/logging/dual_mode_logger_test.go +++ b/pkg/util/logging/dual_mode_logger_test.go @@ -26,7 +26,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestDualModeLogger(t *testing.T) { diff --git a/pkg/util/logging/error_location_hook_test.go b/pkg/util/logging/error_location_hook_test.go index f6f230c02..664b275a0 100644 --- a/pkg/util/logging/error_location_hook_test.go +++ b/pkg/util/logging/error_location_hook_test.go @@ -55,7 +55,7 @@ func TestFire(t *testing.T) { expectedEntryFields: map[string]any{ logrus.ErrorKey: pkgerrs.New("a pkg/errors error"), errorFileField: "", - errorFunctionField: "github.com/vmware-tanzu/velero/pkg/util/logging.TestFire", + errorFunctionField: "github.com/velero-io/velero/pkg/util/logging.TestFire", }, }, { diff --git a/pkg/util/logging/format_flag.go b/pkg/util/logging/format_flag.go index c757a17dd..d49af16a3 100644 --- a/pkg/util/logging/format_flag.go +++ b/pkg/util/logging/format_flag.go @@ -15,7 +15,7 @@ limitations under the License. */ package logging -import "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" +import "github.com/velero-io/velero/pkg/cmd/util/flag" // Format is a string representation of the desired output format for logs type Format string diff --git a/pkg/util/logging/log_counter_hook.go b/pkg/util/logging/log_counter_hook.go index 63c9342df..52e453fc3 100644 --- a/pkg/util/logging/log_counter_hook.go +++ b/pkg/util/logging/log_counter_hook.go @@ -23,7 +23,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/pkg/util/results" ) // LogHook is a logrus hook that counts the number of log diff --git a/pkg/util/logging/log_counter_hook_test.go b/pkg/util/logging/log_counter_hook_test.go index 1afd2bc29..989e155fc 100644 --- a/pkg/util/logging/log_counter_hook_test.go +++ b/pkg/util/logging/log_counter_hook_test.go @@ -9,7 +9,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/velero-io/velero/pkg/util/results" ) func TestLogHook_Fire(t *testing.T) { diff --git a/pkg/util/logging/log_level_flag.go b/pkg/util/logging/log_level_flag.go index ff0f0efb2..1dd7fd111 100644 --- a/pkg/util/logging/log_level_flag.go +++ b/pkg/util/logging/log_level_flag.go @@ -21,7 +21,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/pkg/cmd/util/flag" ) var sortedLogLevels = sortLogLevels() diff --git a/pkg/util/logging/log_location_hook.go b/pkg/util/logging/log_location_hook.go index a0e88813a..c2abf512f 100644 --- a/pkg/util/logging/log_location_hook.go +++ b/pkg/util/logging/log_location_hook.go @@ -28,7 +28,7 @@ const ( logSourceField = "logSource" logSourceSetMarkerField = "@logSourceSetBy" logrusPackage = "github.com/sirupsen/logrus" - veleroPackage = "github.com/vmware-tanzu/velero/" + veleroPackage = "github.com/velero-io/velero/" veleroPackageLen = len(veleroPackage) ) @@ -60,7 +60,7 @@ func (h *LogLocationHook) Fire(entry *logrus.Entry) error { // skip 2 frames: // runtime.Callers - // github.com/vmware-tanzu/velero/pkg/util/logging/(*LogLocationHook).Fire + // github.com/velero-io/velero/pkg/util/logging/(*LogLocationHook).Fire n := runtime.Callers(2, pcs) // re-slice pcs based on the number of entries written @@ -122,7 +122,7 @@ func getLogSourceSetMarker(entry *logrus.Entry) string { func removeVeleroPackagePrefix(file string) string { if index := strings.Index(file, veleroPackage); index != -1 { - // strip off .../github.com/vmware-tanzu/velero/ so we just have pkg/... + // strip off .../github.com/velero-io/velero/ so we just have pkg/... return file[index+veleroPackageLen:] } diff --git a/pkg/util/logging/log_location_hook_test.go b/pkg/util/logging/log_location_hook_test.go index 74f007a0b..8fc23daad 100644 --- a/pkg/util/logging/log_location_hook_test.go +++ b/pkg/util/logging/log_location_hook_test.go @@ -23,6 +23,6 @@ import ( ) func TestRemoveVeleroPackagePrefix(t *testing.T) { - assert.Equal(t, "pkg/foo.go", removeVeleroPackagePrefix("github.com/vmware-tanzu/velero/pkg/foo.go")) - assert.Equal(t, "github.com/vmware-tanzu/velero-plugin-example/foo.go", removeVeleroPackagePrefix("github.com/vmware-tanzu/velero-plugin-example/foo.go")) + assert.Equal(t, "pkg/foo.go", removeVeleroPackagePrefix("github.com/velero-io/velero/pkg/foo.go")) + assert.Equal(t, "github.com/velero-io/velero-plugin-example/foo.go", removeVeleroPackagePrefix("github.com/velero-io/velero-plugin-example/foo.go")) } diff --git a/pkg/util/podvolume/pod_volume.go b/pkg/util/podvolume/pod_volume.go index 7c7e0f9c4..42a36fcbb 100644 --- a/pkg/util/podvolume/pod_volume.go +++ b/pkg/util/podvolume/pod_volume.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/util" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/util" ) // PVCPodCache provides a cached mapping from PVC to the pods that use it. diff --git a/pkg/util/podvolume/pod_volume_test.go b/pkg/util/podvolume/pod_volume_test.go index 87a6f3a0f..894a88034 100644 --- a/pkg/util/podvolume/pod_volume_test.go +++ b/pkg/util/podvolume/pod_volume_test.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerotest "github.com/velero-io/velero/pkg/test" ) func TestGetVolumesToBackup(t *testing.T) { diff --git a/pkg/util/scheme.go b/pkg/util/scheme.go index c398e4196..893594e12 100644 --- a/pkg/util/scheme.go +++ b/pkg/util/scheme.go @@ -20,8 +20,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" utilruntime "k8s.io/apimachinery/pkg/util/runtime" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) var VeleroScheme = runtime.NewScheme() diff --git a/pkg/util/velero/restore/util.go b/pkg/util/velero/restore/util.go index e0812884b..b054ae606 100644 --- a/pkg/util/velero/restore/util.go +++ b/pkg/util/velero/restore/util.go @@ -1,7 +1,7 @@ package restore import ( - api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + api "github.com/velero-io/velero/pkg/apis/velero/v1" ) func IsResourcePolicyValid(resourcePolicy string) bool { diff --git a/pkg/util/velero/restore/util_test.go b/pkg/util/velero/restore/util_test.go index be72ff8ba..dc1f82d22 100644 --- a/pkg/util/velero/restore/util_test.go +++ b/pkg/util/velero/restore/util_test.go @@ -5,7 +5,7 @@ import ( "github.com/stretchr/testify/require" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) func TestIsResourcePolicyValid(t *testing.T) { diff --git a/pkg/util/velero/velero.go b/pkg/util/velero/velero.go index a58d6e76b..a47312775 100644 --- a/pkg/util/velero/velero.go +++ b/pkg/util/velero/velero.go @@ -20,7 +20,7 @@ import ( appsv1api "k8s.io/api/apps/v1" corev1api "k8s.io/api/core/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" ) // GetNodeSelectorFromVeleroServer get the node selector from the Velero server deployment diff --git a/pkg/util/velero/velero_test.go b/pkg/util/velero/velero_test.go index c4e201780..9d2060341 100644 --- a/pkg/util/velero/velero_test.go +++ b/pkg/util/velero/velero_test.go @@ -26,9 +26,9 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/pkg/util/boolptr" ) func TestGetNodeSelectorFromVeleroServer(t *testing.T) { diff --git a/restore-hooks_product-requirements.md b/restore-hooks_product-requirements.md index 1b943fe82..cb62c6818 100644 --- a/restore-hooks_product-requirements.md +++ b/restore-hooks_product-requirements.md @@ -2,7 +2,7 @@ Velero Restore Hooks - PRD (Product Requirements Document) MVP Feature Set -Relates to: [https://github.com/vmware-tanzu/velero/issues/2116](https://github.com/vmware-tanzu/velero/issues/2116) +Relates to: [https://github.com/velero-io/velero/issues/2116](https://github.com/velero-io/velero/issues/2116) # **Change tracking** @@ -23,9 +23,9 @@ _This is a live document, you can reach me on the following channels for more in -* [https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/vmware-tanzu/velero/2465](https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/vmware-tanzu/velero/2465) - * [https://github.com/vmware-tanzu/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a](https://github.com/vmware-tanzu/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a) -* [https://github.com/vmware-tanzu/velero/issues/1150](https://github.com/vmware-tanzu/velero/issues/1150) +* [https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/velero-io/velero/2465](https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/velero-io/velero/2465) + * [https://github.com/velero-io/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a](https://github.com/velero-io/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a) +* [https://github.com/velero-io/velero/issues/1150](https://github.com/velero-io/velero/issues/1150) Background @@ -79,7 +79,7 @@ MVP Use Cases The following use cases must be included as part of the Velero restore hooks MVP (minimum viable product). -**Note: **Processing of concurrent vs sequential workloads is slated later in the Velero roadmap (see [https://github.com/vmware-tanzu/velero/pull/2548/files](https://github.com/vmware-tanzu/velero/pull/2548/files)). The MVP for this feature set will align with restore of single workloads vs concurrent workload restores. A second epic will be created to address the concurrent restore operations and will be added to the backlog for priority visibility. +**Note: **Processing of concurrent vs sequential workloads is slated later in the Velero roadmap (see [https://github.com/velero-io/velero/pull/2548/files](https://github.com/velero-io/velero/pull/2548/files)). The MVP for this feature set will align with restore of single workloads vs concurrent workload restores. A second epic will be created to address the concurrent restore operations and will be added to the backlog for priority visibility. **Note: **Please refer to the Requirements section of this document for more details on what items are P0 (must have in the MVP), P1 (should not ship without for the MVP), P2 (nice to haves). 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..378f99055 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/velero-io/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..11973f50a 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/velero-io/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..67518359a 100644 --- a/site/content/docs/v1.10/csi.md +++ b/site/content/docs/v1.10/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). ## Prerequisites @@ -68,8 +68,8 @@ 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/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/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..e1837fb7d 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) | 🚫 | -| [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) | 🚫 | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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..d10d52570 100644 --- a/site/content/docs/v1.11/csi.md +++ b/site/content/docs/v1.11/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). ## Prerequisites @@ -70,8 +70,8 @@ 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/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/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..e1837fb7d 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) | 🚫 | -| [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) | 🚫 | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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..1654626f4 100644 --- a/site/content/docs/v1.12/csi.md +++ b/site/content/docs/v1.12/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). ## Prerequisites @@ -112,8 +112,8 @@ 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/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/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..e1837fb7d 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) | 🚫 | -| [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) | 🚫 | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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..23ccb29fc 100644 --- a/site/content/docs/v1.13/csi.md +++ b/site/content/docs/v1.13/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). ## Prerequisites @@ -112,8 +112,8 @@ 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/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/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..e1837fb7d 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) | 🚫 | -| [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) | 🚫 | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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..a9efe4fb7 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/velero-io/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..4ec75a9c1 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/velero-io/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..f336caba7 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/velero-io/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..4ec75a9c1 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/velero-io/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..68bf56b2a 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/velero-io/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..33fe1ef70 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/velero-io/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..6c916e0e1 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/velero-io/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..11973f50a 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/velero-io/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..378f99055 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/velero-io/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..11973f50a 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/velero-io/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/csi.md b/site/content/docs/v1.3.0/csi.md index a8f272a32..99d11daf5 100644 --- a/site/content/docs/v1.3.0/csi.md +++ b/site/content/docs/v1.3.0/csi.md @@ -10,7 +10,7 @@ Velero supports taking Container Storage Interface (CSI) snapshots as a beta fea 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster should be the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Roadmap 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/csi.md b/site/content/docs/v1.3.1/csi.md index a8f272a32..99d11daf5 100644 --- a/site/content/docs/v1.3.1/csi.md +++ b/site/content/docs/v1.3.1/csi.md @@ -10,7 +10,7 @@ Velero supports taking Container Storage Interface (CSI) snapshots as a beta fea 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster should be the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Roadmap 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/csi.md b/site/content/docs/v1.3.2/csi.md index 388fbc368..535c36008 100644 --- a/site/content/docs/v1.3.2/csi.md +++ b/site/content/docs/v1.3.2/csi.md @@ -12,19 +12,19 @@ The following are the prerequisites for using Velero to take Container Storage I 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster is the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Implementation Choices -This section documents some of the choices made during implementation of the Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/): +This section documents some of the choices made during implementation of the Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/): 1. Volumesnapshots created by the plugin will be retained only for the lifetime of the backup even if the `DeletionPolicy` on the volumesnapshotclass is set to `Retain`. To accomplish this, during deletion of the backup the prior to deleting the volumesnapshot, volumesnapshotcontent object will be patched to set its `DeletionPolicy` to `Delete`. Thus deleting volumesnapshot object will result in cascade delete of the volumesnapshotcontent and the snapshot in the storage provider. 1. Volumesnapshotcontent objects created during a velero backup that are dangling, unbound to a volumesnapshot object, will also be discovered, through labels, and deleted on backup deletion. # Known Limitations -1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/vmware-tanzu/velero-plugin-for-csi/issues/17)_ +1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/velero-io/velero-plugin-for-csi/issues/17)_ # Roadmap 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/csi.md b/site/content/docs/v1.4/csi.md index 147f4b581..52a8c8dc3 100644 --- a/site/content/docs/v1.4/csi.md +++ b/site/content/docs/v1.4/csi.md @@ -43,7 +43,7 @@ This section documents some of the choices made during implementation of the Vel ## Known Limitations -1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/vmware-tanzu/velero-plugin-for-csi/issues/17)_ +1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/velero-io/velero-plugin-for-csi/issues/17)_ ## Roadmap @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi 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..862a034f3 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) | -| [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) | +| [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/velero-io/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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/csi.md b/site/content/docs/v1.5/csi.md index 49f4f77e9..1f30a07ee 100644 --- a/site/content/docs/v1.5/csi.md +++ b/site/content/docs/v1.5/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi 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..82daa0a15 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) | -| [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) | +| [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/velero-io/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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/csi.md b/site/content/docs/v1.6/csi.md index 49f4f77e9..1f30a07ee 100644 --- a/site/content/docs/v1.6/csi.md +++ b/site/content/docs/v1.6/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi 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..10ad404dc 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) | -| [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) | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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/csi.md b/site/content/docs/v1.7/csi.md index 99365e719..5c8a1f848 100644 --- a/site/content/docs/v1.7/csi.md +++ b/site/content/docs/v1.7/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi 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..122ecbd7b 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) | -| [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) | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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/csi.md b/site/content/docs/v1.8/csi.md index 99365e719..5c8a1f848 100644 --- a/site/content/docs/v1.8/csi.md +++ b/site/content/docs/v1.8/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi 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..10ad404dc 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) | -| [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) | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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..46363e564 100644 --- a/site/content/docs/v1.9/csi.md +++ b/site/content/docs/v1.9/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). ## Prerequisites @@ -68,8 +68,8 @@ 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/ +[2]: https://github.com/velero-io/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/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..a45bf70ef 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) | 🚫 | -| [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) | 🚫 | +| [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/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/plugins/list/10-container-storage-interface.md b/site/content/plugins/list/10-container-storage-interface.md index 21ed41db7..8649a947f 100644 --- a/site/content/plugins/list/10-container-storage-interface.md +++ b/site/content/plugins/list/10-container-storage-interface.md @@ -1,6 +1,6 @@ --- title: Container Storage Interface (CSI) -link: https://github.com/vmware-tanzu/velero-plugin-for-csi +link: https://github.com/velero-io/velero-plugin-for-csi 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..a4c3f067f 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 @@ -16,7 +16,7 @@ Velero v1.4.0 now extends Velero’s support for snapshotting beyond Velero’s The [Container Storage Interface](https://github.com/container-storage-interface/spec) (CSI) is a way for container orchestrators such as Kubernetes to provide a standard interface for storage systems, without having to create drivers for each orchestration system. While basic attach and detach volume operations are generally available in Kubernetes, the volume snapshotting APIs are still in beta. The Velero team is working with the Data Protection Working Group to ensure that the CSI snapshotting API specification is useful to end users and tool builders. We intend to trail behind the official Kubernetes support for the feature, entering general availability sometime after the feature is GA in Kubernetes itself. -Activating and using the CSI support in Velero will require enabling the `EnableCSI` feature flag and installing the [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) alongside the Velero server. For full details on installing and using the feature, see our [CSI beta page](https://velero.io/docs/csi/). +Activating and using the CSI support in Velero will require enabling the `EnableCSI` feature flag and installing the [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) alongside the Velero server. For full details on installing and using the feature, see our [CSI beta page](https://velero.io/docs/csi/). As a very brief example of the seamless integration of CSI into Velero. We will back up and restore a sample workload in the `csi-app` namespace that is using volumes backed by the CSI hostpath plugin driver. Installing and configuring the driver is outside the scope of this blog post, but we will cover the complete example in the future. @@ -30,7 +30,7 @@ Waiting for backup to complete. You may safely press ctrl-c to stop waiting - yo Backup completed with status: Completed. You may check for more information using the commands `velero backup describe csi-b1` and `velero backup logs csi-b1`. ``` -Velero will detect the use of CSI volumes and invoke [BackupItemAction](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create the CSI VolumeSnapshot and VolumesnapshotContents as part of the backup. +Velero will detect the use of CSI volumes and invoke [BackupItemAction](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create the CSI VolumeSnapshot and VolumesnapshotContents as part of the backup. ``` $ kubectl -n csi-app get volumesnapshot,volumesnapshotcontent -lvelero.io/backup-name=csi-b1 -oname @@ -48,7 +48,7 @@ Waiting for restore to complete. You may safely press ctrl-c to stop waiting - y Restore completed with status: Completed. You may check for more information using the commands `velero restore describe csi-b1-20200515112009` and `velero restore logs csi-b1-20200515112009`. ``` -Velero will detect the CSI Snapshot API objects and invoke the [RestoreItemAction](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create CSI VolumeSnapshotContent and statically bind to the VolumeSnapshot created during backup. +Velero will detect the CSI Snapshot API objects and invoke the [RestoreItemAction](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create CSI VolumeSnapshotContent and statically bind to the VolumeSnapshot created during backup. ``` $ kubectl -n csi-app get volumesnapshot,volumesnapshotcontent -lvelero.io/restore-name=csi-b1-20200515112009 -oname @@ -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..12337f33c 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/velero-io/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 @@ -199,4 +199,4 @@ More details about CSI volume snapshotting and its support in Velero may be foun - [Kubernetes 1.17 Feature: Kubernetes Volume Snapshot Moves to Beta](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/) for more information on the CSI beta snapshot APIs. - Prerequisites to use this feature is available [on our website](https://velero.io/docs/csi). - [Kubernetes CSI docs](https://kubernetes-csi.github.io/docs/sidecar-containers.html): To understand components in a CSI environment -- [Velero plugin for CSI snapshots](https://github.com/vmware-tanzu/velero-plugin-for-csi) for implementation details of the CSI plugin. +- [Velero plugin for CSI snapshots](https://github.com/velero-io/velero-plugin-for-csi) for implementation details of the CSI plugin. 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..cdf41c4ce 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/velero-io/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 }} diff --git a/test/e2e/README.md b/test/e2e/README.md index f4e7714af..583606971 100644 --- a/test/e2e/README.md +++ b/test/e2e/README.md @@ -180,8 +180,8 @@ make test-e2e ``` Please refer to `velero-plugin-for-microsoft-azure` documentation for instruction: -* [set up permissions for Velero](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#set-permissions-for-velero) -* [set up azure storage account and blob container](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup-azure-storage-account-and-blob-container) +* [set up permissions for Velero](https://github.com/velero-io/velero-plugin-for-microsoft-azure#set-permissions-for-velero) +* [set up azure storage account and blob container](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup-azure-storage-account-and-blob-container) 1. Run Multi-API group and version tests using MinIO as the backup storage location: ``` bash diff --git a/test/e2e/backup/backup.go b/test/e2e/backup/backup.go index 43a6f4f23..91b0fcae0 100644 --- a/test/e2e/backup/backup.go +++ b/test/e2e/backup/backup.go @@ -25,11 +25,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/util/velero" ) type BackupRestoreTestConfig struct { @@ -208,7 +208,7 @@ func BackupRestoreTest(backupRestoreTestConfig BackupRestoreTestConfig) { )).To(Succeed()) // We limit the length of backup name here to avoid the issue of vsphere plugin - // https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/370 + // https://github.com/velero-io/velero-plugin-for-vsphere/issues/370 // We can remove the logic once the issue is fixed backupName = "backup-" + common.AdditionalBSLName restoreName = "restore-" + common.AdditionalBSLName diff --git a/test/e2e/backups/deletion.go b/test/e2e/backups/deletion.go index 54388b70a..ccffcec55 100644 --- a/test/e2e/backups/deletion.go +++ b/test/e2e/backups/deletion.go @@ -27,11 +27,11 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) // Test backup and restore of Kibishii using restic diff --git a/test/e2e/backups/sync_backups.go b/test/e2e/backups/sync_backups.go index 447fc735b..cbbba10c1 100644 --- a/test/e2e/backups/sync_backups.go +++ b/test/e2e/backups/sync_backups.go @@ -16,7 +16,7 @@ * / */ -// Refer to https://github.com/vmware-tanzu/velero/issues/4253 +// Refer to https://github.com/velero-io/velero/issues/4253 package backups import ( @@ -30,10 +30,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) type SyncBackups struct { diff --git a/test/e2e/backups/ttl.go b/test/e2e/backups/ttl.go index f781c32d4..998e55f19 100644 --- a/test/e2e/backups/ttl.go +++ b/test/e2e/backups/ttl.go @@ -30,11 +30,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) type TTL struct { diff --git a/test/e2e/basic/api-group/enable_api_group_extentions.go b/test/e2e/basic/api-group/enable_api_group_extentions.go index 546d2f721..11a057f3e 100644 --- a/test/e2e/basic/api-group/enable_api_group_extentions.go +++ b/test/e2e/basic/api-group/enable_api_group_extentions.go @@ -24,9 +24,9 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) func APIExtensionsVersionsTest() { diff --git a/test/e2e/basic/api-group/enable_api_group_versions.go b/test/e2e/basic/api-group/enable_api_group_versions.go index 13ee3a39e..5155b8497 100644 --- a/test/e2e/basic/api-group/enable_api_group_versions.go +++ b/test/e2e/basic/api-group/enable_api_group_versions.go @@ -34,11 +34,11 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + "github.com/velero-io/velero/pkg/builder" + veleroexec "github.com/velero-io/velero/pkg/util/exec" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) var veleroCfg VeleroConfig diff --git a/test/e2e/basic/backup-volume-info/base.go b/test/e2e/basic/backup-volume-info/base.go index 2cd574b5c..8f2da8772 100644 --- a/test/e2e/basic/backup-volume-info/base.go +++ b/test/e2e/basic/backup-volume-info/base.go @@ -27,11 +27,11 @@ import ( "github.com/pkg/errors" corev1api "k8s.io/api/core/v1" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) type BackupVolumeInfo struct { @@ -144,7 +144,7 @@ func (v *BackupVolumeInfo) CreateResources() error { for _, pod := range podList.Items { for i := 0; i <= pvcCount-1; i++ { - // Hitting issue https://github.com/vmware-tanzu/velero/issues/7388 + // Hitting issue https://github.com/velero-io/velero/issues/7388 // So populate data only to some of pods, leave other pods empty to verify empty PV datamover if i%2 == 0 { Expect(CreateFileToPod( diff --git a/test/e2e/basic/backup-volume-info/csi_data_mover.go b/test/e2e/basic/backup-volume-info/csi_data_mover.go index 43edb0ddb..9731c7d4b 100644 --- a/test/e2e/basic/backup-volume-info/csi_data_mover.go +++ b/test/e2e/basic/backup-volume-info/csi_data_mover.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var CSIDataMoverVolumeInfoTest func() = TestFunc(&CSIDataMoverVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/csi_snapshot.go b/test/e2e/basic/backup-volume-info/csi_snapshot.go index 5eddb4ea2..fe008baaa 100644 --- a/test/e2e/basic/backup-volume-info/csi_snapshot.go +++ b/test/e2e/basic/backup-volume-info/csi_snapshot.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var CSISnapshotVolumeInfoTest func() = TestFunc(&CSISnapshotVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/filesystem_upload.go b/test/e2e/basic/backup-volume-info/filesystem_upload.go index e6266c0c6..7c176fc50 100644 --- a/test/e2e/basic/backup-volume-info/filesystem_upload.go +++ b/test/e2e/basic/backup-volume-info/filesystem_upload.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var FilesystemUploadVolumeInfoTest func() = TestFunc(&FilesystemUploadVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/native_snapshot.go b/test/e2e/basic/backup-volume-info/native_snapshot.go index 13a75d2e6..725755f5b 100644 --- a/test/e2e/basic/backup-volume-info/native_snapshot.go +++ b/test/e2e/basic/backup-volume-info/native_snapshot.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var NativeSnapshotVolumeInfoTest func() = TestFunc(&NativeSnapshotVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/skipped_volumes.go b/test/e2e/basic/backup-volume-info/skipped_volumes.go index 2fc801a5f..755c527b9 100644 --- a/test/e2e/basic/backup-volume-info/skipped_volumes.go +++ b/test/e2e/basic/backup-volume-info/skipped_volumes.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var SkippedVolumeInfoTest func() = TestFunc(&SkippedVolumeInfo{ diff --git a/test/e2e/basic/namespace-mapping.go b/test/e2e/basic/namespace-mapping.go index 6816b2df0..54314e5dc 100644 --- a/test/e2e/basic/namespace-mapping.go +++ b/test/e2e/basic/namespace-mapping.go @@ -8,9 +8,9 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" ) type NamespaceMapping struct { diff --git a/test/e2e/basic/nodeport.go b/test/e2e/basic/nodeport.go index b561295a1..18f11fa1e 100644 --- a/test/e2e/basic/nodeport.go +++ b/test/e2e/basic/nodeport.go @@ -10,10 +10,10 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/util/intstr" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) type NodePort struct { diff --git a/test/e2e/basic/resources-check/namespaces.go b/test/e2e/basic/resources-check/namespaces.go index 922e4ed07..c2f8e7d33 100644 --- a/test/e2e/basic/resources-check/namespaces.go +++ b/test/e2e/basic/resources-check/namespaces.go @@ -25,8 +25,8 @@ import ( "github.com/pkg/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) type MultiNSBackup struct { diff --git a/test/e2e/basic/resources-check/namespaces_annotation.go b/test/e2e/basic/resources-check/namespaces_annotation.go index e698d4818..e835b99f7 100644 --- a/test/e2e/basic/resources-check/namespaces_annotation.go +++ b/test/e2e/basic/resources-check/namespaces_annotation.go @@ -22,8 +22,8 @@ import ( "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) type NSAnnotationCase struct { diff --git a/test/e2e/basic/resources-check/rbac.go b/test/e2e/basic/resources-check/rbac.go index b79c3615f..9ab4a4e90 100644 --- a/test/e2e/basic/resources-check/rbac.go +++ b/test/e2e/basic/resources-check/rbac.go @@ -39,8 +39,8 @@ import ( . "github.com/onsi/ginkgo/v2" "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) type RBACCase struct { diff --git a/test/e2e/basic/resources-check/resources_check.go b/test/e2e/basic/resources-check/resources_check.go index 880063657..b656300c4 100644 --- a/test/e2e/basic/resources-check/resources_check.go +++ b/test/e2e/basic/resources-check/resources_check.go @@ -33,7 +33,7 @@ limitations under the License. package basic import ( - . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/velero-io/velero/test/e2e/test" ) func GetResourcesCheckTestCases() []VeleroBackupRestoreTest { diff --git a/test/e2e/basic/restore_exec_hooks.go b/test/e2e/basic/restore_exec_hooks.go index fc1b8ceb8..10757feff 100644 --- a/test/e2e/basic/restore_exec_hooks.go +++ b/test/e2e/basic/restore_exec_hooks.go @@ -24,10 +24,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) // RestoreExecHooks tests that a pod with multiple restore exec hooks does not hang diff --git a/test/e2e/basic/storage-class-changing.go b/test/e2e/basic/storage-class-changing.go index 08481d4ad..9a0aa17cb 100644 --- a/test/e2e/basic/storage-class-changing.go +++ b/test/e2e/basic/storage-class-changing.go @@ -7,12 +7,12 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) type StorageClasssChanging struct { diff --git a/test/e2e/bsl-mgmt/deletion.go b/test/e2e/bsl-mgmt/deletion.go index 838aa67b5..9088dee01 100644 --- a/test/e2e/bsl-mgmt/deletion.go +++ b/test/e2e/bsl-mgmt/deletion.go @@ -27,11 +27,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) const ( @@ -143,7 +143,7 @@ func BslDeletionTest(useVolumeSnapshots bool) { podName2 := "kibishii-deployment-1" label1 := "for=1" - // TODO remove when issue https://github.com/vmware-tanzu/velero/issues/4724 is fixed + // TODO remove when issue https://github.com/velero-io/velero/issues/4724 is fixed //label2 := "for!=1" label2 := "for=2" By("Create namespace for sample workload", func() { diff --git a/test/e2e/e2e_suite_test.go b/test/e2e/e2e_suite_test.go index 909cc8074..dadd3a2b9 100644 --- a/test/e2e/e2e_suite_test.go +++ b/test/e2e/e2e_suite_test.go @@ -29,30 +29,30 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/backup" - . "github.com/vmware-tanzu/velero/test/e2e/backups" - . "github.com/vmware-tanzu/velero/test/e2e/basic" - . "github.com/vmware-tanzu/velero/test/e2e/basic/api-group" - . "github.com/vmware-tanzu/velero/test/e2e/basic/backup-volume-info" - . "github.com/vmware-tanzu/velero/test/e2e/basic/resources-check" - . "github.com/vmware-tanzu/velero/test/e2e/bsl-mgmt" - . "github.com/vmware-tanzu/velero/test/e2e/migration" - . "github.com/vmware-tanzu/velero/test/e2e/nodeagentconfig" - . "github.com/vmware-tanzu/velero/test/e2e/parallelfilesdownload" - . "github.com/vmware-tanzu/velero/test/e2e/parallelfilesupload" - . "github.com/vmware-tanzu/velero/test/e2e/privilegesmgmt" - . "github.com/vmware-tanzu/velero/test/e2e/pv-backup" - . "github.com/vmware-tanzu/velero/test/e2e/repomaintenance" - . "github.com/vmware-tanzu/velero/test/e2e/resource-filtering" - . "github.com/vmware-tanzu/velero/test/e2e/resourcemodifiers" - . "github.com/vmware-tanzu/velero/test/e2e/resourcepolicies" - . "github.com/vmware-tanzu/velero/test/e2e/scale" - . "github.com/vmware-tanzu/velero/test/e2e/schedule" - . "github.com/vmware-tanzu/velero/test/e2e/upgrade" - "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + "github.com/velero-io/velero/pkg/cmd/cli/install" + "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/backup" + . "github.com/velero-io/velero/test/e2e/backups" + . "github.com/velero-io/velero/test/e2e/basic" + . "github.com/velero-io/velero/test/e2e/basic/api-group" + . "github.com/velero-io/velero/test/e2e/basic/backup-volume-info" + . "github.com/velero-io/velero/test/e2e/basic/resources-check" + . "github.com/velero-io/velero/test/e2e/bsl-mgmt" + . "github.com/velero-io/velero/test/e2e/migration" + . "github.com/velero-io/velero/test/e2e/nodeagentconfig" + . "github.com/velero-io/velero/test/e2e/parallelfilesdownload" + . "github.com/velero-io/velero/test/e2e/parallelfilesupload" + . "github.com/velero-io/velero/test/e2e/privilegesmgmt" + . "github.com/velero-io/velero/test/e2e/pv-backup" + . "github.com/velero-io/velero/test/e2e/repomaintenance" + . "github.com/velero-io/velero/test/e2e/resource-filtering" + . "github.com/velero-io/velero/test/e2e/resourcemodifiers" + . "github.com/velero-io/velero/test/e2e/resourcepolicies" + . "github.com/velero-io/velero/test/e2e/scale" + . "github.com/velero-io/velero/test/e2e/schedule" + . "github.com/velero-io/velero/test/e2e/upgrade" + "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) func init() { diff --git a/test/e2e/migration/migration.go b/test/e2e/migration/migration.go index e890189c3..faeafc2c8 100644 --- a/test/e2e/migration/migration.go +++ b/test/e2e/migration/migration.go @@ -24,14 +24,14 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/vmware-tanzu/velero/test" - framework "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - util "github.com/vmware-tanzu/velero/test/util/csi" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - "github.com/vmware-tanzu/velero/test/util/kibishii" - "github.com/vmware-tanzu/velero/test/util/providers" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + "github.com/velero-io/velero/test" + framework "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + util "github.com/velero-io/velero/test/util/csi" + k8sutil "github.com/velero-io/velero/test/util/k8s" + "github.com/velero-io/velero/test/util/kibishii" + "github.com/velero-io/velero/test/util/providers" + veleroutil "github.com/velero-io/velero/test/util/velero" ) const BackupObjectsPrefix = "backups" @@ -283,7 +283,7 @@ func (m *migrationE2E) Backup() error { }) } else { // the snapshots of AWS may be still in pending status when do the restore. - // wait for a while to avoid this https://github.com/vmware-tanzu/velero/issues/1799 + // wait for a while to avoid this https://github.com/velero-io/velero/issues/1799 if OriginVeleroCfg.CloudProvider == test.Azure && strings.EqualFold(OriginVeleroCfg.Features, test.FeatureCSI) || OriginVeleroCfg.CloudProvider == test.AWS { diff --git a/test/e2e/nodeagentconfig/cache_pvc.go b/test/e2e/nodeagentconfig/cache_pvc.go index 9104946c7..2f5029215 100644 --- a/test/e2e/nodeagentconfig/cache_pvc.go +++ b/test/e2e/nodeagentconfig/cache_pvc.go @@ -29,13 +29,13 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) type CachePVCTestCase struct { diff --git a/test/e2e/nodeagentconfig/node-agent-config.go b/test/e2e/nodeagentconfig/node-agent-config.go index 5266bffc5..115594197 100644 --- a/test/e2e/nodeagentconfig/node-agent-config.go +++ b/test/e2e/nodeagentconfig/node-agent-config.go @@ -31,15 +31,15 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/velero-io/velero/pkg/builder" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) type NodeAgentConfigTestCase struct { diff --git a/test/e2e/parallelfilesdownload/parallel_files_download.go b/test/e2e/parallelfilesdownload/parallel_files_download.go index bc4d61323..b67af2324 100644 --- a/test/e2e/parallelfilesdownload/parallel_files_download.go +++ b/test/e2e/parallelfilesdownload/parallel_files_download.go @@ -22,10 +22,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) type ParallelFilesDownload struct { diff --git a/test/e2e/parallelfilesupload/parallel_files_upload.go b/test/e2e/parallelfilesupload/parallel_files_upload.go index b11e3382b..bc9b6e4c0 100644 --- a/test/e2e/parallelfilesupload/parallel_files_upload.go +++ b/test/e2e/parallelfilesupload/parallel_files_upload.go @@ -22,10 +22,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) type ParallelFilesUpload struct { diff --git a/test/e2e/privilegesmgmt/ssr.go b/test/e2e/privilegesmgmt/ssr.go index 9b0e99a0f..e6c7fea7b 100644 --- a/test/e2e/privilegesmgmt/ssr.go +++ b/test/e2e/privilegesmgmt/ssr.go @@ -29,10 +29,10 @@ import ( waitutil "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) func SSRTest() { diff --git a/test/e2e/pv-backup/pv-backup-filter.go b/test/e2e/pv-backup/pv-backup-filter.go index 5a6730551..df3ae2333 100644 --- a/test/e2e/pv-backup/pv-backup-filter.go +++ b/test/e2e/pv-backup/pv-backup-filter.go @@ -10,11 +10,11 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) type PVBackupFiltering struct { diff --git a/test/e2e/repomaintenance/repo_maintenance_config.go b/test/e2e/repomaintenance/repo_maintenance_config.go index c0092c4bf..f874896ec 100644 --- a/test/e2e/repomaintenance/repo_maintenance_config.go +++ b/test/e2e/repomaintenance/repo_maintenance_config.go @@ -29,15 +29,15 @@ import ( "k8s.io/apimachinery/pkg/labels" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - velerotypes "github.com/vmware-tanzu/velero/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/kube" - velerokubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" - "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/velero-io/velero/pkg/util/kube" + velerokubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) type RepoMaintenanceTestCase struct { diff --git a/test/e2e/resource-filtering/base.go b/test/e2e/resource-filtering/base.go index f4070d9e7..021dac7cc 100644 --- a/test/e2e/resource-filtering/base.go +++ b/test/e2e/resource-filtering/base.go @@ -23,9 +23,9 @@ import ( "github.com/pkg/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) type FilteringCase struct { diff --git a/test/e2e/resource-filtering/exclude_label.go b/test/e2e/resource-filtering/exclude_label.go index 695d7d8ed..bd1c297bf 100644 --- a/test/e2e/resource-filtering/exclude_label.go +++ b/test/e2e/resource-filtering/exclude_label.go @@ -24,10 +24,10 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/exclude_namespaces.go b/test/e2e/resource-filtering/exclude_namespaces.go index 1b8e5da55..e4be6302f 100644 --- a/test/e2e/resource-filtering/exclude_namespaces.go +++ b/test/e2e/resource-filtering/exclude_namespaces.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/exclude_resources.go b/test/e2e/resource-filtering/exclude_resources.go index b8a7d2e73..dcee6c7aa 100644 --- a/test/e2e/resource-filtering/exclude_resources.go +++ b/test/e2e/resource-filtering/exclude_resources.go @@ -24,9 +24,9 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/include_namespaces.go b/test/e2e/resource-filtering/include_namespaces.go index d511de212..363e4b9a9 100644 --- a/test/e2e/resource-filtering/include_namespaces.go +++ b/test/e2e/resource-filtering/include_namespaces.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/include_resources.go b/test/e2e/resource-filtering/include_resources.go index 22d7e968b..2b86dc59e 100644 --- a/test/e2e/resource-filtering/include_resources.go +++ b/test/e2e/resource-filtering/include_resources.go @@ -24,8 +24,8 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/label_selector.go b/test/e2e/resource-filtering/label_selector.go index 9ecc66a0c..6f310f863 100644 --- a/test/e2e/resource-filtering/label_selector.go +++ b/test/e2e/resource-filtering/label_selector.go @@ -24,9 +24,9 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/wildcard_namespaces.go b/test/e2e/resource-filtering/wildcard_namespaces.go index c3cd50071..aab0bc3b2 100644 --- a/test/e2e/resource-filtering/wildcard_namespaces.go +++ b/test/e2e/resource-filtering/wildcard_namespaces.go @@ -23,8 +23,8 @@ import ( . "github.com/onsi/gomega" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + . "github.com/velero-io/velero/test/util/k8s" ) // WildcardNamespaces tests the inclusion and exclusion of namespaces using wildcards diff --git a/test/e2e/resourcemodifiers/resource_modifiers.go b/test/e2e/resourcemodifiers/resource_modifiers.go index 06cbd91f1..4e20cd613 100644 --- a/test/e2e/resourcemodifiers/resource_modifiers.go +++ b/test/e2e/resourcemodifiers/resource_modifiers.go @@ -24,9 +24,9 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) var yamlData = ` diff --git a/test/e2e/resourcepolicies/resource_policies.go b/test/e2e/resourcepolicies/resource_policies.go index f3254eb04..da68e44f7 100644 --- a/test/e2e/resourcepolicies/resource_policies.go +++ b/test/e2e/resourcepolicies/resource_policies.go @@ -27,10 +27,10 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/api/resource" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) const FileName = "test-data.txt" diff --git a/test/e2e/scale/multiple_namespaces.go b/test/e2e/scale/multiple_namespaces.go index 6bc4e4f9a..4a55539b3 100644 --- a/test/e2e/scale/multiple_namespaces.go +++ b/test/e2e/scale/multiple_namespaces.go @@ -17,8 +17,8 @@ limitations under the License. package scale import ( - basic "github.com/vmware-tanzu/velero/test/e2e/basic/resources-check" - . "github.com/vmware-tanzu/velero/test/e2e/test" + basic "github.com/velero-io/velero/test/e2e/basic/resources-check" + . "github.com/velero-io/velero/test/e2e/test" ) var MultiNSBackupRestore func() = TestFunc(&basic.MultiNSBackup{IsScaleTest: true}) diff --git a/test/e2e/schedule/in_progress.go b/test/e2e/schedule/in_progress.go index 060740c3f..651905449 100644 --- a/test/e2e/schedule/in_progress.go +++ b/test/e2e/schedule/in_progress.go @@ -11,12 +11,12 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/test" - framework "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/test" + framework "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) var ScheduleInProgressTest func() = framework.TestFunc(&InProgressCase{}) diff --git a/test/e2e/schedule/ordered_resources.go b/test/e2e/schedule/ordered_resources.go index df0d8b972..d0464bd3a 100644 --- a/test/e2e/schedule/ordered_resources.go +++ b/test/e2e/schedule/ordered_resources.go @@ -16,7 +16,7 @@ See the License for the specific language governing permissions and limitations under the License. */ -//the ordered resources test related to https://github.com/vmware-tanzu/velero/issues/4561 +//the ordered resources test related to https://github.com/velero-io/velero/issues/4561 import ( "context" "fmt" @@ -30,11 +30,11 @@ import ( waitutil "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - framework "github.com/vmware-tanzu/velero/test/e2e/test" - "github.com/vmware-tanzu/velero/test/util/common" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + framework "github.com/velero-io/velero/test/e2e/test" + "github.com/velero-io/velero/test/util/common" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) var ScheduleOrderedResources func() = framework.TestFunc(&OrderedResources{}) diff --git a/test/e2e/schedule/periodical.go b/test/e2e/schedule/periodical.go index 330356e99..cb904d00e 100644 --- a/test/e2e/schedule/periodical.go +++ b/test/e2e/schedule/periodical.go @@ -10,10 +10,10 @@ import ( . "github.com/onsi/gomega" "k8s.io/apimachinery/pkg/util/wait" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - framework "github.com/vmware-tanzu/velero/test/e2e/test" - k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" - veleroutil "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + framework "github.com/velero-io/velero/test/e2e/test" + k8sutil "github.com/velero-io/velero/test/util/k8s" + veleroutil "github.com/velero-io/velero/test/util/velero" ) type PeriodicalCase struct { diff --git a/test/e2e/test/test.go b/test/e2e/test/test.go index 1a91c115f..dda3f3870 100644 --- a/test/e2e/test/test.go +++ b/test/e2e/test/test.go @@ -27,10 +27,10 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) /* @@ -146,8 +146,8 @@ func (t *TestCase) Restore() error { veleroCfg := t.GetTestCase().VeleroCfg // the snapshots of AWS may be still in pending status when do the restore, wait for a while - // to avoid this https://github.com/vmware-tanzu/velero/issues/1799 - // TODO remove this after https://github.com/vmware-tanzu/velero/issues/3533 is fixed + // to avoid this https://github.com/velero-io/velero/issues/1799 + // TODO remove this after https://github.com/velero-io/velero/issues/3533 is fixed By("Waiting 5 minutes to make sure the snapshots are ready...", func() { if t.UseVolumeSnapshots && veleroCfg.CloudProvider != Vsphere { time.Sleep(5 * time.Minute) diff --git a/test/e2e/upgrade/upgrade.go b/test/e2e/upgrade/upgrade.go index 6d081f1c1..91ade0cfa 100644 --- a/test/e2e/upgrade/upgrade.go +++ b/test/e2e/upgrade/upgrade.go @@ -26,11 +26,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/kibishii" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) var upgradeNamespace string @@ -236,8 +236,8 @@ func BackupUpgradeRestoreTest(useVolumeSnapshots bool, veleroCLI2Version VeleroC }) } // the snapshots of AWS may be still in pending status when do the restore, wait for a while - // to avoid this https://github.com/vmware-tanzu/velero/issues/1799 - // TODO remove this after https://github.com/vmware-tanzu/velero/issues/3533 is fixed + // to avoid this https://github.com/velero-io/velero/issues/1799 + // TODO remove this after https://github.com/velero-io/velero/issues/3533 is fixed if tmpCfg.CloudProvider == AWS && useVolumeSnapshots { fmt.Println("Waiting 5 minutes to make sure the snapshots are ready...") time.Sleep(5 * time.Minute) diff --git a/test/perf/README.md b/test/perf/README.md index a3dd295ba..79e99d95d 100644 --- a/test/perf/README.md +++ b/test/perf/README.md @@ -2,4 +2,4 @@ Document for running Velero end-to-end performance test suite. -And the data generate tool for performance test could be found in [here](https://github.com/vmware-tanzu/velero-performance-test) \ No newline at end of file +And the data generate tool for performance test could be found in [here](https://github.com/velero-io/velero-performance-test) \ No newline at end of file diff --git a/test/perf/backup/backup.go b/test/perf/backup/backup.go index c8c39a6e1..91c5ff9b0 100644 --- a/test/perf/backup/backup.go +++ b/test/perf/backup/backup.go @@ -21,8 +21,8 @@ import ( "strings" "time" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/perf/test" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/perf/test" ) type BackupTest struct { diff --git a/test/perf/basic/basic.go b/test/perf/basic/basic.go index 76bf605a6..5ebbf70c1 100644 --- a/test/perf/basic/basic.go +++ b/test/perf/basic/basic.go @@ -23,9 +23,9 @@ import ( "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/perf/test" - "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/perf/test" + "github.com/velero-io/velero/test/util/k8s" ) type BasicTest struct { diff --git a/test/perf/e2e_suite_test.go b/test/perf/e2e_suite_test.go index 48a5ceec9..a54215dc5 100644 --- a/test/perf/e2e_suite_test.go +++ b/test/perf/e2e_suite_test.go @@ -27,15 +27,15 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - . "github.com/vmware-tanzu/velero/test" - "github.com/vmware-tanzu/velero/test/perf/backup" - "github.com/vmware-tanzu/velero/test/perf/basic" - "github.com/vmware-tanzu/velero/test/perf/restore" - "github.com/vmware-tanzu/velero/test/perf/test" - . "github.com/vmware-tanzu/velero/test/util/k8s" - "github.com/vmware-tanzu/velero/test/util/report" - . "github.com/vmware-tanzu/velero/test/util/velero" + "github.com/velero-io/velero/pkg/cmd/cli/install" + . "github.com/velero-io/velero/test" + "github.com/velero-io/velero/test/perf/backup" + "github.com/velero-io/velero/test/perf/basic" + "github.com/velero-io/velero/test/perf/restore" + "github.com/velero-io/velero/test/perf/test" + . "github.com/velero-io/velero/test/util/k8s" + "github.com/velero-io/velero/test/util/report" + . "github.com/velero-io/velero/test/util/velero" ) func init() { diff --git a/test/perf/metrics/minio.go b/test/perf/metrics/minio.go index 8ea7ae4c3..ecb20a3d3 100644 --- a/test/perf/metrics/minio.go +++ b/test/perf/metrics/minio.go @@ -19,7 +19,7 @@ package metrics import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/test/util/metrics" + "github.com/velero-io/velero/test/util/metrics" ) const MinioDesc = "Minio disk usage" diff --git a/test/perf/metrics/nfs.go b/test/perf/metrics/nfs.go index 043a4f976..6b0946342 100644 --- a/test/perf/metrics/nfs.go +++ b/test/perf/metrics/nfs.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/test/util/metrics" + "github.com/velero-io/velero/test/util/metrics" ) const NFSDesc = "NFS disk usage" diff --git a/test/perf/metrics/pod.go b/test/perf/metrics/pod.go index 56572f672..cedb89cdc 100644 --- a/test/perf/metrics/pod.go +++ b/test/perf/metrics/pod.go @@ -26,7 +26,7 @@ import ( metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" - "github.com/vmware-tanzu/velero/test/util/metrics" + "github.com/velero-io/velero/test/util/metrics" ) const PodResourceDesc = "Resource consumption" diff --git a/test/perf/restore/restore.go b/test/perf/restore/restore.go index 6adbff5f4..2aedc4d48 100644 --- a/test/perf/restore/restore.go +++ b/test/perf/restore/restore.go @@ -22,10 +22,10 @@ import ( "github.com/pkg/errors" - . "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test/perf/test" - "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test/perf/test" + "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/velero" ) type RestoreTest struct { diff --git a/test/perf/test/test.go b/test/perf/test/test.go index 1bc8a3fc0..f40165cd9 100644 --- a/test/perf/test/test.go +++ b/test/perf/test/test.go @@ -26,13 +26,13 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - . "github.com/vmware-tanzu/velero/test" - "github.com/vmware-tanzu/velero/test/perf/metrics" - . "github.com/vmware-tanzu/velero/test/util/k8s" - "github.com/vmware-tanzu/velero/test/util/report" - "github.com/vmware-tanzu/velero/test/util/velero" - . "github.com/vmware-tanzu/velero/test/util/velero" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + . "github.com/velero-io/velero/test" + "github.com/velero-io/velero/test/perf/metrics" + . "github.com/velero-io/velero/test/util/k8s" + "github.com/velero-io/velero/test/util/report" + "github.com/velero-io/velero/test/util/velero" + . "github.com/velero-io/velero/test/util/velero" ) /* diff --git a/test/pkg/client/client.go b/test/pkg/client/client.go index 331b786f2..9ac1f1d55 100644 --- a/test/pkg/client/client.go +++ b/test/pkg/client/client.go @@ -24,7 +24,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/clientcmd" - "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/velero-io/velero/pkg/buildinfo" ) func buildConfigFromFlags(context, kubeconfigPath string, precedence []string) (*rest.Config, error) { diff --git a/test/pkg/client/factory.go b/test/pkg/client/factory.go index 340cba587..c5d089ea5 100644 --- a/test/pkg/client/factory.go +++ b/test/pkg/client/factory.go @@ -32,8 +32,8 @@ import ( "k8s.io/client-go/rest" metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" ) // Factory knows how to create a VeleroClient and Kubernetes client. diff --git a/test/types.go b/test/types.go index ef9582ce3..f2aa135c3 100644 --- a/test/types.go +++ b/test/types.go @@ -21,8 +21,8 @@ import ( "github.com/google/uuid" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/velero-io/velero/pkg/cmd/cli/install" + "github.com/velero-io/velero/test/util/k8s" ) // e2e-storage-class is the default StorageClass for E2E. diff --git a/test/util/csi/common.go b/test/util/csi/common.go index 373bc1502..0d36cb530 100644 --- a/test/util/csi/common.go +++ b/test/util/csi/common.go @@ -28,7 +28,7 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/tools/clientcmd" - . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/k8s" ) func GetClients() (*kubernetes.Clientset, *snapshotterClientSet.Clientset, error) { diff --git a/test/util/eks/eks.go b/test/util/eks/eks.go index f2e491c1f..56a1d0736 100644 --- a/test/util/eks/eks.go +++ b/test/util/eks/eks.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/util/wait" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func KubectlDeleteIAMServiceAcount(ctx context.Context, name, namespace, cluster string) error { diff --git a/test/util/k8s/client.go b/test/util/k8s/client.go index 1018e3bdf..5c1779f61 100644 --- a/test/util/k8s/client.go +++ b/test/util/k8s/client.go @@ -21,7 +21,7 @@ import ( metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/test/pkg/client" + "github.com/velero-io/velero/test/pkg/client" ) // TestClient contains different API clients that are in use throughout diff --git a/test/util/k8s/clusterrolebinding.go b/test/util/k8s/clusterrolebinding.go index e682c0bdc..95b804304 100644 --- a/test/util/k8s/clusterrolebinding.go +++ b/test/util/k8s/clusterrolebinding.go @@ -23,7 +23,7 @@ import ( "context" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func KubectlDeleteClusterRoleBinding(ctx context.Context, name string) error { diff --git a/test/util/k8s/common.go b/test/util/k8s/common.go index 8869caab3..368da15b6 100644 --- a/test/util/k8s/common.go +++ b/test/util/k8s/common.go @@ -30,9 +30,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/util/wait" - "github.com/vmware-tanzu/velero/pkg/builder" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" - common "github.com/vmware-tanzu/velero/test/util/common" + "github.com/velero-io/velero/pkg/builder" + veleroexec "github.com/velero-io/velero/pkg/util/exec" + common "github.com/velero-io/velero/test/util/common" ) // ensureClusterExists returns whether or not a Kubernetes cluster exists for tests to be run on. diff --git a/test/util/k8s/crd.go b/test/util/k8s/crd.go index fe17fb0ae..5d1379b64 100644 --- a/test/util/k8s/crd.go +++ b/test/util/k8s/crd.go @@ -26,7 +26,7 @@ import ( "github.com/pkg/errors" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func InstallCRD(ctx context.Context, yaml string) error { diff --git a/test/util/k8s/deployment.go b/test/util/k8s/deployment.go index 42e2d6ac7..c172604ff 100644 --- a/test/util/k8s/deployment.go +++ b/test/util/k8s/deployment.go @@ -29,8 +29,8 @@ import ( "k8s.io/apimachinery/pkg/util/wait" clientset "k8s.io/client-go/kubernetes" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - common "github.com/vmware-tanzu/velero/test/util/common" + "github.com/velero-io/velero/pkg/util/boolptr" + common "github.com/velero-io/velero/test/util/common" ) const ( diff --git a/test/util/k8s/namespace.go b/test/util/k8s/namespace.go index b46075fee..59454c1a7 100644 --- a/test/util/k8s/namespace.go +++ b/test/util/k8s/namespace.go @@ -31,8 +31,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" waitutil "k8s.io/apimachinery/pkg/util/wait" - "github.com/vmware-tanzu/velero/pkg/builder" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/velero-io/velero/pkg/builder" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func CreateNamespace(ctx context.Context, client TestClient, namespace string) error { diff --git a/test/util/k8s/node.go b/test/util/k8s/node.go index 5fd1dafc6..949c75aaf 100644 --- a/test/util/k8s/node.go +++ b/test/util/k8s/node.go @@ -8,7 +8,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - common "github.com/vmware-tanzu/velero/test/util/common" + common "github.com/velero-io/velero/test/util/common" ) func GetWorkerNodes(ctx context.Context, workerOS string) ([]string, error) { diff --git a/test/util/k8s/pod.go b/test/util/k8s/pod.go index 9906e08b5..7b8e04a83 100644 --- a/test/util/k8s/pod.go +++ b/test/util/k8s/pod.go @@ -27,8 +27,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/vmware-tanzu/velero/pkg/util/boolptr" - common "github.com/vmware-tanzu/velero/test/util/common" + "github.com/velero-io/velero/pkg/util/boolptr" + common "github.com/velero-io/velero/test/util/common" ) func CreatePod( diff --git a/test/util/k8s/serviceaccount.go b/test/util/k8s/serviceaccount.go index 31773d846..7f6b0fa8e 100644 --- a/test/util/k8s/serviceaccount.go +++ b/test/util/k8s/serviceaccount.go @@ -29,7 +29,7 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/apimachinery/pkg/util/wait" - "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/velero-io/velero/pkg/builder" ) func WaitUntilServiceAccountCreated(ctx context.Context, client TestClient, namespace, serviceAccount string, timeout time.Duration) error { diff --git a/test/util/k8s/statefulset.go b/test/util/k8s/statefulset.go index f0ac3a651..6699a731b 100644 --- a/test/util/k8s/statefulset.go +++ b/test/util/k8s/statefulset.go @@ -24,7 +24,7 @@ import ( "github.com/pkg/errors" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + veleroexec "github.com/velero-io/velero/pkg/util/exec" ) func ScaleStatefulSet(ctx context.Context, namespace, name string, replicas int) error { diff --git a/test/util/kibishii/kibishii_utils.go b/test/util/kibishii/kibishii_utils.go index 5948a2c7b..175938438 100644 --- a/test/util/kibishii/kibishii_utils.go +++ b/test/util/kibishii/kibishii_utils.go @@ -35,12 +35,12 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/yaml" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" - . "github.com/vmware-tanzu/velero/test" - "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" - . "github.com/vmware-tanzu/velero/test/util/providers" - . "github.com/vmware-tanzu/velero/test/util/velero" + veleroexec "github.com/velero-io/velero/pkg/util/exec" + . "github.com/velero-io/velero/test" + "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" + . "github.com/velero-io/velero/test/util/providers" + . "github.com/velero-io/velero/test/util/velero" ) const ( diff --git a/test/util/metrics/minio.go b/test/util/metrics/minio.go index 163212713..1f0dc44cd 100644 --- a/test/util/metrics/minio.go +++ b/test/util/metrics/minio.go @@ -19,7 +19,7 @@ package metrics import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/test/util/providers" + "github.com/velero-io/velero/test/util/providers" ) func GetMinioDiskUsage(cloudCredentialsFile string, bslBucket string, bslPrefix string, bslConfig string) (int64, error) { diff --git a/test/util/providers/aws_utils.go b/test/util/providers/aws_utils.go index 7b8916cef..7750749f8 100644 --- a/test/util/providers/aws_utils.go +++ b/test/util/providers/aws_utils.go @@ -38,8 +38,8 @@ import ( s3types "github.com/aws/aws-sdk-go-v2/service/s3/types" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - "github.com/vmware-tanzu/velero/test" + "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/velero-io/velero/test" ) type AWSStorage string diff --git a/test/util/providers/azure_utils.go b/test/util/providers/azure_utils.go index 468dbfe40..79375ec8e 100644 --- a/test/util/providers/azure_utils.go +++ b/test/util/providers/azure_utils.go @@ -39,8 +39,8 @@ import ( "github.com/joho/godotenv" "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - . "github.com/vmware-tanzu/velero/test" + "github.com/velero-io/velero/pkg/cmd/util/flag" + . "github.com/velero-io/velero/test" ) type AzureStorage string diff --git a/test/util/providers/common.go b/test/util/providers/common.go index a7c68dc37..2e915c460 100644 --- a/test/util/providers/common.go +++ b/test/util/providers/common.go @@ -27,9 +27,9 @@ import ( "github.com/pkg/errors" - "github.com/vmware-tanzu/velero/internal/volume" - velerotest "github.com/vmware-tanzu/velero/test" - velero "github.com/vmware-tanzu/velero/test/util/velero" + "github.com/velero-io/velero/internal/volume" + velerotest "github.com/velero-io/velero/test" + velero "github.com/velero-io/velero/test/util/velero" ) type ObjectsInStorage interface { diff --git a/test/util/providers/gcloud_utils.go b/test/util/providers/gcloud_utils.go index 022d92ff2..571a6f3d9 100644 --- a/test/util/providers/gcloud_utils.go +++ b/test/util/providers/gcloud_utils.go @@ -32,7 +32,7 @@ import ( "google.golang.org/api/iterator" "google.golang.org/api/option" - "github.com/vmware-tanzu/velero/test" + "github.com/velero-io/velero/test" ) type GCSStorage string diff --git a/test/util/report/report.go b/test/util/report/report.go index 6d5955392..04bc6a209 100644 --- a/test/util/report/report.go +++ b/test/util/report/report.go @@ -22,7 +22,7 @@ import ( "github.com/pkg/errors" "gopkg.in/yaml.v3" - "github.com/vmware-tanzu/velero/test" + "github.com/velero-io/velero/test" ) func GenerateYamlReport() error { diff --git a/test/util/velero/install.go b/test/util/velero/install.go index e2c57392e..02eacf28c 100644 --- a/test/util/velero/install.go +++ b/test/util/velero/install.go @@ -39,13 +39,13 @@ import ( clientset "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - velerexec "github.com/vmware-tanzu/velero/pkg/util/exec" - "github.com/vmware-tanzu/velero/test" - common "github.com/vmware-tanzu/velero/test/util/common" - eksutil "github.com/vmware-tanzu/velero/test/util/eks" - "github.com/vmware-tanzu/velero/test/util/k8s" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/cmd/cli/install" + velerexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/velero-io/velero/test" + common "github.com/velero-io/velero/test/util/common" + eksutil "github.com/velero-io/velero/test/util/eks" + "github.com/velero-io/velero/test/util/k8s" ) // we provide more install options other than the standard install.InstallOptions in E2E test @@ -222,7 +222,7 @@ func VeleroInstall(ctx context.Context, veleroCfg *test.VeleroConfig, isStandbyC } // generateVSpherePlugin refers to -// https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md +// https://github.com/velero-io/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md func generateVSpherePlugin(veleroCfg *test.VeleroConfig) error { cli := veleroCfg.ClientToInstallVelero @@ -927,7 +927,7 @@ func VeleroUninstall(ctx context.Context, veleroCfg test.VeleroConfig) error { } // createVCCredentialSecret refer to -// https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md +// https://github.com/velero-io/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md func createVCCredentialSecret(c clientset.Interface, veleroNamespace string) error { secret, err := getVCCredentialSecret(c) if err != nil { @@ -970,7 +970,7 @@ func createVCCredentialSecret(c clientset.Interface, veleroNamespace string) err return nil } -// Reference https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/main/docs/vanilla.md#create-vc-credential-secret +// Reference https://github.com/velero-io/velero-plugin-for-vsphere/blob/main/docs/vanilla.md#create-vc-credential-secret // Read secret from kube-system namespace first, if not found, try with vmware-system-csi. func getVCCredentialSecret(c clientset.Interface) (secret *corev1api.Secret, err error) { secret, err = k8s.GetSecret(c, test.KubeSystemNamespace, "vsphere-config-secret") diff --git a/test/util/velero/velero_utils.go b/test/util/velero/velero_utils.go index 5c9b39a84..dc1ddc4a8 100644 --- a/test/util/velero/velero_utils.go +++ b/test/util/velero/velero_utils.go @@ -45,16 +45,16 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/vmware-tanzu/velero/internal/volume" - velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - "github.com/vmware-tanzu/velero/pkg/builder" - cliinstall "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" - "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" - veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" - "github.com/vmware-tanzu/velero/test" - . "github.com/vmware-tanzu/velero/test" - common "github.com/vmware-tanzu/velero/test/util/common" - . "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/velero-io/velero/internal/volume" + velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/velero-io/velero/pkg/builder" + cliinstall "github.com/velero-io/velero/pkg/cmd/cli/install" + "github.com/velero-io/velero/pkg/cmd/util/flag" + veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/velero-io/velero/test" + . "github.com/velero-io/velero/test" + common "github.com/velero-io/velero/test/util/common" + . "github.com/velero-io/velero/test/util/k8s" ) const BackupObjectsPrefix = "backups" @@ -477,7 +477,7 @@ func VeleroBackupNamespace(ctx context.Context, veleroCLI, veleroNamespace strin args = append(args, "--default-volumes-to-fs-backup") } - // To workaround https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/347 for vsphere plugin v1.1.1 + // To workaround https://github.com/velero-io/velero-plugin-for-vsphere/issues/347 for vsphere plugin v1.1.1 // if the "--snapshot-volumes=false" isn't specified explicitly, the vSphere plugin will always take snapshots // for the volumes even though the "--default-volumes-to-fs-backup" is specified // TODO This can be removed if the logic of vSphere plugin bump up to 1.3 @@ -946,7 +946,7 @@ func InstallVeleroCLI(ctx context.Context, version string) (string, error) { postfix := ".tar.gz" tarball := name + postfix err := wait.PollUntilContextTimeout(ctx, time.Second*5, time.Minute*5, true, func(ctx context.Context) (bool, error) { - tempFile, err := getVeleroCliTarball("https://github.com/vmware-tanzu/velero/releases/download/" + version + "/" + tarball) + tempFile, err := getVeleroCliTarball("https://github.com/velero-io/velero/releases/download/" + version + "/" + tarball) if err != nil { return false, errors.WithMessagef(err, "failed to get Velero CLI tarball") } From f5fe41dabf013f943add31ee24ee715ca5d13136 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 22 May 2026 07:46:23 +0000 Subject: [PATCH 3/6] chore: add unreleased changelog for PR 9844 Agent-Logs-Url: https://github.com/velero-io/velero/sessions/9c249471-23d8-4621-aa48-7d9b81c6ed44 Co-authored-by: kaovilai <11228024+kaovilai@users.noreply.github.com> --- changelogs/unreleased/9844-Copilot | 1 + 1 file changed, 1 insertion(+) create mode 100644 changelogs/unreleased/9844-Copilot 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) From fb603765e20b218974df391f5472a4d1bec7a5b6 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 22 May 2026 15:22:21 +0000 Subject: [PATCH 4/6] fix: update datapath messages to new naming Agent-Logs-Url: https://github.com/velero-io/velero/sessions/4e226ac0-3c47-4894-9b70-d0e0b9b7c374 Co-authored-by: kaovilai <11228024+kaovilai@users.noreply.github.com> --- pkg/datapath/data_path.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkg/datapath/data_path.go b/pkg/datapath/data_path.go index 33217ee09..fc6336cd7 100644 --- a/pkg/datapath/data_path.go +++ b/pkg/datapath/data_path.go @@ -167,7 +167,7 @@ func (dp *generalDataPath) close(ctx context.Context) { func (dp *generalDataPath) StartBackup(source AccessPoint, uploaderConfig map[string]string, param any) error { if !dp.initialized { - return errors.New("file system data path is not initialized") + return errors.New("data path is not initialized") } dp.wgDataPath.Add(1) @@ -243,7 +243,7 @@ func (dp *generalDataPath) UpdateProgress(p *uploader.Progress) { func (dp *generalDataPath) Cancel() { dp.cancel() - dp.log.WithField("user", dp.jobName).Info("FileSystemBR is canceled") + dp.log.WithField("user", dp.jobName).Info("Data path is canceled") } func (dp *generalDataPath) boostRepoConnect(ctx context.Context, repositoryType string, credentialGetter *credentials.CredentialGetter, cacheDir string) error { From a34a676fa323bc8daf31280b699bb0edb43ba859 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 25 May 2026 05:35:00 +0000 Subject: [PATCH 5/6] chore: narrow PR scope to site docs updates Agent-Logs-Url: https://github.com/velero-io/velero/sessions/3fa04f71-b7a9-47d5-b881-fb3cd9226d98 Co-authored-by: blackpiglet <59276555+blackpiglet@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/config.yml | 2 +- .../feature-enhancement-request.md | 2 +- .gitignore | 2 +- .golangci.yaml | 2 +- .goreleaser.yml | 2 +- ADOPTERS.md | 4 +- CHANGELOG.md | 52 +++++++-------- Dockerfile | 4 +- Dockerfile-Windows | 4 +- GOVERNANCE.md | 22 +++---- MAINTAINERS.md | 2 +- Makefile | 10 +-- ROADMAP.md | 2 +- SECURITY.md | 6 +- changelogs/CHANGELOG-0.10.md | 4 +- changelogs/CHANGELOG-0.9.md | 2 +- changelogs/CHANGELOG-1.10.md | 12 ++-- changelogs/CHANGELOG-1.11.md | 6 +- changelogs/CHANGELOG-1.12.md | 8 +-- changelogs/CHANGELOG-1.13.md | 8 +-- changelogs/CHANGELOG-1.14.md | 2 +- changelogs/CHANGELOG-1.15.md | 16 ++--- changelogs/CHANGELOG-1.16.md | 34 +++++----- changelogs/CHANGELOG-1.17.md | 16 ++--- changelogs/CHANGELOG-1.18.md | 8 +-- changelogs/CHANGELOG-1.2.md | 2 +- changelogs/CHANGELOG-1.3.md | 14 ++-- changelogs/CHANGELOG-1.4.md | 4 +- changelogs/CHANGELOG-1.5.md | 4 +- changelogs/CHANGELOG-1.6.md | 2 +- changelogs/CHANGELOG-1.7.md | 4 +- changelogs/CHANGELOG-1.8.md | 4 +- changelogs/CHANGELOG-1.9.md | 4 +- cmd/velero/velero.go | 4 +- ...-bsl-delete-associated-resources_design.md | 4 +- ...-VolumePolicies-to-support-more-actions.md | 20 +++--- .../clean_artifacts_in_csi_flow.md | 2 +- .../cluster-scope-resource-filter.md | 4 +- design/Implemented/custom-ca-support.md | 10 +-- .../existing-resource-policy_design.md | 10 +-- .../general-progress-monitoring.md | 12 ++-- .../include-exclude-in-resource-policy.md | 2 +- .../json-substitution-action-design.md | 2 +- ...atch-and-strategic-in-resource-modifier.md | 4 +- design/Implemented/move-gh-org.md | 4 +- ...ultiple-csi-volumesnapshotclass-support.md | 2 +- .../multiple-label-selectors_design.md | 6 +- ...ugin-backup-and-restore-progress-design.md | 6 +- design/Implemented/plugin-versioning.md | 14 ++-- design/Implemented/pv-cloning.md | 4 +- design/Implemented/pv_backup_info.md | 8 +-- design/Implemented/pv_restore_info.md | 4 +- .../repo_maintenance_job_config.md | 6 +- design/Implemented/resource-status-restore.md | 2 +- .../restore-finalizing-phase_design.md | 2 +- ...ore-with-EnableAPIGroupVersions-feature.md | 10 +-- .../retry-patching-configuration_design.md | 8 +-- ...schedule-skip-immediately-config_design.md | 2 +- design/Implemented/secrets.md | 16 ++--- ...orting-volumeattributes-resource-policy.md | 4 +- design/Implemented/velero-debug.md | 2 +- .../Implemented/vgdp-affinity-enhancement.md | 2 +- .../vgdp-micro-service-for-fs-backup.md | 10 +-- design/Implemented/volume-group-snapshot.md | 4 +- .../volume-snapshot-data-movement.md | 2 +- .../Implemented/wait-for-additional-items.md | 6 +- .../wildcard-namespace-support-design.md | 2 +- design/cli-install-changes.md | 6 +- .../new-prepost-backuprestore-plugin-hooks.md | 18 +++--- design/restore-progress.md | 2 +- go.mod | 2 +- hack/issue-template-gen/main.go | 2 +- hack/release-tools/brew-update.sh | 2 +- hack/release-tools/gen-docs.sh | 4 +- hack/update-1fmt.sh | 2 +- hack/update-2proto.sh | 2 +- internal/credentials/file_store.go | 4 +- internal/credentials/file_store_test.go | 4 +- internal/credentials/secret_store.go | 2 +- .../csi/volumesnapshotcontent_action.go | 8 +-- .../csi/volumesnapshotcontent_action_test.go | 10 +-- internal/delete/delete_item_action_handler.go | 12 ++-- .../delete/delete_item_action_handler_test.go | 12 ++-- internal/hook/item_hook_handler.go | 16 ++--- internal/hook/item_hook_handler_test.go | 12 ++-- internal/hook/wait_exec_hook_handler.go | 8 +-- internal/hook/wait_exec_hook_handler_test.go | 8 +-- .../resourcemodifiers/resource_modifiers.go | 2 +- .../resourcepolicies/resource_policies.go | 2 +- .../restartabletest/restartable_delegate.go | 4 +- internal/storage/storagelocation.go | 2 +- internal/storage/storagelocation_test.go | 8 +-- internal/velero/images.go | 2 +- internal/velero/images_test.go | 2 +- internal/velero/serverstatusrequest.go | 6 +- internal/volume/snapshotlocation.go | 4 +- internal/volume/utils.go | 2 +- internal/volume/volumes_information.go | 12 ++-- internal/volume/volumes_information_test.go | 16 ++--- internal/volumehelper/volume_policy_helper.go | 14 ++-- .../volumehelper/volume_policy_helper_test.go | 12 ++-- pkg/apis/velero/v1/pod_volume_backup_types.go | 2 +- pkg/apis/velero/v1/pod_volume_restore_type.go | 2 +- .../velero/v2alpha1/data_download_types.go | 2 +- pkg/apis/velero/v2alpha1/data_upload_types.go | 2 +- pkg/archive/extractor.go | 2 +- pkg/archive/extractor_test.go | 4 +- pkg/archive/filesystem.go | 4 +- pkg/archive/filesystem_test.go | 4 +- pkg/archive/parser.go | 4 +- pkg/archive/parser_test.go | 2 +- pkg/backup/actions/backup_pv_action.go | 6 +- pkg/backup/actions/backup_pv_action_test.go | 10 +-- pkg/backup/actions/csi/pvc_action.go | 30 ++++----- pkg/backup/actions/csi/pvc_action_test.go | 18 +++--- .../actions/csi/volumesnapshot_action.go | 20 +++--- .../actions/csi/volumesnapshot_action_test.go | 12 ++-- .../actions/csi/volumesnapshotclass_action.go | 10 +-- .../csi/volumesnapshotclass_action_test.go | 8 +-- .../csi/volumesnapshotcontent_action.go | 10 +-- .../csi/volumesnapshotcontent_action_test.go | 10 +-- pkg/backup/actions/pod_action.go | 6 +- pkg/backup/actions/pod_action_test.go | 6 +- .../actions/remap_crd_version_action.go | 6 +- .../actions/remap_crd_version_action_test.go | 8 +-- pkg/backup/actions/service_account_action.go | 8 +-- .../actions/service_account_action_test.go | 8 +-- pkg/backup/backup.go | 46 ++++++------- pkg/backup/backup_test.go | 42 ++++++------ pkg/backup/delete_helpers.go | 4 +- pkg/backup/item_backupper.go | 34 +++++----- pkg/backup/item_backupper_test.go | 6 +- pkg/backup/item_collector.go | 12 ++-- pkg/backup/item_collector_test.go | 10 +-- pkg/backup/itemblock.go | 2 +- pkg/backup/request.go | 14 ++-- pkg/backup/snapshots.go | 8 +-- pkg/backup/volume_snapshotter_cache.go | 4 +- pkg/builder/backup_builder.go | 8 +-- .../backup_storage_location_builder.go | 2 +- pkg/builder/container_builder.go | 2 +- pkg/builder/container_builder_test.go | 4 +- pkg/builder/data_download_builder.go | 4 +- pkg/builder/data_upload_builder.go | 4 +- pkg/builder/delete_backup_request_builder.go | 2 +- pkg/builder/download_request_builder.go | 2 +- pkg/builder/item_operation_builder.go | 4 +- pkg/builder/pod_volume_backup_builder.go | 2 +- pkg/builder/pod_volume_restore_builder.go | 2 +- pkg/builder/restore_builder.go | 2 +- pkg/builder/schedule_builder.go | 2 +- pkg/builder/server_status_request_builder.go | 2 +- pkg/builder/testcr_builder.go | 2 +- .../volume_snapshot_location_builder.go | 2 +- pkg/cbtservice/mocks/Service.go | 2 +- pkg/client/client.go | 2 +- pkg/client/factory.go | 4 +- pkg/cmd/cli/backup/backup.go | 2 +- pkg/cmd/cli/backup/backup_test.go | 2 +- pkg/cmd/cli/backup/create.go | 16 ++--- pkg/cmd/cli/backup/create_test.go | 12 ++-- pkg/cmd/cli/backup/delete.go | 14 ++-- pkg/cmd/cli/backup/delete_test.go | 12 ++-- pkg/cmd/cli/backup/describe.go | 10 +-- pkg/cmd/cli/backup/describe_test.go | 12 ++-- pkg/cmd/cli/backup/download.go | 10 +-- pkg/cmd/cli/backup/download_test.go | 10 +-- pkg/cmd/cli/backup/get.go | 8 +-- pkg/cmd/cli/backup/get_test.go | 10 +-- pkg/cmd/cli/backup/logs.go | 10 +-- pkg/cmd/cli/backup/logs_test.go | 12 ++-- pkg/cmd/cli/backuplocation/backup_location.go | 2 +- .../backuplocation/backup_location_test.go | 2 +- pkg/cmd/cli/backuplocation/create.go | 14 ++-- pkg/cmd/cli/backuplocation/create_test.go | 6 +- pkg/cmd/cli/backuplocation/delete.go | 10 +-- pkg/cmd/cli/backuplocation/delete_test.go | 12 ++-- pkg/cmd/cli/backuplocation/get.go | 8 +-- pkg/cmd/cli/backuplocation/get_test.go | 8 +-- pkg/cmd/cli/backuplocation/set.go | 14 ++-- pkg/cmd/cli/backuplocation/set_test.go | 12 ++-- pkg/cmd/cli/bug/bug.go | 10 +-- pkg/cmd/cli/client/client.go | 2 +- pkg/cmd/cli/client/config/get.go | 4 +- pkg/cmd/cli/client/config/set.go | 4 +- pkg/cmd/cli/create/create.go | 12 ++-- pkg/cmd/cli/datamover/backup.go | 26 ++++---- pkg/cmd/cli/datamover/backup_test.go | 8 +-- pkg/cmd/cli/datamover/data_mover.go | 2 +- pkg/cmd/cli/datamover/restore.go | 26 ++++---- pkg/cmd/cli/datamover/restore_test.go | 4 +- pkg/cmd/cli/debug/debug.go | 6 +- pkg/cmd/cli/delete/delete.go | 10 +-- pkg/cmd/cli/delete_options.go | 4 +- pkg/cmd/cli/describe/describe.go | 8 +-- pkg/cmd/cli/get/get.go | 14 ++-- pkg/cmd/cli/install/install.go | 20 +++--- pkg/cmd/cli/install/install_test.go | 4 +- pkg/cmd/cli/nodeagent/node_agent.go | 2 +- pkg/cmd/cli/nodeagent/server.go | 34 +++++----- pkg/cmd/cli/nodeagent/server_test.go | 10 +-- pkg/cmd/cli/plugin/add.go | 10 +-- pkg/cmd/cli/plugin/get.go | 8 +-- pkg/cmd/cli/plugin/helpers.go | 4 +- pkg/cmd/cli/plugin/plugin.go | 2 +- pkg/cmd/cli/plugin/remove.go | 4 +- pkg/cmd/cli/podvolume/backup.go | 24 +++---- pkg/cmd/cli/podvolume/backup_test.go | 8 +-- pkg/cmd/cli/podvolume/podvolume.go | 2 +- pkg/cmd/cli/podvolume/restore.go | 24 +++---- pkg/cmd/cli/podvolume/restore_test.go | 4 +- pkg/cmd/cli/repo/get.go | 8 +-- pkg/cmd/cli/repo/repo.go | 2 +- pkg/cmd/cli/repomantenance/maintenance.go | 18 +++--- pkg/cmd/cli/restore/create.go | 18 +++--- pkg/cmd/cli/restore/create_test.go | 10 +-- pkg/cmd/cli/restore/delete.go | 10 +-- pkg/cmd/cli/restore/delete_test.go | 12 ++-- pkg/cmd/cli/restore/describe.go | 10 +-- pkg/cmd/cli/restore/describe_test.go | 12 ++-- pkg/cmd/cli/restore/get.go | 8 +-- pkg/cmd/cli/restore/get_test.go | 10 +-- pkg/cmd/cli/restore/logs.go | 10 +-- pkg/cmd/cli/restore/logs_test.go | 12 ++-- pkg/cmd/cli/restore/restore.go | 2 +- pkg/cmd/cli/restore/restore_test.go | 2 +- pkg/cmd/cli/schedule/create.go | 12 ++-- pkg/cmd/cli/schedule/delete.go | 10 +-- pkg/cmd/cli/schedule/describe.go | 8 +-- pkg/cmd/cli/schedule/get.go | 8 +-- pkg/cmd/cli/schedule/pause.go | 8 +-- pkg/cmd/cli/schedule/schedule.go | 2 +- pkg/cmd/cli/schedule/skip_options.go | 2 +- pkg/cmd/cli/schedule/unpause.go | 6 +- pkg/cmd/cli/select_option.go | 2 +- pkg/cmd/cli/select_option_test.go | 2 +- pkg/cmd/cli/serverstatus/server_status.go | 6 +- pkg/cmd/cli/snapshotlocation/create.go | 12 ++-- pkg/cmd/cli/snapshotlocation/get.go | 8 +-- pkg/cmd/cli/snapshotlocation/set.go | 12 ++-- .../cli/snapshotlocation/snapshot_location.go | 2 +- pkg/cmd/cli/uninstall/uninstall.go | 18 +++--- pkg/cmd/cli/version/version.go | 8 +-- pkg/cmd/cli/version/version_test.go | 8 +-- pkg/cmd/server/config/config.go | 16 ++--- pkg/cmd/server/plugin/plugin.go | 30 ++++----- pkg/cmd/server/server.go | 64 +++++++++---------- pkg/cmd/server/server_test.go | 18 +++--- pkg/cmd/util/cacert/bsl_cacert.go | 2 +- pkg/cmd/util/cacert/bsl_cacert_test.go | 6 +- .../util/downloadrequest/downloadrequest.go | 4 +- .../downloadrequest/downloadrequest_test.go | 8 +-- pkg/cmd/util/output/backup_describer.go | 16 ++--- pkg/cmd/util/output/backup_describer_test.go | 10 +-- pkg/cmd/util/output/backup_printer.go | 2 +- pkg/cmd/util/output/backup_printer_test.go | 2 +- pkg/cmd/util/output/backup_repo_printer.go | 2 +- .../output/backup_storage_location_printer.go | 4 +- .../output/backup_structured_describer.go | 10 +-- .../backup_structured_describer_test.go | 8 +-- pkg/cmd/util/output/output.go | 6 +- pkg/cmd/util/output/output_test.go | 2 +- pkg/cmd/util/output/plugin_printer.go | 2 +- pkg/cmd/util/output/restore_describer.go | 14 ++-- pkg/cmd/util/output/restore_describer_test.go | 12 ++-- pkg/cmd/util/output/restore_printer.go | 2 +- pkg/cmd/util/output/schedule_describe_test.go | 4 +- pkg/cmd/util/output/schedule_describer.go | 2 +- pkg/cmd/util/output/schedule_printer.go | 2 +- .../volume_snapshot_location_printer.go | 2 +- pkg/cmd/velero/velero.go | 54 ++++++++-------- pkg/controller/backup_controller.go | 44 ++++++------- pkg/controller/backup_controller_test.go | 36 +++++------ pkg/controller/backup_deletion_controller.go | 42 ++++++------ .../backup_deletion_controller_test.go | 36 +++++------ pkg/controller/backup_finalizer_controller.go | 22 +++---- .../backup_finalizer_controller_test.go | 20 +++--- .../backup_operations_controller.go | 22 +++---- .../backup_operations_controller_test.go | 26 ++++---- pkg/controller/backup_queue_controller.go | 8 +-- .../backup_queue_controller_test.go | 6 +- .../backup_repository_controller.go | 16 ++--- .../backup_repository_controller_test.go | 22 +++---- .../backup_storage_location_controller.go | 14 ++-- ...backup_storage_location_controller_test.go | 16 ++--- pkg/controller/backup_sync_controller.go | 14 ++-- pkg/controller/backup_sync_controller_test.go | 14 ++-- pkg/controller/data_download_controller.go | 28 ++++---- .../data_download_controller_test.go | 24 +++---- pkg/controller/data_upload_controller.go | 26 ++++---- pkg/controller/data_upload_controller_test.go | 24 +++---- pkg/controller/download_request_controller.go | 12 ++-- .../download_request_controller_test.go | 12 ++-- pkg/controller/gc_controller.go | 14 ++-- pkg/controller/gc_controller_test.go | 6 +- .../pod_volume_backup_controller.go | 20 +++--- .../pod_volume_backup_controller_test.go | 20 +++--- .../pod_volume_restore_controller.go | 24 +++---- .../pod_volume_restore_controller_test.go | 24 +++---- pkg/controller/restore_controller.go | 44 ++++++------- pkg/controller/restore_controller_test.go | 28 ++++---- .../restore_finalizer_controller.go | 24 +++---- .../restore_finalizer_controller_test.go | 28 ++++---- .../restore_operations_controller.go | 16 ++--- .../restore_operations_controller_test.go | 24 +++---- pkg/controller/schedule_controller.go | 10 +-- pkg/controller/schedule_controller_test.go | 10 +-- .../server_status_request_controller.go | 12 ++-- .../server_status_request_controller_test.go | 12 ++-- pkg/controller/suite_test.go | 8 +-- pkg/datamover/backup_micro_service.go | 14 ++-- pkg/datamover/backup_micro_service_test.go | 14 ++-- pkg/datamover/dataupload_delete_action.go | 10 +-- .../dataupload_delete_action_test.go | 10 +-- pkg/datamover/restore_micro_service.go | 14 ++-- pkg/datamover/restore_micro_service_test.go | 14 ++-- pkg/datapath/data_path.go | 20 +++--- pkg/datapath/data_path_test.go | 6 +- pkg/datapath/micro_service_watcher.go | 6 +- pkg/datapath/micro_service_watcher_test.go | 8 +-- pkg/datapath/mocks/asyncBR.go | 2 +- pkg/datapath/types.go | 2 +- pkg/discovery/helper.go | 6 +- pkg/discovery/helper_test.go | 8 +-- pkg/exposer/cache_volume.go | 4 +- pkg/exposer/csi_snapshot.go | 12 ++-- pkg/exposer/csi_snapshot_priority_test.go | 6 +- pkg/exposer/csi_snapshot_test.go | 12 ++-- pkg/exposer/generic_restore.go | 8 +-- pkg/exposer/generic_restore_priority_test.go | 6 +- pkg/exposer/generic_restore_test.go | 6 +- pkg/exposer/host_path.go | 10 +-- pkg/exposer/host_path_test.go | 14 ++-- pkg/exposer/image.go | 2 +- pkg/exposer/image_test.go | 2 +- pkg/exposer/mocks/GenericRestoreExposer.go | 2 +- pkg/exposer/mocks/PodVolumeExposer.go | 2 +- pkg/exposer/pod_volume.go | 8 +-- pkg/exposer/pod_volume_test.go | 10 +-- pkg/exposer/vgdp_counter.go | 4 +- pkg/exposer/vgdp_counter_test.go | 8 +-- pkg/install/daemonset.go | 4 +- pkg/install/deployment.go | 6 +- pkg/install/deployment_test.go | 2 +- pkg/install/import_test.go | 2 +- pkg/install/install.go | 4 +- pkg/install/install_test.go | 4 +- pkg/install/resources.go | 8 +-- pkg/itemblock/actions/pod_action.go | 6 +- pkg/itemblock/actions/pod_action_test.go | 6 +- pkg/itemblock/actions/pvc_action.go | 14 ++-- pkg/itemblock/actions/pvc_action_test.go | 12 ++-- .../actions/service_account_action.go | 8 +-- .../actions/service_account_action_test.go | 8 +-- pkg/itemoperation/backup_operation.go | 2 +- pkg/itemoperation/restore_operation.go | 2 +- pkg/itemoperationmap/backup_operation_map.go | 6 +- pkg/itemoperationmap/restore_operation_map.go | 6 +- pkg/kopia/kopia_log_test.go | 2 +- pkg/label/label.go | 2 +- pkg/nodeagent/node_agent.go | 4 +- pkg/nodeagent/node_agent_test.go | 6 +- pkg/persistence/mocks/backup_store.go | 10 +-- pkg/persistence/object_store.go | 14 ++-- pkg/persistence/object_store_test.go | 22 +++---- .../v1/restartable_backup_item_action.go | 10 +-- .../v1/restartable_backup_item_action_test.go | 12 ++-- .../v2/restartable_backup_item_action.go | 12 ++-- .../v2/restartable_backup_item_action_test.go | 12 ++-- .../v1/restartable_item_block_action.go | 10 +-- .../v1/restartable_item_block_action_test.go | 12 ++-- pkg/plugin/clientmgmt/manager.go | 30 ++++----- pkg/plugin/clientmgmt/manager_test.go | 22 +++---- .../clientmgmt/process/client_builder.go | 10 +-- .../clientmgmt/process/client_builder_test.go | 12 ++-- pkg/plugin/clientmgmt/process/process.go | 2 +- pkg/plugin/clientmgmt/process/process_test.go | 4 +- pkg/plugin/clientmgmt/process/registry.go | 6 +- .../clientmgmt/process/registry_test.go | 2 +- .../restartable_delete_item_action.go | 6 +- .../restartable_delete_item_action_test.go | 12 ++-- .../clientmgmt/restartable_object_store.go | 6 +- .../restartable_object_store_test.go | 8 +-- .../v1/restartable_restore_item_action.go | 8 +-- .../restartable_restore_item_action_test.go | 12 ++-- .../v2/restartable_restore_item_action.go | 12 ++-- .../restartable_restore_item_action_test.go | 12 ++-- .../v1/restartable_volume_snapshotter.go | 6 +- .../v1/restartable_volume_snapshotter_test.go | 8 +-- pkg/plugin/framework/action_resolver.go | 16 ++--- pkg/plugin/framework/action_resolver_test.go | 4 +- pkg/plugin/framework/backup_item_action.go | 4 +- .../framework/backup_item_action_client.go | 8 +-- .../framework/backup_item_action_server.go | 10 +-- .../framework/backup_item_action_test.go | 12 ++-- .../backupitemaction/v2/backup_item_action.go | 4 +- .../v2/backup_item_action_client.go | 8 +-- .../v2/backup_item_action_server.go | 12 ++-- .../v2/backup_item_action_test.go | 14 ++-- .../framework/common/client_dispenser_test.go | 2 +- pkg/plugin/framework/common/client_errors.go | 2 +- .../framework/common/plugin_base_test.go | 2 +- .../framework/common/plugin_config_test.go | 2 +- pkg/plugin/framework/common/server_errors.go | 4 +- pkg/plugin/framework/delete_item_action.go | 4 +- .../framework/delete_item_action_client.go | 6 +- .../framework/delete_item_action_server.go | 8 +-- pkg/plugin/framework/examples_test.go | 2 +- pkg/plugin/framework/import_test.go | 2 +- .../itemblockaction/v1/item_block_action.go | 4 +- .../v1/item_block_action_client.go | 8 +-- .../v1/item_block_action_server.go | 12 ++-- .../v1/item_block_action_test.go | 14 ++-- pkg/plugin/framework/logger.go | 2 +- pkg/plugin/framework/logger_test.go | 2 +- pkg/plugin/framework/object_store.go | 4 +- pkg/plugin/framework/object_store_client.go | 4 +- pkg/plugin/framework/object_store_server.go | 6 +- pkg/plugin/framework/plugin_lister.go | 4 +- pkg/plugin/framework/restore_item_action.go | 4 +- .../framework/restore_item_action_client.go | 8 +-- .../framework/restore_item_action_server.go | 10 +-- .../v2/restore_item_action.go | 4 +- .../v2/restore_item_action_client.go | 10 +-- .../v2/restore_item_action_server.go | 12 ++-- pkg/plugin/framework/server.go | 10 +-- pkg/plugin/framework/volume_snapshotter.go | 4 +- .../framework/volume_snapshotter_client.go | 4 +- .../framework/volume_snapshotter_server.go | 6 +- .../v2/BackupItemAction.pb.go | 2 +- .../itemblockaction/v1/ItemBlockAction.pb.go | 2 +- .../v2/RestoreItemAction.pb.go | 2 +- pkg/plugin/mocks/manager.go | 14 ++-- pkg/plugin/mocks/process_factory.go | 2 +- pkg/plugin/proto/BackupItemAction.proto | 2 +- pkg/plugin/proto/DeleteItemAction.proto | 2 +- pkg/plugin/proto/ObjectStore.proto | 2 +- pkg/plugin/proto/PluginLister.proto | 2 +- pkg/plugin/proto/RestoreItemAction.proto | 2 +- pkg/plugin/proto/Shared.proto | 2 +- pkg/plugin/proto/VolumeSnapshotter.proto | 2 +- .../v2/BackupItemAction.proto | 2 +- .../itemblockaction/v1/ItemBlockAction.proto | 2 +- .../v2/RestoreItemAction.proto | 2 +- .../volumehelper/volume_policy_helper.go | 12 ++-- .../volumehelper/volume_policy_helper_test.go | 8 +-- .../backupitemaction/v1/backup_item_action.go | 4 +- .../backupitemaction/v2/backup_item_action.go | 4 +- pkg/plugin/velero/delete_item_action.go | 2 +- .../itemblockaction/v1/item_block_action.go | 4 +- pkg/plugin/velero/mocks/DeleteItemAction.go | 2 +- .../backupitemaction/v1/BackupItemAction.go | 4 +- .../backupitemaction/v2/BackupItemAction.go | 4 +- .../itemblockaction/v1/ItemBlockAction.go | 4 +- .../restoreitemaction/v1/RestoreItemAction.go | 2 +- .../restoreitemaction/v2/RestoreItemAction.go | 4 +- .../velero/restore_item_action_shared.go | 2 +- .../v1/restore_item_action.go | 2 +- .../v2/restore_item_action.go | 4 +- pkg/podexec/pod_command_executor.go | 2 +- pkg/podexec/pod_command_executor_test.go | 4 +- pkg/podvolume/backup_micro_service.go | 12 ++-- pkg/podvolume/backup_micro_service_test.go | 12 ++-- pkg/podvolume/backupper.go | 26 ++++---- pkg/podvolume/backupper_factory.go | 4 +- pkg/podvolume/backupper_test.go | 10 +-- pkg/podvolume/mocks/restorer.go | 4 +- pkg/podvolume/restore_micro_service.go | 12 ++-- pkg/podvolume/restore_micro_service_test.go | 12 ++-- pkg/podvolume/restorer.go | 18 +++--- pkg/podvolume/restorer_factory.go | 4 +- pkg/podvolume/restorer_test.go | 10 +-- pkg/podvolume/snaphost_tracker_test.go | 2 +- pkg/podvolume/util.go | 12 ++-- pkg/podvolume/util_test.go | 4 +- pkg/repository/backup_repo_op.go | 4 +- pkg/repository/backup_repo_op_test.go | 4 +- pkg/repository/config/azure.go | 2 +- pkg/repository/config/azure_test.go | 2 +- pkg/repository/ensurer.go | 2 +- pkg/repository/ensurer_test.go | 4 +- pkg/repository/keys/keys.go | 2 +- pkg/repository/maintenance/maintenance.go | 16 ++--- .../maintenance/maintenance_test.go | 18 +++--- pkg/repository/manager/manager.go | 10 +-- pkg/repository/manager/manager_test.go | 2 +- pkg/repository/mocks/Manager.go | 2 +- pkg/repository/provider/provider.go | 2 +- pkg/repository/provider/unified_repo.go | 12 ++-- pkg/repository/provider/unified_repo_test.go | 12 ++-- .../udmrepo/kopialib/backend/azure.go | 6 +- .../backend/azure/azure_storage_wrapper.go | 6 +- .../udmrepo/kopialib/backend/azure_test.go | 4 +- .../udmrepo/kopialib/backend/common.go | 2 +- .../udmrepo/kopialib/backend/common_test.go | 2 +- .../udmrepo/kopialib/backend/file_system.go | 4 +- .../kopialib/backend/file_system_test.go | 4 +- .../udmrepo/kopialib/backend/gcs.go | 4 +- .../udmrepo/kopialib/backend/gcs_test.go | 4 +- pkg/repository/udmrepo/kopialib/backend/s3.go | 4 +- .../udmrepo/kopialib/backend/s3_test.go | 4 +- .../udmrepo/kopialib/backend/utils_test.go | 2 +- pkg/repository/udmrepo/kopialib/lib_repo.go | 6 +- .../udmrepo/kopialib/lib_repo_test.go | 6 +- pkg/repository/udmrepo/kopialib/repo_init.go | 6 +- .../udmrepo/kopialib/repo_init_test.go | 10 +-- pkg/repository/udmrepo/mocks/BackupRepo.go | 2 +- .../udmrepo/mocks/BackupRepoService.go | 2 +- pkg/repository/udmrepo/mocks/ObjectWriter.go | 2 +- pkg/repository/udmrepo/service/service.go | 4 +- pkg/restic/common.go | 8 +-- pkg/restic/common_test.go | 4 +- pkg/restic/exec_commands.go | 6 +- pkg/restic/exec_commands_test.go | 4 +- .../actions/add_pvc_from_pod_action.go | 4 +- .../actions/add_pvc_from_pod_action_test.go | 6 +- .../actions/admissionwebhook_config_action.go | 4 +- .../admissionwebhook_config_action_test.go | 4 +- pkg/restore/actions/apiservice_action.go | 2 +- pkg/restore/actions/apiservice_action_test.go | 4 +- .../actions/change_image_name_action.go | 4 +- .../actions/change_image_name_action_test.go | 4 +- .../actions/change_storageclass_action.go | 4 +- .../change_storageclass_action_test.go | 4 +- .../actions/clusterrolebinding_action.go | 2 +- .../actions/clusterrolebinding_action_test.go | 6 +- .../crd_v1_preserve_unknown_fields_action.go | 2 +- ..._v1_preserve_unknown_fields_action_test.go | 8 +-- pkg/restore/actions/csi/pvc_action.go | 22 +++---- pkg/restore/actions/csi/pvc_action_test.go | 20 +++--- .../actions/csi/volumesnapshot_action.go | 14 ++-- .../actions/csi/volumesnapshot_action_test.go | 12 ++-- .../actions/csi/volumesnapshotclass_action.go | 8 +-- .../csi/volumesnapshotclass_action_test.go | 10 +-- .../csi/volumesnapshotcontent_action.go | 14 ++-- .../csi/volumesnapshotcontent_action_test.go | 14 ++-- .../actions/dataupload_retrieve_action.go | 10 +-- .../dataupload_retrieve_action_test.go | 12 ++-- .../actions/init_restorehook_pod_action.go | 6 +- .../init_restorehook_pod_action_test.go | 10 +-- pkg/restore/actions/job_action.go | 2 +- pkg/restore/actions/job_action_test.go | 4 +- pkg/restore/actions/pod_action.go | 4 +- pkg/restore/actions/pod_action_test.go | 6 +- .../actions/pod_volume_restore_action.go | 22 +++---- .../actions/pod_volume_restore_action_test.go | 16 ++--- pkg/restore/actions/pvc_action.go | 8 +-- pkg/restore/actions/pvc_action_test.go | 8 +-- pkg/restore/actions/rolebinding_action.go | 2 +- .../actions/rolebinding_action_test.go | 6 +- pkg/restore/actions/secret_action.go | 4 +- pkg/restore/actions/secret_action_test.go | 4 +- pkg/restore/actions/service_account_action.go | 4 +- .../actions/service_account_action_test.go | 4 +- pkg/restore/actions/service_action.go | 4 +- pkg/restore/actions/service_action_test.go | 8 +-- pkg/restore/merge_service_account_test.go | 2 +- pkg/restore/prioritize_group_version.go | 6 +- pkg/restore/prioritize_group_version_test.go | 4 +- pkg/restore/pv_restorer.go | 8 +-- pkg/restore/pv_restorer_test.go | 12 ++-- pkg/restore/request.go | 10 +-- pkg/restore/restore.go | 56 ++++++++-------- pkg/restore/restore_test.go | 42 ++++++------ pkg/restore/restore_wildcard_test.go | 4 +- pkg/test/fake_controller_runtime_client.go | 4 +- pkg/test/fake_dynamic.go | 2 +- pkg/test/fake_file_system.go | 2 +- pkg/test/mock_pod_command_executor.go | 2 +- pkg/test/tar_writer.go | 2 +- pkg/types/node_agent.go | 2 +- pkg/types/repo_maintenance.go | 2 +- pkg/uploader/cbt/bitmap.go | 2 +- pkg/uploader/cbt/set.go | 4 +- pkg/uploader/cbt/set_test.go | 6 +- pkg/uploader/cbt/types/mocks/Bitmap.go | 2 +- pkg/uploader/kopia/progress.go | 2 +- pkg/uploader/kopia/progress_test.go | 2 +- pkg/uploader/kopia/shim.go | 2 +- pkg/uploader/kopia/shim_test.go | 4 +- pkg/uploader/kopia/snapshot.go | 8 +-- pkg/uploader/kopia/snapshot_test.go | 6 +- pkg/uploader/provider/block.go | 10 +-- pkg/uploader/provider/block_test.go | 12 ++-- pkg/uploader/provider/kopia.go | 14 ++-- pkg/uploader/provider/kopia_test.go | 18 +++--- pkg/uploader/provider/mocks/Provider.go | 4 +- pkg/uploader/provider/provider.go | 8 +-- pkg/uploader/provider/provider_test.go | 8 +-- pkg/uploader/util/uploader_config.go | 2 +- pkg/uploader/util/uploader_config_test.go | 2 +- pkg/util/actionhelpers/pod_helper.go | 4 +- pkg/util/actionhelpers/pvc_helper.go | 4 +- .../actionhelpers/service_account_helper.go | 6 +- pkg/util/azure/storage.go | 4 +- pkg/util/collections/includes_excludes.go | 14 ++-- .../collections/includes_excludes_test.go | 8 +-- pkg/util/csi/util.go | 4 +- pkg/util/csi/util_test.go | 2 +- pkg/util/csi/volume_snapshot.go | 8 +-- pkg/util/csi/volume_snapshot_test.go | 14 ++-- pkg/util/encode/encode.go | 4 +- pkg/util/kube/client.go | 2 +- pkg/util/kube/event_test.go | 2 +- pkg/util/kube/list_watch_test.go | 4 +- pkg/util/kube/node_test.go | 4 +- .../kube/periodical_enqueue_source_test.go | 4 +- pkg/util/kube/pod_test.go | 2 +- pkg/util/kube/predicate_test.go | 2 +- pkg/util/kube/priority_class_test.go | 2 +- pkg/util/kube/pvc_pv_test.go | 4 +- pkg/util/kube/resource_requirements.go | 2 +- pkg/util/kube/secrets_test.go | 4 +- pkg/util/kube/security_context_test.go | 2 +- pkg/util/kube/utils.go | 10 +-- pkg/util/kube/utils_test.go | 6 +- pkg/util/logging/dual_mode_logger_test.go | 2 +- pkg/util/logging/error_location_hook_test.go | 2 +- pkg/util/logging/format_flag.go | 2 +- pkg/util/logging/log_counter_hook.go | 2 +- pkg/util/logging/log_counter_hook_test.go | 2 +- pkg/util/logging/log_level_flag.go | 2 +- pkg/util/logging/log_location_hook.go | 6 +- pkg/util/logging/log_location_hook_test.go | 4 +- pkg/util/podvolume/pod_volume.go | 4 +- pkg/util/podvolume/pod_volume_test.go | 4 +- pkg/util/scheme.go | 4 +- pkg/util/velero/restore/util.go | 2 +- pkg/util/velero/restore/util_test.go | 2 +- pkg/util/velero/velero.go | 2 +- pkg/util/velero/velero_test.go | 6 +- restore-hooks_product-requirements.md | 10 +-- test/e2e/README.md | 4 +- test/e2e/backup/backup.go | 12 ++-- test/e2e/backups/deletion.go | 10 +-- test/e2e/backups/sync_backups.go | 10 +-- test/e2e/backups/ttl.go | 10 +-- .../api-group/enable_api_group_extentions.go | 6 +- .../api-group/enable_api_group_versions.go | 10 +-- test/e2e/basic/backup-volume-info/base.go | 12 ++-- .../backup-volume-info/csi_data_mover.go | 6 +- .../basic/backup-volume-info/csi_snapshot.go | 6 +- .../backup-volume-info/filesystem_upload.go | 6 +- .../backup-volume-info/native_snapshot.go | 6 +- .../backup-volume-info/skipped_volumes.go | 6 +- test/e2e/basic/namespace-mapping.go | 6 +- test/e2e/basic/nodeport.go | 8 +-- test/e2e/basic/resources-check/namespaces.go | 4 +- .../resources-check/namespaces_annotation.go | 4 +- test/e2e/basic/resources-check/rbac.go | 4 +- .../basic/resources-check/resources_check.go | 2 +- test/e2e/basic/restore_exec_hooks.go | 8 +-- test/e2e/basic/storage-class-changing.go | 12 ++-- test/e2e/bsl-mgmt/deletion.go | 12 ++-- test/e2e/e2e_suite_test.go | 48 +++++++------- test/e2e/migration/migration.go | 18 +++--- test/e2e/nodeagentconfig/cache_pvc.go | 14 ++-- test/e2e/nodeagentconfig/node-agent-config.go | 18 +++--- .../parallel_files_download.go | 8 +-- .../parallel_files_upload.go | 8 +-- test/e2e/privilegesmgmt/ssr.go | 8 +-- test/e2e/pv-backup/pv-backup-filter.go | 10 +-- .../repo_maintenance_config.go | 18 +++--- test/e2e/resource-filtering/base.go | 6 +- test/e2e/resource-filtering/exclude_label.go | 8 +-- .../resource-filtering/exclude_namespaces.go | 4 +- .../resource-filtering/exclude_resources.go | 6 +- .../resource-filtering/include_namespaces.go | 4 +- .../resource-filtering/include_resources.go | 4 +- test/e2e/resource-filtering/label_selector.go | 6 +- .../resource-filtering/wildcard_namespaces.go | 4 +- .../resourcemodifiers/resource_modifiers.go | 6 +- .../e2e/resourcepolicies/resource_policies.go | 8 +-- test/e2e/scale/multiple_namespaces.go | 4 +- test/e2e/schedule/in_progress.go | 12 ++-- test/e2e/schedule/ordered_resources.go | 12 ++-- test/e2e/schedule/periodical.go | 8 +-- test/e2e/test/test.go | 12 ++-- test/e2e/upgrade/upgrade.go | 14 ++-- test/perf/README.md | 2 +- test/perf/backup/backup.go | 4 +- test/perf/basic/basic.go | 6 +- test/perf/e2e_suite_test.go | 18 +++--- test/perf/metrics/minio.go | 2 +- test/perf/metrics/nfs.go | 2 +- test/perf/metrics/pod.go | 2 +- test/perf/restore/restore.go | 8 +-- test/perf/test/test.go | 14 ++-- test/pkg/client/client.go | 2 +- test/pkg/client/factory.go | 4 +- test/types.go | 4 +- test/util/csi/common.go | 2 +- test/util/eks/eks.go | 2 +- test/util/k8s/client.go | 2 +- test/util/k8s/clusterrolebinding.go | 2 +- test/util/k8s/common.go | 6 +- test/util/k8s/crd.go | 2 +- test/util/k8s/deployment.go | 4 +- test/util/k8s/namespace.go | 4 +- test/util/k8s/node.go | 2 +- test/util/k8s/pod.go | 4 +- test/util/k8s/serviceaccount.go | 2 +- test/util/k8s/statefulset.go | 2 +- test/util/kibishii/kibishii_utils.go | 12 ++-- test/util/metrics/minio.go | 2 +- test/util/providers/aws_utils.go | 4 +- test/util/providers/azure_utils.go | 4 +- test/util/providers/common.go | 6 +- test/util/providers/gcloud_utils.go | 2 +- test/util/report/report.go | 2 +- test/util/velero/install.go | 20 +++--- test/util/velero/velero_utils.go | 24 +++---- 713 files changed, 2900 insertions(+), 2900 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 68e065038..6851cf68b 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -40,7 +40,7 @@ Please provide the output of the following commands (Pasting long output into a **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "I would like to see this bug fixed as soon as possible" diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 6468a2e2f..6e4e6841b 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1,5 @@ blank_issues_enabled: false contact_links: - name: Velero Q&A - url: https://github.com/velero-io/velero/discussions/categories/community-support-q-a + url: https://github.com/vmware-tanzu/velero/discussions/categories/community-support-q-a about: Have questions about Velero? Please ask them here. diff --git a/.github/ISSUE_TEMPLATE/feature-enhancement-request.md b/.github/ISSUE_TEMPLATE/feature-enhancement-request.md index 7e839def3..bf95fd986 100644 --- a/.github/ISSUE_TEMPLATE/feature-enhancement-request.md +++ b/.github/ISSUE_TEMPLATE/feature-enhancement-request.md @@ -26,7 +26,7 @@ about: Suggest an idea for this project **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "The project would be better with this feature added" diff --git a/.gitignore b/.gitignore index e7e14f74d..ce62679f1 100644 --- a/.gitignore +++ b/.gitignore @@ -60,6 +60,6 @@ debug.test* .cache/ # Go telemetry directory created when container sets HOME to working directory -# This happens because Makefile uses 'docker run -w /github.com/velero-io/velero' +# This happens because Makefile uses 'docker run -w /github.com/vmware-tanzu/velero' # and Go's os.UserConfigDir() falls back to $HOME/.config when XDG_CONFIG_HOME is unset .config/ diff --git a/.golangci.yaml b/.golangci.yaml index 582ed84ba..72db2986b 100644 --- a/.golangci.yaml +++ b/.golangci.yaml @@ -423,7 +423,7 @@ formatters: simplify: true goimports: local-prefixes: - - github.com/velero-io/velero + - github.com/vmware-tanzu/velero severity: default: error diff --git a/.goreleaser.yml b/.goreleaser.yml index 1b30ab300..f206d3f9c 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -44,7 +44,7 @@ builds: - goos: windows goarch: s390x ldflags: - - -X "github.com/velero-io/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/velero-io/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/velero-io/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}" -X "github.com/velero-io/velero/pkg/buildinfo.ImageRegistry={{ .Env.REGISTRY }}" + - -X "github.com/vmware-tanzu/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.ImageRegistry={{ .Env.REGISTRY }}" archives: - name_template: "{{ .ProjectName }}-{{ .Tag }}-{{ .Os }}-{{ .Arch }}" wrap_in_directory: true diff --git a/ADOPTERS.md b/ADOPTERS.md index d8f320523..7bc46e9c3 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -82,8 +82,8 @@ If you would like to add your logo to a future `Adopters of Velero` section on [ [1]: #adding-a-logo-to-veleroio [2]: https://velero.io -[3]: https://github.com/velero-io/velero/pulls -[4]: https://github.com/velero-io/velero/pull/2242 +[3]: https://github.com/vmware-tanzu/velero/pulls +[4]: https://github.com/vmware-tanzu/velero/pull/2242 [10]: https://www.nirmata.com/2019/08/14/kubernetes-disaster-recovery-using-velero-and-nirmata/ [11]: https://nirmata.com diff --git a/CHANGELOG.md b/CHANGELOG.md index c29f81481..cc3e910d0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -28,29 +28,29 @@ * [CHANGELOG-0.3.md][1] -[25]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.15.md -[24]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.14.md -[23]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.13.md -[22]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.12.md -[21]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.11.md -[20]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.10.md -[19]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.9.md -[18]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.8.md -[17]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.7.md -[16]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.6.md -[15]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.5.md -[14]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.4.md -[13]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.3.md -[12]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.2.md -[11]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.1.md -[10]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-1.0.md -[9]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.11.md -[8]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.10.md -[7]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.9.md -[6]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.8.md -[5]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.7.md -[4]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.6.md -[3]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.5.md -[2]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.4.md -[1]: https://github.com/velero-io/velero/blob/main/changelogs/CHANGELOG-0.3.md -[0]: https://github.com/velero-io/velero/blob/main/changelogs/unreleased +[25]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.15.md +[24]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.14.md +[23]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.13.md +[22]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.12.md +[21]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.11.md +[20]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.10.md +[19]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.9.md +[18]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.8.md +[17]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.7.md +[16]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.6.md +[15]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.5.md +[14]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.4.md +[13]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.3.md +[12]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.2.md +[11]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.1.md +[10]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.0.md +[9]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.11.md +[8]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.10.md +[7]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.9.md +[6]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.8.md +[5]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.7.md +[4]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.6.md +[3]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.5.md +[2]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.4.md +[1]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-0.3.md +[0]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/unreleased diff --git a/Dockerfile b/Dockerfile index 3c6b8d460..12306fad2 100644 --- a/Dockerfile +++ b/Dockerfile @@ -34,9 +34,9 @@ ENV CGO_ENABLED=0 \ GOARM=${TARGETVARIANT} \ LDFLAGS="-X ${PKG}/pkg/buildinfo.Version=${VERSION} -X ${PKG}/pkg/buildinfo.GitSHA=${GIT_SHA} -X ${PKG}/pkg/buildinfo.GitTreeState=${GIT_TREE_STATE} -X ${PKG}/pkg/buildinfo.ImageRegistry=${REGISTRY}" -WORKDIR /go/src/github.com/velero-io/velero +WORKDIR /go/src/github.com/vmware-tanzu/velero -COPY . /go/src/github.com/velero-io/velero +COPY . /go/src/github.com/vmware-tanzu/velero RUN mkdir -p /output/usr/bin && \ export GOARM=$( echo "${GOARM}" | cut -c2-) && \ diff --git a/Dockerfile-Windows b/Dockerfile-Windows index 26774b375..df588def5 100644 --- a/Dockerfile-Windows +++ b/Dockerfile-Windows @@ -36,9 +36,9 @@ ENV CGO_ENABLED=0 \ GOARM=${TARGETVARIANT} \ LDFLAGS="-X ${PKG}/pkg/buildinfo.Version=${VERSION} -X ${PKG}/pkg/buildinfo.GitSHA=${GIT_SHA} -X ${PKG}/pkg/buildinfo.GitTreeState=${GIT_TREE_STATE} -X ${PKG}/pkg/buildinfo.ImageRegistry=${REGISTRY}" -WORKDIR /go/src/github.com/velero-io/velero +WORKDIR /go/src/github.com/vmware-tanzu/velero -COPY . /go/src/github.com/velero-io/velero +COPY . /go/src/github.com/vmware-tanzu/velero RUN mkdir -p /output/usr/bin && \ export GOARM=$( echo "${GOARM}" | cut -c2-) && \ diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 0bf265329..687baeb00 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -10,14 +10,14 @@ This document defines the project governance for Velero. The following code repositories are governed by Velero community and maintained under the `vmware-tanzu\Velero` organization. -* **[Velero](https://github.com/velero-io/velero):** Main Velero codebase +* **[Velero](https://github.com/vmware-tanzu/velero):** Main Velero codebase * **[Helm Chart](https://github.com/vmware-tanzu/helm-charts/tree/main/charts/velero):** The Helm chart for the Velero server component -* **[Velero CSI Plugin](https://github.com/velero-io/velero-plugin-for-csi):** This repository contains Velero plugins for snapshotting CSI backed PVCs using the CSI beta snapshot APIs -* **[Velero Plugin for vSphere](https://github.com/velero-io/velero-plugin-for-vsphere):** This repository contains the Velero Plugin for vSphere. This plugin is a volume snapshotter plugin that provides crash-consistent snapshots of vSphere block volumes and backup of volume data into S3 compatible storage. -* **[Velero Plugin for AWS](https://github.com/velero-io/velero-plugin-for-aws):** This repository contains the plugins to support running Velero on AWS, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin for GCP](https://github.com/velero-io/velero-plugin-for-gcp):** This repository contains the plugins to support running Velero on GCP, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin for Azure](https://github.com/velero-io/velero-plugin-for-microsoft-azure):** This repository contains the plugins to support running Velero on Azure, including the object store plugin and the volume snapshotter plugin -* **[Velero Plugin Example](https://github.com/velero-io/velero-plugin-example):** This repository contains example plugins for Velero +* **[Velero CSI Plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi):** This repository contains Velero plugins for snapshotting CSI backed PVCs using the CSI beta snapshot APIs +* **[Velero Plugin for vSphere](https://github.com/vmware-tanzu/velero-plugin-for-vsphere):** This repository contains the Velero Plugin for vSphere. This plugin is a volume snapshotter plugin that provides crash-consistent snapshots of vSphere block volumes and backup of volume data into S3 compatible storage. +* **[Velero Plugin for AWS](https://github.com/vmware-tanzu/velero-plugin-for-aws):** This repository contains the plugins to support running Velero on AWS, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin for GCP](https://github.com/vmware-tanzu/velero-plugin-for-gcp):** This repository contains the plugins to support running Velero on GCP, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin for Azure](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure):** This repository contains the plugins to support running Velero on Azure, including the object store plugin and the volume snapshotter plugin +* **[Velero Plugin Example](https://github.com/vmware-tanzu/velero-plugin-example):** This repository contains example plugins for Velero ## Community Roles @@ -67,12 +67,12 @@ interested in implementing the proposal should be either deeply engaged in the proposal process or be an author of the proposal. The proposal should be documented as a separated markdown file pushed to the root of the -`design` folder in the [Velero](https://github.com/velero-io/velero/tree/main/design) +`design` folder in the [Velero](https://github.com/vmware-tanzu/velero/tree/main/design) repository via PR. The name of the file should follow the name pattern `_design.md`, e.g: `restore-hooks-design.md`. -Use the [Proposal Template](https://github.com/velero-io/velero/blob/main/design/_template.md) as a starting point. +Use the [Proposal Template](https://github.com/vmware-tanzu/velero/blob/main/design/_template.md) as a starting point. ### Proposal Lifecycle @@ -88,7 +88,7 @@ To maintain velocity in a project as busy as Velero, the concept of [Lazy Consensus](http://en.osswiki.info/concepts/lazy_consensus) is practiced. Ideas and / or proposals should be shared by maintainers via GitHub with the appropriate maintainer groups (e.g., -`@velero-io/velero-maintainers`) tagged. Out of respect for other contributors, +`@vmware-tanzu/velero-maintainers`) tagged. Out of respect for other contributors, major changes should also be accompanied by a ping on Slack or a note on the Velero mailing list as appropriate. Author(s) of proposal, Pull Requests, issues, etc. will give a time period of no less than five (5) working days for @@ -111,7 +111,7 @@ Lazy consensus does _not_ apply to the process of: ### Deprecation Process -Any contributor may introduce a request to deprecate a feature or an option of a feature by opening a feature request issue in the velero-io/velero GitHub project. The issue should describe why the feature is no longer needed or has become detrimental to Velero, as well as whether and how it has been superseded. The submitter should give as much detail as possible. +Any contributor may introduce a request to deprecate a feature or an option of a feature by opening a feature request issue in the vmware-tanzu/velero GitHub project. The issue should describe why the feature is no longer needed or has become detrimental to Velero, as well as whether and how it has been superseded. The submitter should give as much detail as possible. Once the issue is filed, a one-month discussion period begins. Discussions take place within the issue itself as well as in the community meetings. The person who opens the issue, or a maintainer, should add the date and time marking the end of the discussion period in a comment on the issue as soon as possible after it is opened. A decision on the issue needs to be made within this one-month period. diff --git a/MAINTAINERS.md b/MAINTAINERS.md index b3c157989..2789a573d 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,6 +1,6 @@ # Velero Maintainers -[GOVERNANCE.md](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities. +[GOVERNANCE.md](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities. ## Maintainers diff --git a/Makefile b/Makefile index cf0276f9b..80db72e3a 100644 --- a/Makefile +++ b/Makefile @@ -18,7 +18,7 @@ BIN ?= velero # This repo's root import path (under GOPATH). -PKG := github.com/velero-io/velero +PKG := github.com/vmware-tanzu/velero # Where to push the docker image. REGISTRY ?= velero @@ -194,7 +194,7 @@ TTY := $(shell tty -s && echo "-t") # Example: make shell CMD="date > datefile" shell: build-dirs build-env - @# bind-mount the Velero root dir in at /github.com/velero-io/velero + @# bind-mount the Velero root dir in at /github.com/vmware-tanzu/velero @# because the Kubernetes code-generator tools require the project to @# exist in a directory hierarchy ending like this (but *NOT* necessarily @# under $GOPATH). @@ -204,7 +204,7 @@ shell: build-dirs build-env -i $(TTY) \ --rm \ -u $$(id -u):$$(id -g) \ - -v "$$(pwd):/github.com/velero-io/velero:delegated" \ + -v "$$(pwd):/github.com/vmware-tanzu/velero:delegated" \ -v "$$(pwd)/_output/bin:/output:delegated" \ -v "$$(pwd)/.go/pkg:/go/pkg:delegated" \ -v "$$(pwd)/.go/std:/go/std:delegated" \ @@ -212,7 +212,7 @@ shell: build-dirs build-env -v "$$(pwd)/.go/go-build:/.cache/go-build:delegated" \ -v "$$(pwd)/.go/golangci-lint:/.cache/golangci-lint:delegated" \ -v "$$(pwd)/.go/goimports:/.cache/goimports:delegated" \ - -w /github.com/velero-io/velero \ + -w /github.com/vmware-tanzu/velero \ $(BUILDER_IMAGE) \ /bin/sh $(CMD) @@ -432,7 +432,7 @@ changelog: # PUBLISH=false \ # make release # -# To run the release, which will publish a *DRAFT* GitHub release in github.com/velero-io/velero +# To run the release, which will publish a *DRAFT* GitHub release in github.com/vmware-tanzu/velero # (you still need to review/publish the GitHub release manually): # GITHUB_TOKEN=your-github-token \ # RELEASE_NOTES_FILE=changelogs/CHANGELOG-1.2.md \ diff --git a/ROADMAP.md b/ROADMAP.md index a9b7037fe..798acf588 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1 +1 @@ -# Please go to the [Velero Wiki](https://github.com/velero-io/velero/wiki/) to see our latest roadmap, archived roadmaps and roadmap guidance. \ No newline at end of file +# Please go to the [Velero Wiki](https://github.com/vmware-tanzu/velero/wiki/) to see our latest roadmap, archived roadmaps and roadmap guidance. \ No newline at end of file diff --git a/SECURITY.md b/SECURITY.md index 219426f6f..84e6f45dc 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -5,7 +5,7 @@ Velero is an open source tool with a growing community devoted to safe backup an ## Supported Versions -The Velero project maintains the following [governance document](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md), [release document](https://github.com/velero-io/velero/blob/f42c63af1b9af445e38f78a7256b1c48ef79c10e/site/docs/main/release-instructions.md), and [support document](https://velero.io/docs/main/support-process/). Please refer to these for release and related details. Only the most recent version of Velero is supported. Each [release](https://github.com/velero-io/velero/releases) includes information about upgrading to the latest version. +The Velero project maintains the following [governance document](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md), [release document](https://github.com/vmware-tanzu/velero/blob/f42c63af1b9af445e38f78a7256b1c48ef79c10e/site/docs/main/release-instructions.md), and [support document](https://velero.io/docs/main/support-process/). Please refer to these for release and related details. Only the most recent version of Velero is supported. Each [release](https://github.com/vmware-tanzu/velero/releases) includes information about upgrading to the latest version. ## Reporting a Vulnerability - Private Disclosure Process @@ -18,7 +18,7 @@ If you know of a publicly disclosed security vulnerability for Velero, please ** **IMPORTANT: Do not file public issues on GitHub for security vulnerabilities** -To report a vulnerability or a security-related issue, please contact the email address with the details of the vulnerability. The email will be fielded by the Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/velero-io/velero/issues/new/choose) instead. +To report a vulnerability or a security-related issue, please contact the email address with the details of the vulnerability. The email will be fielded by the Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/vmware-tanzu/velero/issues/new/choose) instead. ## Proposed Email Content @@ -68,7 +68,7 @@ The Security Team will respond to vulnerability reports as follows: ## Public Disclosure Process -The Security Team publishes a [public advisory](https://github.com/velero-io/velero/security/advisories) to the Velero community via GitHub. In most cases, additional communication via Slack, Twitter, mailing lists, blog and other channels will assist in educating Velero users and rolling out the patched release to affected users. +The Security Team publishes a [public advisory](https://github.com/vmware-tanzu/velero/security/advisories) to the Velero community via GitHub. In most cases, additional communication via Slack, Twitter, mailing lists, blog and other channels will assist in educating Velero users and rolling out the patched release to affected users. The Security Team will also publish any mitigating steps users can take until the fix can be applied to their Velero instances. Velero distributors will handle creating and publishing their own security advisories. diff --git a/changelogs/CHANGELOG-0.10.md b/changelogs/CHANGELOG-0.10.md index 699d1dd9c..e4f451d9d 100644 --- a/changelogs/CHANGELOG-0.10.md +++ b/changelogs/CHANGELOG-0.10.md @@ -69,8 +69,8 @@ carefully to ensure a successful upgrade!** - The `Config` CRD has been replaced by `BackupStorageLocation` and `VolumeSnapshotLocation` CRDs. - The interface for external plugins (object/block stores, backup/restore item actions) has changed. If you have authored any custom plugins, they'll need to be updated for v0.10. - - The [`ObjectStore.ListCommonPrefixes`](https://github.com/velero-io/velero/blob/main/pkg/cloudprovider/object_store.go#L50) signature has changed to add a `prefix` parameter. - - Registering plugins has changed. Create a new plugin server with the `NewServer` function, and register plugins with the appropriate functions. See the [`Server`](https://github.com/velero-io/velero/blob/main/pkg/plugin/server.go#L37) interface for details. + - The [`ObjectStore.ListCommonPrefixes`](https://github.com/vmware-tanzu/velero/blob/main/pkg/cloudprovider/object_store.go#L50) signature has changed to add a `prefix` parameter. + - Registering plugins has changed. Create a new plugin server with the `NewServer` function, and register plugins with the appropriate functions. See the [`Server`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/server.go#L37) interface for details. - The organization of Ark data in object storage has changed. Existing data will need to be moved around to conform to the new layout. ### All Changes diff --git a/changelogs/CHANGELOG-0.9.md b/changelogs/CHANGELOG-0.9.md index 5e243128b..f29a0d28e 100644 --- a/changelogs/CHANGELOG-0.9.md +++ b/changelogs/CHANGELOG-0.9.md @@ -137,7 +137,7 @@ ### Highlights: * Ark now has support for backing up and restoring Kubernetes volumes using a free open-source backup tool called [restic](https://github.com/restic/restic). This provides users an out-of-the-box solution for backing up and restoring almost any type of Kubernetes volume, whether or not it has snapshot support - integrated with Ark. For more information, see the [documentation](https://github.com/velero-io/velero/blob/main/docs/restic.md). + integrated with Ark. For more information, see the [documentation](https://github.com/vmware-tanzu/velero/blob/main/docs/restic.md). * Support for Prometheus metrics has been added! View total number of backup attempts (including success or failure), total backup size in bytes, and backup durations. More metrics coming in future releases! diff --git a/changelogs/CHANGELOG-1.10.md b/changelogs/CHANGELOG-1.10.md index aba7d8419..412b23b07 100644 --- a/changelogs/CHANGELOG-1.10.md +++ b/changelogs/CHANGELOG-1.10.md @@ -2,7 +2,7 @@ ### 2022-11-23 ### Download -https://github.com/velero-io/velero/releases/tag/v1.10.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.10.0 ### Container Image `velero/velero:v1.10.0` @@ -20,7 +20,7 @@ In this release, we introduced the Unified Repository architecture to build a da In this release, we also deeply integrate Velero with Kopia, specifically, Kopia's uploader modules are isolated as a generic file system uploader; Kopia's repository modules are encapsulated as the unified backup repository. -For more information, refer to the [design document](https://github.com/velero-io/velero/blob/v1.10.0/design/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md). +For more information, refer to the [design document](https://github.com/vmware-tanzu/velero/blob/v1.10.0/design/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md). #### File system backup refactor Velero's file system backup (a.k.s. pod volume backup or formerly restic backup) is refactored as the first user of the Unified Repository architecture. Specifically, we added a new path, the Kopia path, besides the existing Restic path. While Restic path is still available and set as default, you can opt in Kopia path by specifying the `uploader-type` parameter at installation time. Meanwhile, you are free to restore from existing backups under either path, Velero dynamically switches to the correct path to process the restore. @@ -33,7 +33,7 @@ Meanwhile, we've created a performance guide for both Restic path and Kopia path #### Plugin versioning V1 refactor In this release, Velero moves plugins BackupItemAction, RestoreItemAction and VolumeSnapshotterAction to version v1, this allows future plugin changes that do not support backward compatibility, so is a preparation for various complex tasks, for example, data movement tasks. -For more information, refer to the [plugin versioning design document](https://github.com/velero-io/velero/blob/v1.10.0/design/plugin-versioning.md). +For more information, refer to the [plugin versioning design document](https://github.com/vmware-tanzu/velero/blob/v1.10.0/design/plugin-versioning.md). #### Refactor the controllers using Kubebuilder v3 In this release we continued our code modernization work, rewriting some controllers using Kubebuilder v3. This work is ongoing and we will continue to make progress in future releases. @@ -75,9 +75,9 @@ Due to file system backup refactor, below modules and parameters name have been Due to the major changes of file system backup, the old upgrade steps are not suitable any more. For the new upgrade steps, visit [v1.10 upgrade guide document](https://velero.io/docs/v1.10/upgrade-to-1.10/). #### Limitations/Known issues -In this release, Kopia backup repository (so the Kopia path of file system backup) doesn't support self signed certificate for S3 compatible storage. To track this problem, refer to this [Velero issue](https://github.com/velero-io/velero/issues/5123) or [Kopia issue](https://github.com/kopia/kopia/issues/1443). +In this release, Kopia backup repository (so the Kopia path of file system backup) doesn't support self signed certificate for S3 compatible storage. To track this problem, refer to this [Velero issue](https://github.com/vmware-tanzu/velero/issues/5123) or [Kopia issue](https://github.com/kopia/kopia/issues/1443). -Due to the code change in Velero, there will be some code change required in vSphere plugin, without which the functionality may be impacted. Therefore, if you are using vSphere plugin in your workflow, please hold the upgrade until the issue [#485](https://github.com/velero-io/velero-plugin-for-vsphere/issues/485) is fixed in vSphere plugin. +Due to the code change in Velero, there will be some code change required in vSphere plugin, without which the functionality may be impacted. Therefore, if you are using vSphere plugin in your workflow, please hold the upgrade until the issue [#485](https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/485) is fixed in vSphere plugin. ### All changes @@ -185,6 +185,6 @@ Related issue: #2413 (#5178, @allenxu404) * Delete opened issues triage action. (#5041, @jxun) * When spec.RestoreStatus is empty, don't restore status (#5008, @sseago) * Added DownloadTargetKindCSIBackupVolumeSnapshots for retrieving the signed URL to download only the ``-csi-volumesnapshots.json.gz and DownloadTargetKindCSIBackupVolumeSnapshotContents to download only ``-csi-volumesnapshotcontents.json.gz in the DownloadRequest CR structure. These files are already present in the backup layout. (#4980, @anshulahuja98) - * Refactor BackupItemAction proto and related code to backupitemaction/v1 package. This is part of implementation of the plugin version design https://github.com/velero-io/velero/blob/main/design/plugin-versioning.md (#4943, @phuongatemc) + * Refactor BackupItemAction proto and related code to backupitemaction/v1 package. This is part of implementation of the plugin version design https://github.com/vmware-tanzu/velero/blob/main/design/plugin-versioning.md (#4943, @phuongatemc) * Unified Repository Design (#4926, @Lyndon-Li) * Add credentials to volume snapshot locations (#4864, @sseago) \ No newline at end of file diff --git a/changelogs/CHANGELOG-1.11.md b/changelogs/CHANGELOG-1.11.md index 0eef338eb..75d08d4df 100644 --- a/changelogs/CHANGELOG-1.11.md +++ b/changelogs/CHANGELOG-1.11.md @@ -2,7 +2,7 @@ ### 2023-04-07 ### Download -https://github.com/velero-io/velero/releases/tag/v1.11.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.11.0 ### Container Image `velero/velero:v1.11.0` @@ -26,10 +26,10 @@ This feature implemented the RestoreItemAction v2. RIA v2 has three new methods: 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. #### Plugin Progress Monitoring -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. +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. #### 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 [policy API design](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md#api-design)Β 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. +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 [policy API design](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md#api-design)Β 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. #### Resource Filters that can distinguish cluster scope and namespace scope resources This feature adds four new resource filters for backup. The new filters are separated into cluster scope and namespace scope. Before this feature, Velero could not filter cluster scope resources precisely. This feature provides the ability and refactors existing resource filter parameters. diff --git a/changelogs/CHANGELOG-1.12.md b/changelogs/CHANGELOG-1.12.md index f65d5b663..4b980641a 100644 --- a/changelogs/CHANGELOG-1.12.md +++ b/changelogs/CHANGELOG-1.12.md @@ -2,7 +2,7 @@ ### 2023-08-18 ### Download -https://github.com/velero-io/velero/releases/tag/v1.12.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.12.0 ### Container Image `velero/velero:v1.12.0` @@ -23,17 +23,17 @@ CSI Snapshot Data Movement is useful in below scenarios: * For on-premises users, the storage usually doesn't support durable snapshots, so it is impossible/less efficient/cost ineffective to keep volume snapshots by the storage This feature helps to move the snapshot data to a storage with lower cost and larger scale for long time preservation. * For public cloud users, this feature helps users to fulfill the multiple cloud strategy. It allows users to back up volume snapshots from one cloud provider and preserve or restore the data to another cloud provider. Then users will be free to flow their business data across cloud providers based on Velero backup and restore -CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design ([Volume Snapshot Data Movement](https://github.com/velero-io/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md)). More details can be found in the design. +CSI Snapshot Data Movement is built according to the Volume Snapshot Data Movement design ([Volume Snapshot Data Movement](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md)). More details can be found in the design. #### Resource Modifiers In many use cases, customers often need to substitute specific values in Kubernetes resources during the restoration process like changing the namespace, changing the storage class, etc. -To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design ([Resource Modifiers](https://github.com/velero-io/velero/blob/main/design/Implemented/json-substitution-action-design.md)). +To address this need, Resource Modifiers (also known as JSON Substitutions) offer a generic solution in the restore workflow. It allows the user to define filters for specific resources and then specify a JSON patch (operator, path, value) to apply to the resource. This feature simplifies the process of making substitutions without requiring the implementation of a new RestoreItemAction plugin. More details can be found in Volume Snapshot Resource Modifiers design ([Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/json-substitution-action-design.md)). #### Multiple VolumeSnapshotClasses Prior to version 1.12, the Velero CSI plugin would choose the VolumeSnapshotClass in the cluster based on matching driver names and the presence of the "velero.io/csi-volumesnapshot-class" label. However, this approach proved inadequate for many user scenarios. -With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design ([Multiple VolumeSnapshotClasses](https://github.com/velero-io/velero/blob/main/design/Implemented/multiple-csi-volumesnapshotclass-support.md)). +With the introduction of version 1.12, Velero now offers support for multiple VolumeSnapshotClasses in the CSI Plugin, enabling users to select a specific class for a particular backup. More details can be found in Multiple VolumeSnapshotClasses design ([Multiple VolumeSnapshotClasses](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/multiple-csi-volumesnapshotclass-support.md)). #### Restore Finalizer Before v1.12, the restore controller would only delete restore resources but wouldn’t delete restore data from the backup storage location when the command `velero restore delete` was executed. The only chance Velero deletes restores data from the backup storage location is when the associated backup is deleted. diff --git a/changelogs/CHANGELOG-1.13.md b/changelogs/CHANGELOG-1.13.md index 26132ec64..ec7362bbe 100644 --- a/changelogs/CHANGELOG-1.13.md +++ b/changelogs/CHANGELOG-1.13.md @@ -2,7 +2,7 @@ ### 2024-01-10 ### Download -https://github.com/velero-io/velero/releases/tag/v1.13.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.13.0 ### Container Image `velero/velero:v1.13.0` @@ -16,7 +16,7 @@ https://velero.io/docs/v1.13/upgrade-to-1.13/ ### Highlights #### Resource Modifier Enhancement -Velero introduced the Resource Modifiers in v1.12.0. This feature allows users to specify a ConfigMap with a set of rules to modify the resources during restoration. However, only the JSON Patch is supported when creating the rules, and JSON Patch has some limitations, which cannot cover all use cases. In v1.13.0, Velero adds new support for JSON Merge Patch and Strategic Merge Patch, which provide more power and flexibility and allow users to use the same ConfigMap to apply patches on the resources. More design details can be found in [Support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers](https://github.com/velero-io/velero/blob/main/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md) design. For instructions on how to use the feature, please refer to the [Resource Modifiers](https://velero.io/docs/v1.13/restore-resource-modifiers/) doc. +Velero introduced the Resource Modifiers in v1.12.0. This feature allows users to specify a ConfigMap with a set of rules to modify the resources during restoration. However, only the JSON Patch is supported when creating the rules, and JSON Patch has some limitations, which cannot cover all use cases. In v1.13.0, Velero adds new support for JSON Merge Patch and Strategic Merge Patch, which provide more power and flexibility and allow users to use the same ConfigMap to apply patches on the resources. More design details can be found in [Support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md) design. For instructions on how to use the feature, please refer to the [Resource Modifiers](https://velero.io/docs/v1.13/restore-resource-modifiers/) doc. #### Node-Agent Concurrency Velero data movement activities from fs-backups and CSI snapshot data movements run in Velero node-agent, so may be hosted by every node in the cluster and consume resources (i.e. CPU, memory, network bandwidth) from there. With v1.13, users are allowed to configure how many data movement activities (a.k.a, loads) run in each node globally or by node, so that users can better leverage the performance of Velero data movement activities and the resource consumption in the cluster. For more information, check the [Node-Agent Concurrency](https://velero.io/docs/v1.13/node-agent-concurrency/) document. @@ -57,8 +57,8 @@ To fix CVEs and keep pace with Golang, Velero made changes as follows: ### Breaking changes * Backup describe command: due to the backup describe output enhancement, some existing information (i.e. the output for native snapshot, CSI snapshot, and fs-backup) has been moved to the Backup Volumes section with some format changes. -* API type changes: changes the field [DataMoverConfig](https://github.com/velero-io/velero/blob/v1.13.0/pkg/apis/velero/v2alpha1/data_upload_types.go#L54) in DataUploadSpec from `*map[string][string]`` to `map[string]string` -* Velero install command: due to the issue [#7264](https://github.com/velero-io/velero/issues/7264), v1.13.0 introduces a break change that make the informer cache enabled by default to keep the actual behavior consistent with the helper message(the informer cache is disabled by default before the change). +* API type changes: changes the field [DataMoverConfig](https://github.com/vmware-tanzu/velero/blob/v1.13.0/pkg/apis/velero/v2alpha1/data_upload_types.go#L54) in DataUploadSpec from `*map[string][string]`` to `map[string]string` +* Velero install command: due to the issue [#7264](https://github.com/vmware-tanzu/velero/issues/7264), v1.13.0 introduces a break change that make the informer cache enabled by default to keep the actual behavior consistent with the helper message(the informer cache is disabled by default before the change). ### Limitations/Known issues diff --git a/changelogs/CHANGELOG-1.14.md b/changelogs/CHANGELOG-1.14.md index 86a62b6b7..209334fc2 100644 --- a/changelogs/CHANGELOG-1.14.md +++ b/changelogs/CHANGELOG-1.14.md @@ -1,7 +1,7 @@ ## v1.14 ### Download -https://github.com/velero-io/velero/releases/tag/v1.14.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.14.0 ### Container Image `velero/velero:v1.14.0` diff --git a/changelogs/CHANGELOG-1.15.md b/changelogs/CHANGELOG-1.15.md index 883921563..e52d6f7f4 100644 --- a/changelogs/CHANGELOG-1.15.md +++ b/changelogs/CHANGELOG-1.15.md @@ -1,7 +1,7 @@ ## v1.15 ### Download -https://github.com/velero-io/velero/releases/tag/v1.15.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.15.0 ### Container Image `velero/velero:v1.15.0` @@ -19,13 +19,13 @@ Data transfer activities for CSI Snapshot Data Movement are moved from node-agen - This enables users to to control resource (i.e., cpu, memory) allocations in a granular manner, e.g., control them per backup/restore of a volume. - This enhances the resilience, crash of one data movement activity won't affect others. - This prevents unnecessary full backup because of host path changes after workload pods restart. -- For more information, check the design https://github.com/velero-io/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md. +- For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md. #### Item Block concepts and ItemBlockAction (IBA) plugin Item Block concepts are introduced for resource backups to help to achieve multiple thread backups. Specifically, correlated resources are categorized in the same item block and item blocks could be processed concurrently in multiple threads. ItemBlockAction plugin is introduced to help Velero to categorize resources into item blocks. At present, Velero provides built-in IBAs for pods and PVCs and Velero also supports customized IBAs for any resources. In v1.15, Velero doesn't support multiple thread process of item blocks though item block concepts and IBA plugins are fully supported. The multiple thread support will be delivered in future releases. -For more information, check the design https://github.com/velero-io/velero/blob/main/design/backup-performance-improvements.md. +For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/backup-performance-improvements.md. #### Node selection for repository maintenance job Repository maintenance are resource consuming tasks, Velero now allows you to configure the nodes to run repository maintenance jobs, so that you can run repository maintenance jobs in idle nodes or avoid them to run in nodes hosting critical workloads. @@ -50,9 +50,9 @@ For more information, check the document https://velero.io/docs/v1.15/backup-rep #### Performance improvements In 1.15, several performance related issues/enhancements are included, which makes significant performance improvements in specific scenarios: -- There was a memory leak of Velero server after plugin calls, now it is fixed, see issue https://github.com/velero-io/velero/issues/7925 -- The `client-burst/client-qps` parameters are automatically inherited to plugins, so that you can use the same velero server parameters to accelerate the plugin executions when large number of API server calls happen, see issue https://github.com/velero-io/velero/issues/7806 -- Maintenance of Kopia repository takes huge memory in scenarios that huge number of files have been backed up, Velero 1.15 has included the Kopia upstream enhancement to fix the problem, see issue https://github.com/velero-io/velero/issues/7510 +- There was a memory leak of Velero server after plugin calls, now it is fixed, see issue https://github.com/vmware-tanzu/velero/issues/7925 +- The `client-burst/client-qps` parameters are automatically inherited to plugins, so that you can use the same velero server parameters to accelerate the plugin executions when large number of API server calls happen, see issue https://github.com/vmware-tanzu/velero/issues/7806 +- Maintenance of Kopia repository takes huge memory in scenarios that huge number of files have been backed up, Velero 1.15 has included the Kopia upstream enhancement to fix the problem, see issue https://github.com/vmware-tanzu/velero/issues/7510 ### Runtime and dependencies Golang runtime: v1.22.8 @@ -65,7 +65,7 @@ Therefore, a user option is added in the same backup PVC configuration configMap ### Breaking changes #### Deprecation of Restic -Restic path for fs-backup is in deprecation process starting from 1.15. According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy), for 1.15, if Restic path is used the backup/restore of fs-backup still creates and succeeds, but you will see warnings in below scenarios: +Restic path for fs-backup is in deprecation process starting from 1.15. According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy), for 1.15, if Restic path is used the backup/restore of fs-backup still creates and succeeds, but you will see warnings in below scenarios: - When `--uploader-type=restic` is used in Velero installation - When Restic path is used to create backup/restore of fs-backup @@ -83,7 +83,7 @@ In 1.15, below Velero server parameters for repository maintenance jobs are move ``` #### Changing PVC selected-node feature is deprecated -In 1.15, the [Changing PVC selected-node feature](https://velero.io/docs/v1.15/restore-reference/#changing-pvc-selected-node) enters deprecation process and will be removed in future releases according to [Velero deprecation policy](https://github.com/velero-io/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy). Usage of this feature for any purpose is not recommended. +In 1.15, the [Changing PVC selected-node feature](https://velero.io/docs/v1.15/restore-reference/#changing-pvc-selected-node) enters deprecation process and will be removed in future releases according to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy). Usage of this feature for any purpose is not recommended. ### All Changes * add no-relabeling option to backupPVC configmap (#8288, @sseago) diff --git a/changelogs/CHANGELOG-1.16.md b/changelogs/CHANGELOG-1.16.md index b33ae4497..fa8793f16 100644 --- a/changelogs/CHANGELOG-1.16.md +++ b/changelogs/CHANGELOG-1.16.md @@ -1,7 +1,7 @@ ## v1.16 ### Download -https://github.com/velero-io/velero/releases/tag/v1.16.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.16.0 ### Container Image `velero/velero:v1.16.0` @@ -15,28 +15,28 @@ https://velero.io/docs/v1.16/upgrade-to-1.16/ ### Highlights #### Windows cluster support In v1.16, Velero supports to run in Windows clusters and backup/restore Windows workloads, either stateful or stateless: - * Hybrid build and all-in-one image: the build process is enhanced to build an all-in-one image for hybrid CPU architecture and hybrid platform. For more information, check the design https://github.com/velero-io/velero/blob/main/design/multiple-arch-build-with-windows.md + * Hybrid build and all-in-one image: the build process is enhanced to build an all-in-one image for hybrid CPU architecture and hybrid platform. For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/multiple-arch-build-with-windows.md * Deployment in Windows clusters: Velero node-agent, data mover pods and maintenance jobs now support to run in both linux and Windows nodes * Data mover backup/restore Windows workloads: Velero built-in data mover supports Windows workloads throughout its full cycle, i.e., discovery, backup, restore, pre/post hook, etc. It automatically identifies Windows workloads and schedules data mover pods to the right group of nodes -Check the epic issue https://github.com/velero-io/velero/issues/8289 for more information. +Check the epic issue https://github.com/vmware-tanzu/velero/issues/8289 for more information. #### Parallel Item Block backup v1.16 now supports to back up item blocks in parallel. Specifically, during backup, correlated resources are grouped in item blocks and Velero backup engine creates a thread pool to back up the item blocks in parallel. This significantly improves the backup throughput, especially when there are large scale of resources. Pre/post hooks also belongs to item blocks, so will also run in parallel along with the item blocks. Users are allowed to configure the parallelism through the `--item-block-worker-count` Velero server parameter. If not configured, the default parallelism is 1. -For more information, check issue https://github.com/velero-io/velero/issues/8334. +For more information, check issue https://github.com/vmware-tanzu/velero/issues/8334. #### Data mover restore enhancement in scalability -In previous releases, for each volume of WaitForFirstConsumer mode, data mover restore is only allowed to happen in the node that the volume is attached. This severely degrades the parallelism and the balance of node resource(CPU, memory, network bandwidth) consumption for data mover restore (https://github.com/velero-io/velero/issues/8044). +In previous releases, for each volume of WaitForFirstConsumer mode, data mover restore is only allowed to happen in the node that the volume is attached. This severely degrades the parallelism and the balance of node resource(CPU, memory, network bandwidth) consumption for data mover restore (https://github.com/vmware-tanzu/velero/issues/8044). -In v1.16, users are allowed to configure data mover restores running and spreading evenly across all nodes in the cluster. The configuration is done through a new flag `ignoreDelayBinding` in node-agent configuration (https://github.com/velero-io/velero/issues/8242). +In v1.16, users are allowed to configure data mover restores running and spreading evenly across all nodes in the cluster. The configuration is done through a new flag `ignoreDelayBinding` in node-agent configuration (https://github.com/vmware-tanzu/velero/issues/8242). #### Data mover enhancements in observability In 1.16, some observability enhancements are added: - * Output various statuses of intermediate objects for failures of data mover backup/restore (https://github.com/velero-io/velero/issues/8267) - * Output the errors when Velero fails to delete intermediate objects during clean up (https://github.com/velero-io/velero/issues/8125) + * Output various statuses of intermediate objects for failures of data mover backup/restore (https://github.com/vmware-tanzu/velero/issues/8267) + * Output the errors when Velero fails to delete intermediate objects during clean up (https://github.com/vmware-tanzu/velero/issues/8125) The outputs are in the same node-agent log and enabled automatically. @@ -45,24 +45,24 @@ In previous releases, a unnecessary VolumeSnapshotContent object is retained for In 1.16, the retained VolumeSnapshotContent is removed from the backup, so no unnecessary CSI objects are synced or restored. -For more information, check issue https://github.com/velero-io/velero/issues/8725. +For more information, check issue https://github.com/vmware-tanzu/velero/issues/8725. #### Backup Repository Maintenance enhancement in resiliency and observability In v1.16, some enhancements of backup repository maintenance are added to improve the observability and resiliency: - * A new backup repository maintenance history section, called `RecentMaintenance`, is added to the BackupRepository CR. Specifically, for each BackupRepository, including start/completion time, completion status and error message. (https://github.com/velero-io/velero/issues/7810) - * Running maintenance jobs are now recaptured after Velero server restarts. (https://github.com/velero-io/velero/issues/7753) - * The maintenance job will not be launched for readOnly BackupStorageLocation. (https://github.com/velero-io/velero/issues/8238) - * The backup repository will not try to initialize a new repository for readOnly BackupStorageLocation. (https://github.com/velero-io/velero/issues/8091) - * Users now are allowed to configure the intervals of an effective maintenance in the way of `normalGC`, `fastGC` and `eagerGC`, through the `fullMaintenanceInterval` parameter in backupRepository configuration. (https://github.com/velero-io/velero/issues/8364) + * A new backup repository maintenance history section, called `RecentMaintenance`, is added to the BackupRepository CR. Specifically, for each BackupRepository, including start/completion time, completion status and error message. (https://github.com/vmware-tanzu/velero/issues/7810) + * Running maintenance jobs are now recaptured after Velero server restarts. (https://github.com/vmware-tanzu/velero/issues/7753) + * The maintenance job will not be launched for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8238) + * The backup repository will not try to initialize a new repository for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8091) + * Users now are allowed to configure the intervals of an effective maintenance in the way of `normalGC`, `fastGC` and `eagerGC`, through the `fullMaintenanceInterval` parameter in backupRepository configuration. (https://github.com/vmware-tanzu/velero/issues/8364) #### Volume Policy enhancement of filtering volumes by PVC labels -In v1.16, Volume Policy is extended to support filtering volumes by PVC labels. (https://github.com/velero-io/velero/issues/8256). +In v1.16, Volume Policy is extended to support filtering volumes by PVC labels. (https://github.com/vmware-tanzu/velero/issues/8256). #### Resource Status restore per object -In v1.16, users are allowed to define whether to restore resource status per object through an annotation `velero.io/restore-status` set on the object. (https://github.com/velero-io/velero/issues/8204). +In v1.16, users are allowed to define whether to restore resource status per object through an annotation `velero.io/restore-status` set on the object. (https://github.com/vmware-tanzu/velero/issues/8204). #### Velero Restore Helper binary is merged into Velero image -In v1.16, Velero banaries, i.e., velero, velero-helper and velero-restore-helper, are all included into the single Velero image. (https://github.com/velero-io/velero/issues/8484). +In v1.16, Velero banaries, i.e., velero, velero-helper and velero-restore-helper, are all included into the single Velero image. (https://github.com/vmware-tanzu/velero/issues/8484). ### Runtime and dependencies Golang runtime: 1.23.7 diff --git a/changelogs/CHANGELOG-1.17.md b/changelogs/CHANGELOG-1.17.md index 85fa75557..54e1c22dc 100644 --- a/changelogs/CHANGELOG-1.17.md +++ b/changelogs/CHANGELOG-1.17.md @@ -1,7 +1,7 @@ ## v1.17 ### Download -https://github.com/velero-io/velero/releases/tag/v1.17.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.17.0 ### Container Image `velero/velero:v1.17.0` @@ -19,11 +19,11 @@ In v1.17, Velero fs-backup is modernized to the micro-service architecture, whic - fs-backup is more robust, the running backup/restore could survive from node-agent restart; and the resource allocation is in a more granular manner, the failure of one backup/restore won't impact others. - The resource usage of node-agent is steady, especially, the node-agent pods won't request huge memory and hold it for a long time. -Check design https://github.com/velero-io/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. #### fs-backup support Windows cluster In v1.17, Velero fs-backup supports to backup/restore Windows workloads. By leveraging the new micro-service architecture for fs-backup, data mover pods could run in Windows nodes and backup/restore Windows volumes. Together with CSI snapshot data movement for Windows which is delivered in 1.16, Velero now supports Windows workload backup/restore in full scenarios. -Check design https://github.com/velero-io/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details. #### Volume group snapshot support In v1.17, Velero supports [volume group snapshots](https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/) which is a beta feature in Kubernetes upstream, for both CSI snapshot backup and CSI snapshot data movement. This allows a snapshot to be taken from multiple volumes at the same point-in-time to achieve write order consistency, which is helpful to achieve better data consistency when multiple volumes being backed up are correlated. @@ -31,20 +31,20 @@ Check the document https://velero.io/docs/main/volume-group-snapshots/ for more #### Priority class support In v1.17, [Kubernetes priority class](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) is supported for all modules across Velero. Specifically, users are allowed to configure priority class to Velero server, node-agent, data mover pods, backup repository maintenance jobs separately. -Check design https://github.com/velero-io/velero/blob/main/design/Implemented/priority-class-name-support_design.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/priority-class-name-support_design.md for more details. #### Scalability and Resiliency improvements of data movers ##### Reduce excessive number of data mover pods in Pending state In v1.17, Velero allows users to set a `PrepareQueueLength` in the node-agent configuration, data mover pods and volumes out of this number won't be created until data path quota is available, so that excessive number cluster resources won't be taken unnecessarily, which is particularly helpful for large scale environments. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement. -Check design https://github.com/velero-io/velero/blob/main/design/node-agent-load-soothing.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/node-agent-load-soothing.md for more details. ##### Enhancement on node-agent restart handling for data movements In v1.17, data movements in all phases could survive from node-agent restart and resume themselves; when a data movement gets orphaned in special cases, e.g., cluster node absent, it could also be canceled appropriately after the restart. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement. -Check issue https://github.com/velero-io/velero/issues/8534 for more details. +Check issue https://github.com/vmware-tanzu/velero/issues/8534 for more details. ##### CSI snapshot data movement restore node-selection and node-selection by storage class In v1.17, CSI snapshot data movement restore acquires the same node-selection capability as backup, that is, users could specify which nodes can/cannot run data mover pods for both backup and restore now. And users are also allowed to configure the node-selection per storage class, which is particularly helpful to the environments where a storage class are not usable by all cluster nodes. -Check issue https://github.com/velero-io/velero/issues/8186 and https://github.com/velero-io/velero/issues/8223 for more details. +Check issue https://github.com/vmware-tanzu/velero/issues/8186 and https://github.com/vmware-tanzu/velero/issues/8223 for more details. #### Include/exclude policy support for resource policy In v1.17, Velero resource policy supports `includeExcludePolicy` besides the existing `volumePolicy`. This allows users to set include/exclude filters for resources in a resource policy configmap, so that these filters are reusable among multiple backups. @@ -58,7 +58,7 @@ kopia: 0.21.1 ### Breaking changes #### Deprecation of Restic -According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#deprecation-policy), backup of fs-backup under Restic path is removed in v1.17, so `--uploader-type=restic` is not a valid installation configuration anymore. This means you cannot create a backup under Restic path, but you can still restore from the previous backups under Restic path until v1.19. +According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy), backup of fs-backup under Restic path is removed in v1.17, so `--uploader-type=restic` is not a valid installation configuration anymore. This means you cannot create a backup under Restic path, but you can still restore from the previous backups under Restic path until v1.19. #### Repository maintenance job configurations are removed from Velero server parameter Since the repository maintenance job configurations are moved to repository maintenance job configMap, in v1.17 below Velero sever parameters are removed: diff --git a/changelogs/CHANGELOG-1.18.md b/changelogs/CHANGELOG-1.18.md index 358bee22e..66c486ddf 100644 --- a/changelogs/CHANGELOG-1.18.md +++ b/changelogs/CHANGELOG-1.18.md @@ -1,7 +1,7 @@ ## v1.18 ### Download -https://github.com/velero-io/velero/releases/tag/v1.18.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.18.0 ### Container Image `velero/velero:v1.18.0` @@ -16,7 +16,7 @@ https://velero.io/docs/v1.18/upgrade-to-1.18/ #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. -Check design https://github.com/velero-io/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: @@ -24,7 +24,7 @@ In v1.18, Velero allows users to configure cache volumes for data mover pods dur - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache limit configuration, cache volume with appropriate size helps to improve the restore throughput -Check design https://github.com/velero-io/velero/blob/main/design/Implemented/backup-repo-cache-volume.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/backup-repo-cache-volume.md for more details. #### Incremental size for data movers In v1.18, Velero allows users to observe the incremental size of data movers backups for CSI snapshot data movement and fs-backup, so that users could visually see the data reduction due to incremental backup. @@ -53,7 +53,7 @@ kopia: 0.22.3 ### Breaking changes #### Deprecation of PVC selected node feature -According to [Velero deprecation policy](https://github.com/velero-io/velero/blob/main/GOVERNANCE.md#deprecation-policy), PVC selected node feature is deprecated in v1.18. Velero could appropriately handle PVC's selected-node annotation, so users don't need to do anything particularly. +According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy), PVC selected node feature is deprecated in v1.18. Velero could appropriately handle PVC's selected-node annotation, so users don't need to do anything particularly. ### All Changes * Remove backup from running list when backup fails validation (#9498, @sseago) diff --git a/changelogs/CHANGELOG-1.2.md b/changelogs/CHANGELOG-1.2.md index 808111aa1..e3fd61641 100644 --- a/changelogs/CHANGELOG-1.2.md +++ b/changelogs/CHANGELOG-1.2.md @@ -2,7 +2,7 @@ #### 2019-11-07 ### Download -https://github.com/velero-io/velero/releases/tag/v1.2.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.2.0 ### Container Image `velero/velero:v1.2.0` diff --git a/changelogs/CHANGELOG-1.3.md b/changelogs/CHANGELOG-1.3.md index 6d1476431..6dbfb57d8 100644 --- a/changelogs/CHANGELOG-1.3.md +++ b/changelogs/CHANGELOG-1.3.md @@ -2,7 +2,7 @@ ### 2020-04-03 ### Download -https://github.com/velero-io/velero/releases/tag/v1.3.2 +https://github.com/vmware-tanzu/velero/releases/tag/v1.3.2 ### Container Image `velero/velero:v1.3.2` @@ -21,7 +21,7 @@ https://velero.io/docs/v1.3.2/upgrade-to-1.3/ ### 2020-03-10 ### Download -https://github.com/velero-io/velero/releases/tag/v1.3.1 +https://github.com/vmware-tanzu/velero/releases/tag/v1.3.1 ### Container Image `velero/velero:v1.3.1` @@ -44,7 +44,7 @@ Fixed a bug that caused failures when backing up CustomResourceDefinitions with #### 2020-03-02 ### Download -https://github.com/velero-io/velero/releases/tag/v1.3.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.3.0 ### Container Image `velero/velero:v1.3.0` @@ -83,10 +83,10 @@ 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/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)) +- 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)) ### All Changes diff --git a/changelogs/CHANGELOG-1.4.md b/changelogs/CHANGELOG-1.4.md index 71d26a61d..354e68514 100644 --- a/changelogs/CHANGELOG-1.4.md +++ b/changelogs/CHANGELOG-1.4.md @@ -2,7 +2,7 @@ ### 2020-07-13 ### Download -https://github.com/velero-io/velero/releases/tag/v1.4.2 +https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2 ### Container Image `velero/velero:v1.4.2` @@ -27,7 +27,7 @@ This tag was created in code, but has no associated docker image due to misconfi ### 2020-05-26 ### Download -https://github.com/velero-io/velero/releases/tag/v1.4.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0 ### Container Image `velero/velero:v1.4.0` diff --git a/changelogs/CHANGELOG-1.5.md b/changelogs/CHANGELOG-1.5.md index d71ba0bf7..7013a85e7 100644 --- a/changelogs/CHANGELOG-1.5.md +++ b/changelogs/CHANGELOG-1.5.md @@ -2,7 +2,7 @@ ### 2020-09-16 ### Download -https://github.com/velero-io/velero/releases/tag/v1.5.1 +https://github.com/vmware-tanzu/velero/releases/tag/v1.5.1 ### Container Image `velero/velero:v1.5.1` @@ -57,7 +57,7 @@ Displays the Timestamps when issued a print or describe (#2748, @thejasbabu) * StorageGrid compatibility by removing explicit gzip accept header setting (#2712, @fvsqr) * restic: add support for setting SecurityContext (runAsUser, runAsGroup) for restore (#2621, @jaygridley) * Add backupValidationFailureTotal to metrics (#2714, @kathpeony) - * bump Kubernetes module dependencies to v0.18.4 to fix https://github.com/velero-io/velero/issues/2540 by adding code compatibility with kubernetes v1.18 (#2651, @laverya) + * bump Kubernetes module dependencies to v0.18.4 to fix https://github.com/vmware-tanzu/velero/issues/2540 by adding code compatibility with kubernetes v1.18 (#2651, @laverya) * Add a BSL controller to handle validation + update BSL status phase (validation removed from the server and no longer blocks when there's any invalid BSL) (#2674, @carlisia) * updated acceptable values on cron schedule from 0-7 to 0-6 (#2676, @dthrasher) * Improve velero download doc (#2660, @carlisia) diff --git a/changelogs/CHANGELOG-1.6.md b/changelogs/CHANGELOG-1.6.md index df1c24ab1..73cae45f0 100644 --- a/changelogs/CHANGELOG-1.6.md +++ b/changelogs/CHANGELOG-1.6.md @@ -2,7 +2,7 @@ ### 2021-04-12 ### Download -https://github.com/velero-io/velero/releases/tag/v1.6.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.6.0 ### Container Image `velero/velero:v1.6.0` diff --git a/changelogs/CHANGELOG-1.7.md b/changelogs/CHANGELOG-1.7.md index 5f769019a..fdff3c2b0 100644 --- a/changelogs/CHANGELOG-1.7.md +++ b/changelogs/CHANGELOG-1.7.md @@ -2,7 +2,7 @@ ### 2021-09-07 ### Download -https://github.com/velero-io/velero/releases/tag/v1.7.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.7.0 ### Container Image `velero/velero:v1.7.0` @@ -75,6 +75,6 @@ This command collects information about a Velero installation, such as pod logs * πŸ› Fix plugin name derivation from image name (#3711, @ashish-amarnath) * ✨ ⚠️ Remove CSI volumesnapshot artifact deletion -This change requires https://github.com/velero-io/velero-plugin-for-csi/pull/86 for Velero to continue +This change requires https://github.com/vmware-tanzu/velero-plugin-for-csi/pull/86 for Velero to continue deleting of CSI volumesnapshots when the corresponding backups are deleted. (#3734, @ashish-amarnath) * use unstructured to marshal selective fields for service restore action (#3789, @alaypatel07) diff --git a/changelogs/CHANGELOG-1.8.md b/changelogs/CHANGELOG-1.8.md index c45b56536..e317849d1 100644 --- a/changelogs/CHANGELOG-1.8.md +++ b/changelogs/CHANGELOG-1.8.md @@ -2,7 +2,7 @@ ### 2022-01-14 ### Download -https://github.com/velero-io/velero/releases/tag/v1.8.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.8.0 ### Container Image `velero/velero:v1.8.0` @@ -41,7 +41,7 @@ When a Backup Storage Location (BSL) is deleted, backup and Restic repository re #### Breaking changes -Starting in v1.8, Velero will only support Kubernetes v1 CRD meaning that Velero v1.8+ will only run on Kubernetes v1.16+. Before upgrading, make sure you are running a supported Kubernetes version. For more information, see our [compatibility matrix](https://github.com/velero-io/velero#velero-compatibility-matrix). +Starting in v1.8, Velero will only support Kubernetes v1 CRD meaning that Velero v1.8+ will only run on Kubernetes v1.16+. Before upgrading, make sure you are running a supported Kubernetes version. For more information, see our [compatibility matrix](https://github.com/vmware-tanzu/velero#velero-compatibility-matrix). #### Upload Progress Monitoring and Item Snapshotter Item Snapshotter plugin API was merged. This will support both Upload Progress diff --git a/changelogs/CHANGELOG-1.9.md b/changelogs/CHANGELOG-1.9.md index 7472288a5..9f887aaf5 100644 --- a/changelogs/CHANGELOG-1.9.md +++ b/changelogs/CHANGELOG-1.9.md @@ -2,7 +2,7 @@ ### 2022-06-13 ### Download -https://github.com/velero-io/velero/releases/tag/v1.9.0 +https://github.com/vmware-tanzu/velero/releases/tag/v1.9.0 ### Container Image `velero/velero:v1.9.0` @@ -20,7 +20,7 @@ https://velero.io/docs/v1.9/upgrade-to-1.9/ - No VolumeSnapshot will be left in the source namespace of the workload - Report metrics for CSI snapshots -More improvements please refer to [CSI plugin improvement](https://github.com/velero-io/velero/issues?q=is%3Aissue+label%3A%22CSI+plugin+-+GA+-+phase1%22+is%3Aclosed) +More improvements please refer to [CSI plugin improvement](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+label%3A%22CSI+plugin+-+GA+-+phase1%22+is%3Aclosed) With these improvements we'll provide official support for CSI snapshots on AKS/EKS clusters. (with CSI plugin v0.3.0) diff --git a/cmd/velero/velero.go b/cmd/velero/velero.go index 6b150b844..07be4a884 100644 --- a/cmd/velero/velero.go +++ b/cmd/velero/velero.go @@ -22,8 +22,8 @@ import ( "k8s.io/klog/v2" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/velero" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/velero" ) func main() { diff --git a/design/2082-bsl-delete-associated-resources_design.md b/design/2082-bsl-delete-associated-resources_design.md index 907d10bcf..da5ac0bf0 100644 --- a/design/2082-bsl-delete-associated-resources_design.md +++ b/design/2082-bsl-delete-associated-resources_design.md @@ -20,7 +20,7 @@ Update the `velero backup-location delete ` command to delete associat ## Non Goals -[It was suggested](https://github.com/velero-io/velero/issues/2082#issuecomment-827951311) to fix bug #2697 alongside this issue. +[It was suggested](https://github.com/vmware-tanzu/velero/issues/2082#issuecomment-827951311) to fix bug #2697 alongside this issue. However, I think that should be fixed separately because although it is similar (restore objects are not being deleted), it is also quite different. One is adding a command feature update (this issue) and the other is a bug fix and each affect different parts of the code base. @@ -31,7 +31,7 @@ Update the `velero backup-location delete ` command to do the followin - find in the same Velero namespace from which the BSL was deleted the associated backup resources and Restic repositories, called "backups.velero.io" and "resticrepositories.velero.io" respectively - delete the resources found -The above logic will be added to [where BSLs are deleted](https://github.com/velero-io/velero/blob/main/pkg/cmd/cli/backuplocation/delete.go). +The above logic will be added to [where BSLs are deleted](https://github.com/vmware-tanzu/velero/blob/main/pkg/cmd/cli/backuplocation/delete.go). ## Alternative Considered diff --git a/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md b/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md index 2798dc5bd..e1503dba5 100644 --- a/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md +++ b/design/Implemented/Extend-VolumePolicies-to-support-more-actions.md @@ -2,7 +2,7 @@ ## Abstract -Currently, the [VolumePolicies feature](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) which can be used to filter/handle volumes during backup only supports the skip action on matching conditions. Users need more actions to be supported. +Currently, the [VolumePolicies feature](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) which can be used to filter/handle volumes during backup only supports the skip action on matching conditions. Users need more actions to be supported. ## Background @@ -58,17 +58,17 @@ volumePolicies: ``` ## High-Level Design - When the VolumePolicy action is set as `fs-backup` the backup workflow modifications would be: - - We call [backupItem() -> backupItemInternal()](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up - - Here when we encounter [Pod as an item ](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L195) + - We call [backupItem() -> backupItemInternal()](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up + - Here when we encounter [Pod as an item ](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L195) - We will have to modify the backup workflow to account for the `fs-backup` VolumePolicy action - When the VolumePolicy action is set as `snapshot` the backup workflow modifications would be: - - Once again, We call [backupItem() -> backupItemInternal()](https://github.com/velero-io/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up - - Here when we encounter [Persistent Volume as an item](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L253) - - And we call the [takePVSnapshot func](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) + - Once again, We call [backupItem() -> backupItemInternal()](https://github.com/vmware-tanzu/velero/blob/main/pkg/backup/item_backupper.go#L95) on all the items that are to be backed up + - Here when we encounter [Persistent Volume as an item](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L253) + - And we call the [takePVSnapshot func](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) - We need to modify the takePVSnapshot function to account for the `snapshot` VolumePolicy action. - - In case of csi snapshots for PVC objects, these snapshot actions are taken by the velero-plugin-for-csi, we need to modify the [executeActions()](https://github.com/velero-io/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L232) function to account for the `snapshot` VolumePolicy action. + - In case of csi snapshots for PVC objects, these snapshot actions are taken by the velero-plugin-for-csi, we need to modify the [executeActions()](https://github.com/vmware-tanzu/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L232) function to account for the `snapshot` VolumePolicy action. **Note:** `Snapshot` action can either be a native snapshot or a csi snapshot, as is the case with the current flow where velero itself makes the decision based on the backup CR. @@ -80,9 +80,9 @@ volumePolicies: - Else continue with the annotation based legacy approach workflow. - Modifications needed for `snapshot` action: - - In the [takePVSnapshot function](https://github.com/velero-io/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) we will check the PV fits the volume policy criteria and see if the associated action is `snapshot` + - In the [takePVSnapshot function](https://github.com/vmware-tanzu/velero/blob/d4128542590470b204a642ee43311921c11db880/pkg/backup/item_backupper.go#L508) we will check the PV fits the volume policy criteria and see if the associated action is `snapshot` - If it is not snapshot then we skip the further workflow and avoid taking the snapshot of the PV - - Similarly, For csi snapshot of PVC object, we need to do similar changes in [executeAction() function](https://github.com/velero-io/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L348). we will check the PVC fits the volume policy criteria and see if the associated action is `snapshot` via csi plugin + - Similarly, For csi snapshot of PVC object, we need to do similar changes in [executeAction() function](https://github.com/vmware-tanzu/velero/blob/512fe0dabdcb3bbf1ca68a9089056ae549663bcf/pkg/backup/item_backupper.go#L348). we will check the PVC fits the volume policy criteria and see if the associated action is `snapshot` via csi plugin - If it is not snapshot then we skip the csi BIA execute action and avoid taking the snapshot of the PVC by not invoking the csi plugin action for the PVC **Note:** @@ -338,7 +338,7 @@ In the future, we envision the following actions that can be implemented: ## Related to Design -[Handle backup of volumes by resources filters](https://github.com/velero-io/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) +[Handle backup of volumes by resources filters](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/handle-backup-of-volumes-by-resources-filters.md) ## Alternatives Considered Same as the earlier design as this is an extension of the original VolumePolicies design \ No newline at end of file diff --git a/design/Implemented/clean_artifacts_in_csi_flow.md b/design/Implemented/clean_artifacts_in_csi_flow.md index 2f1b18181..2d42bb2a9 100644 --- a/design/Implemented/clean_artifacts_in_csi_flow.md +++ b/design/Implemented/clean_artifacts_in_csi_flow.md @@ -371,4 +371,4 @@ In this design, no new information is added in backup and restore. As a result, ## Open Issues Please notice the CSI snapshot backup and restore mechanism not supporting all file-store-based volume, e.g. Azure Files, EFS or vSphere CNS File Volume. Only block-based volumes are supported. -Refer to [this comment](https://github.com/velero-io/velero/issues/3151#issuecomment-2623507686) for more details. +Refer to [this comment](https://github.com/vmware-tanzu/velero/issues/3151#issuecomment-2623507686) for more details. diff --git a/design/Implemented/cluster-scope-resource-filter.md b/design/Implemented/cluster-scope-resource-filter.md index a5ae5ea75..37267c5ac 100644 --- a/design/Implemented/cluster-scope-resource-filter.md +++ b/design/Implemented/cluster-scope-resource-filter.md @@ -382,7 +382,7 @@ type BackupSpec struct { ``` ## Alternatives Considered -Proposal from Jibu Data [Issue 5120](https://github.com/velero-io/velero/issues/5120#issue-1304534563) +Proposal from Jibu Data [Issue 5120](https://github.com/vmware-tanzu/velero/issues/5120#issue-1304534563) ## Security Considerations No security impact. @@ -399,4 +399,4 @@ Plan to deprecate `IncludedResources`, `ExcludedResources` and `IncludeClusterRe ## Open Issues `LabelSelector/OrLabelSelectors` apply to namespace-scoped resources. It may be reasonable to make them also working on cluster-scoped resources. -An issue is created to trace this topic [resource label selector not work for cluster-scoped resources](https://github.com/velero-io/velero/issues/5787) +An issue is created to trace this topic [resource label selector not work for cluster-scoped resources](https://github.com/vmware-tanzu/velero/issues/5787) diff --git a/design/Implemented/custom-ca-support.md b/design/Implemented/custom-ca-support.md index b1a3936ad..05bf9e769 100644 --- a/design/Implemented/custom-ca-support.md +++ b/design/Implemented/custom-ca-support.md @@ -73,8 +73,8 @@ This same approach can be taken for CA bundles. The bundle can be stored in a secret which is referenced on the BSL and written to a temp file prior to invoking Restic. -[1](https://github.com/velero-io/velero/blob/main/pkg/restic/repository_manager.go#L238-L245) -[2](https://github.com/velero-io/velero/blob/main/pkg/restic/common.go#L168-L203) +[1](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/repository_manager.go#L238-L245) +[2](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/common.go#L168-L203) ## Detailed Design @@ -126,7 +126,7 @@ would look like: $ velero client config set cacert PATH ``` -[1]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L135 -[2]: https://github.com/velero-io/velero/blob/main/pkg/restic/command.go#L47 +[1]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L135 +[2]: https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/command.go#L47 [3]: https://github.com/restic/restic/blob/main/internal/backend/http_transport.go#L81 -[4]: https://github.com/velero-io/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L154 +[4]: https://github.com/vmware-tanzu/velero-plugin-for-aws/blob/main/velero-plugin-for-aws/object_store.go#L154 diff --git a/design/Implemented/existing-resource-policy_design.md b/design/Implemented/existing-resource-policy_design.md index 0c4bd84d3..7d119b8e7 100644 --- a/design/Implemented/existing-resource-policy_design.md +++ b/design/Implemented/existing-resource-policy_design.md @@ -8,12 +8,12 @@ As of Today, Velero will skip over the restoration of resources that already exi - Fetches the `service` from the cluster - If the `service` exists then: - Checks whether the `service` instance in the cluster is equal to the `service` instance present in backup - - If not equal then skips the restore of the `service` and adds a restore warning (except for [ServiceAccount objects](https://github.com/velero-io/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/restore/restore.go#L1246)) + - If not equal then skips the restore of the `service` and adds a restore warning (except for [ServiceAccount objects](https://github.com/vmware-tanzu/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/restore/restore.go#L1246)) - If equal then skips the restore of the `service` and mentions that the restore of resource `service` is skipped in logs It is desired to add the functionality to specify whether or not to overwrite the instance of resource `service` in cluster with the one present in backup during the restore process. -Related issue: https://github.com/velero-io/velero/issues/4066 +Related issue: https://github.com/vmware-tanzu/velero/issues/4066 ## Goals - Add support for `ExistingResourcePolicy` to restore API for Kubernetes resources. @@ -31,7 +31,7 @@ Related issue: https://github.com/velero-io/velero/issues/4066 ### A. Production Cluster - Backup Cluster: Let's say you have a Backup Cluster which is identical to the Production Cluster. After some operations/usage/time the Production Cluster had changed itself, there might be new deployments, some secrets might have been updated. Now, this means that the Backup cluster will no longer be identical to the Production Cluster. In order to keep the Backup Cluster up to date/identical to the Production Cluster with respect to Kubernetes resources except PV data we would like to use Velero for scheduling new backups which would in turn help us update the Backup Cluster via Velero restore. -Reference: https://github.com/velero-io/velero/issues/4066#issuecomment-954320686 +Reference: https://github.com/vmware-tanzu/velero/issues/4066#issuecomment-954320686 ### B. Help identify resource delta: Here delta resources mean the resources restored by a previous backup, but they are no longer in the latest backup. Let's follow a sequence of steps to understand this scenario: @@ -43,7 +43,7 @@ Here delta resources mean the resources restored by a previous backup, but they - So the Delta here is (|Cluster B - Backup2|), Delete P1 and Update P2. - During Restore time we would want the Restore to help us identify this resource delta. -Reference: https://github.com/velero-io/velero/pull/4613#issuecomment-1027260446 +Reference: https://github.com/vmware-tanzu/velero/pull/4613#issuecomment-1027260446 ## High-Level Design ### Approach 1: Add a new spec field `existingResourcePolicy` to the Restore API @@ -238,7 +238,7 @@ IncludedResources []string } ``` -The restore workflow changes will be done [here](https://github.com/velero-io/velero/blob/b40bbda2d62af2f35d1406b9af4d387d4b396839/pkg/restore/restore.go#L1245) +The restore workflow changes will be done [here](https://github.com/vmware-tanzu/velero/blob/b40bbda2d62af2f35d1406b9af4d387d4b396839/pkg/restore/restore.go#L1245) ### CLI changes for Approach 1 We would introduce a new CLI flag called `existing-resource-policy` of string type. This flag would be used to accept the diff --git a/design/Implemented/general-progress-monitoring.md b/design/Implemented/general-progress-monitoring.md index 6f64a0d4b..35c2ed2ae 100644 --- a/design/Implemented/general-progress-monitoring.md +++ b/design/Implemented/general-progress-monitoring.md @@ -526,24 +526,24 @@ updates. Here is a list of some of these items: 1. Consts for the "Uploading" and "UploadingPartiallyFailed" phases have already been defined. These will need to be removed when the "WaitingForPluginOperations" and "WaitingForPluginOperationsPartiallyFailed" phases are defined. - - https://github.com/velero-io/velero/pull/3805 + - https://github.com/vmware-tanzu/velero/pull/3805 1. Remove the ItemSnapshotter plugin APIs (and related code) since the revised design will reuse VolumeSnapshotter and BackupItemAction plugins. - - https://github.com/velero-io/velero/pull/4077 - - https://github.com/velero-io/velero/pull/4417 + - https://github.com/vmware-tanzu/velero/pull/4077 + - https://github.com/vmware-tanzu/velero/pull/4417 1. UploadProgressFeatureFlag shouldn't be needed anymore. The current design won't really need a feature flag here -- the new features will be added to V2 of the VolumeSnapshotter, BackupItemAction, and RestoreItemAction plugins, and it will only be used if there are plugins which return operation IDs. - - https://github.com/velero-io/velero/pull/4416 + - https://github.com/vmware-tanzu/velero/pull/4416 1. Adds -itemsnapshots.gz file to backup (when provided) -- this is still part of the revised design, so it should stay. - - https://github.com/velero-io/velero/pull/4429 + - https://github.com/vmware-tanzu/velero/pull/4429 1. Upload Progress Monitoring and Item Snapshotter basic support: This PR is not yet merged, so nothing will need to be reverted. While the implementation here will be useful in informing the implementation of the new design, several things have changed in the design proposal since the PR was written. - - https://github.com/velero-io/velero/pull/4467 + - https://github.com/vmware-tanzu/velero/pull/4467 # Implementation tasks diff --git a/design/Implemented/include-exclude-in-resource-policy.md b/design/Implemented/include-exclude-in-resource-policy.md index ead936ddb..ddba2a874 100644 --- a/design/Implemented/include-exclude-in-resource-policy.md +++ b/design/Implemented/include-exclude-in-resource-policy.md @@ -4,7 +4,7 @@ This enhancement will allow the user to set include and exclude filters for reso these filters are reusable and the user will not need to set them each time they create a backup. ## Background -As mentioned in issue [#8610](https://github.com/velero-io/velero/issues/8610). When there's a long list of resources +As mentioned in issue [#8610](https://github.com/vmware-tanzu/velero/issues/8610). When there's a long list of resources to include or exclude in a backup, it can be cumbersome to set them each time a backup is created. There's a requirement to set these filters in a separate data structure so that they can be reused in multiple backups. diff --git a/design/Implemented/json-substitution-action-design.md b/design/Implemented/json-substitution-action-design.md index f48834e76..102503beb 100644 --- a/design/Implemented/json-substitution-action-design.md +++ b/design/Implemented/json-substitution-action-design.md @@ -150,7 +150,7 @@ Compatibility with existing StorageClass mapping RestoreItemAction and similar p ## Implementation - Changes in Restore CRD. Add a new field to the RestoreSpec to reference the configmap. -- One example of where code will be modified: https://github.com/velero-io/velero/blob/eeee4e06d209df7f08bfabda326b27aaf0054759/pkg/restore/restore.go#L1266 On the obj before Creation, we can apply the conditions to check if the resource is filtered out using given parameters. Then using JsonPatch provided, we can update the resource. +- One example of where code will be modified: https://github.com/vmware-tanzu/velero/blob/eeee4e06d209df7f08bfabda326b27aaf0054759/pkg/restore/restore.go#L1266 On the obj before Creation, we can apply the conditions to check if the resource is filtered out using given parameters. Then using JsonPatch provided, we can update the resource. - For Jsonpatch - https://github.com/evanphx/json-patch library is used. - JSON Patch RFC https://datatracker.ietf.org/doc/html/rfc6902 diff --git a/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md b/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md index a5f34317a..a8127bc49 100644 --- a/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md +++ b/design/Implemented/merge-patch-and-strategic-in-resource-modifier.md @@ -49,7 +49,7 @@ This proposal is to add support for JSON Merge Patch and Strategic Merge Patch i - New fields `MergePatches` and `StrategicPatches` will be added to the `ResourceModifierRule` struct to support all three patch types. - Only one of the three patch types can be specified in a single `ResourceModifierRule`. - Add wildcard support for `groupResource` in `conditions` struct. -- The workflow to create Resource Modifier ConfigMap and reference it in RestoreSpec will remain the same as described in document [Resource Modifiers](https://github.com/velero-io/velero/blob/main/site/content/docs/main/restore-resource-modifiers.md). +- The workflow to create Resource Modifier ConfigMap and reference it in RestoreSpec will remain the same as described in document [Resource Modifiers](https://github.com/vmware-tanzu/velero/blob/main/site/content/docs/main/restore-resource-modifiers.md). ### How to choose the right patch type - [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) is a naively simple format, with limited usability. Probably it is a good choice if you are building something small, with very simple JSON Schema. @@ -187,7 +187,7 @@ Compatible with current Resource Modifiers. ## Future enhancements - add a Velero subcommand to generate/validate the patchData for Strategic Merge Patch and JSON Merge Patch. -- add jq support for more complex conditions or patches, to meet the situations that the current conditions or patches can not handle. like [this issue](https://github.com/velero-io/velero/issues/6344) +- add jq support for more complex conditions or patches, to meet the situations that the current conditions or patches can not handle. like [this issue](https://github.com/vmware-tanzu/velero/issues/6344) ## Open Issues N/A diff --git a/design/Implemented/move-gh-org.md b/design/Implemented/move-gh-org.md index 0a2102257..0d76a748a 100644 --- a/design/Implemented/move-gh-org.md +++ b/design/Implemented/move-gh-org.md @@ -17,7 +17,7 @@ Currently, the Velero repository sits under the Heptio GitHub organization. With #### Pre move - [ ] PR: Blog post communicating the move. https://github.com/heptio/velero/issues/1841. Who: TBD. -- [ ] PR: Find/replace in all Go, script, yaml, documentation, and website files: `github.com/heptio/velero -> github.com/velero-io/velero`. Who: a Velero developer; TBD +- [ ] PR: Find/replace in all Go, script, yaml, documentation, and website files: `github.com/heptio/velero -> github.com/vmware-tanzu/velero`. Who: a Velero developer; TBD - [ ] PR: Update website with the correct GH links. Who: a Velero developer; TBD - [ ] PR: Change deployment and grpc-push scripts with the new location path. Who: a Velero developer; TBD - [ ] Delete branches not to be carried over (https://github.com/heptio/velero/branches/all). Who: Any of the current repo owners; TBD @@ -32,7 +32,7 @@ Currently, the Velero repository sits under the Heptio GitHub organization. With #### Post move -- [ ] Each individual developer should point their origin to the new location: `git remote set-url origin git@github.com:velero-io/velero.git` +- [ ] Each individual developer should point their origin to the new location: `git remote set-url origin git@github.com:vmware-tanzu/velero.git` - [ ] Transfer ZenHub. Who: Any of the new repo owners; TBD - [ ] Update Netlify deploy settings. Any of the new repo owners; TBD - [ ] GH app: Netlify integration. Who: Any of the new repo owners; TBD diff --git a/design/Implemented/multiple-csi-volumesnapshotclass-support.md b/design/Implemented/multiple-csi-volumesnapshotclass-support.md index a1fa1557e..089557193 100644 --- a/design/Implemented/multiple-csi-volumesnapshotclass-support.md +++ b/design/Implemented/multiple-csi-volumesnapshotclass-support.md @@ -95,7 +95,7 @@ The Velero CSI plugin chooses the VolumeSnapshotClass in the cluster that has th We can add support for - velero backup create my-backup --annotations "velero.io/csi:csi.cloud.disk.driver=csi-diskdriver-snapclass" ### Stage 2 Approach -The above annotations route is to get started and for initial design closure/ implementation, north star is to either introduce CSI specific fields (considering that CSI might be a very core part of velero going forward) in the backup/restore CR OR leverage the pluginInputs field as being tracked in: https://github.com/velero-io/velero/pull/5981 +The above annotations route is to get started and for initial design closure/ implementation, north star is to either introduce CSI specific fields (considering that CSI might be a very core part of velero going forward) in the backup/restore CR OR leverage the pluginInputs field as being tracked in: https://github.com/vmware-tanzu/velero/pull/5981 Refer section Alternatives 2. **Through generic property bag in the velero contracts**: in the design doc for more details on the pluginInputs field. diff --git a/design/Implemented/multiple-label-selectors_design.md b/design/Implemented/multiple-label-selectors_design.md index d4d9e144b..9c301f3b5 100644 --- a/design/Implemented/multiple-label-selectors_design.md +++ b/design/Implemented/multiple-label-selectors_design.md @@ -14,7 +14,7 @@ backup for resources consisting of a label from a set of labels (label1 OR label create multiple backups per label rule. It would be really useful if Velero Backup API could respect a set of labels (OR Rule) for a single backup request. -Related Issue: https://github.com/velero-io/velero/issues/1508 +Related Issue: https://github.com/vmware-tanzu/velero/issues/1508 ## Goals - Enable support for backing up resources based on multiple labels (OR Logic) in a single backup config. @@ -130,9 +130,9 @@ OrLabelSelectors []\*metav1.LabelSelector ``` The logic to collect resources to be backed up for a particular backup will be updated in the `backup/item_collector.go` -around [here](https://github.com/velero-io/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/backup/item_collector.go#L294). +around [here](https://github.com/vmware-tanzu/velero/blob/574baeb3c920f97b47985ec3957debdc70bcd5f8/pkg/backup/item_collector.go#L294). -And for filtering the resources to be restored, the changes will go [here](https://github.com/velero-io/velero/blob/d1063bda7e513150fd9ae09c3c3c8b1115cb1965/pkg/restore/restore.go#L1769) +And for filtering the resources to be restored, the changes will go [here](https://github.com/vmware-tanzu/velero/blob/d1063bda7e513150fd9ae09c3c3c8b1115cb1965/pkg/restore/restore.go#L1769) **Note:** - This feature will not be exposed via Velero CLI. \ No newline at end of file diff --git a/design/Implemented/plugin-backup-and-restore-progress-design.md b/design/Implemented/plugin-backup-and-restore-progress-design.md index f3eefd0b5..46544f01b 100644 --- a/design/Implemented/plugin-backup-and-restore-progress-design.md +++ b/design/Implemented/plugin-backup-and-restore-progress-design.md @@ -154,7 +154,7 @@ In order to know the CR created for the particular backup of a volume, Velero ad - `velero.io/pv-name` with value as volume that is undergoing backup Backup name being unique won't cause issues like duplicates in identifying the CR. -Labels will be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). +Labels will be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). If Plugin supports showing progress of the operation it is performing, it does following: - finds the VolumePluginBackup CR related to this backup operation by using `tags` passed in CreateSnapshot call @@ -281,7 +281,7 @@ In order to know the CR created for the particular restore of a volume, Velero a - `velero.io/snapshot-id` with value as snapshot id that need to be restored - `velero.io/provider` with value as `Provider` in `VolumeSnapshotLocation` -Labels will be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). +Labels will be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). Plugin will be able to identify CR by using snapshotID that it received as parameter of CreateVolumeFromSnapshot API, and plugin's Provider name. It updates the progress of restore operation regularly if plugin supports feature of showing progress. @@ -376,7 +376,7 @@ In order to know the CR created for the particular backup of a volume, volume sn Backup name being unique won't cause issues like duplicates in identifying the CR. -Plugin need to sanitize the value that can be set for above labels. Label need to be set with the value returned from `GetValidName` function. (https://github.com/velero-io/velero/blob/main/pkg/label/label.go#L35). +Plugin need to sanitize the value that can be set for above labels. Label need to be set with the value returned from `GetValidName` function. (https://github.com/vmware-tanzu/velero/blob/main/pkg/label/label.go#L35). Though no restrictions are required on the name of CR, as a general practice, volume snapshotter can name this CR with the value same as return value of CreateSnapshot. diff --git a/design/Implemented/plugin-versioning.md b/design/Implemented/plugin-versioning.md index 99e3eaae0..43b236f96 100644 --- a/design/Implemented/plugin-versioning.md +++ b/design/Implemented/plugin-versioning.md @@ -92,7 +92,7 @@ type ObjectStore interface { If a method is being added to the `ObjectStore` API, a file would be added to `pkg/plugin/velero/objectstore/v2/` and may contain a new API definition as follows: ``` -import "github.com/velero-io/velero/pkg/plugin/velero/objectstore/v1" +import "github.com/vmware-tanzu/velero/pkg/plugin/velero/objectstore/v1" type ObjectStore interface { // Import all the methods from the previous version of the API if they are to be included as is @@ -147,15 +147,15 @@ The message definitions can be shared however, so these could be extracted from ### Plugin Framework To allow plugins to register which versions of the API they implement, the plugin framework will need to be adapted to accept new versions. -Currently, the plugin manager stores a [`map[string]RestartableProcess`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L69), where the string key is the binary name for the plugin process (e.g. "velero-plugin-for-aws"). -Each `RestartableProcess` contains a [`map[kindAndName]interface{}`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/restartable_process.go#L60) which represents each of the unique plugin implementations provided by that binary. -[`kindAndName`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/registry.go#L42) is a struct which combines the plugin kind (`ObjectStore`, `VolumeSnapshotter`) and the plugin name ("velero.io/aws", "velero.io/azure"). +Currently, the plugin manager stores a [`map[string]RestartableProcess`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L69), where the string key is the binary name for the plugin process (e.g. "velero-plugin-for-aws"). +Each `RestartableProcess` contains a [`map[kindAndName]interface{}`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/restartable_process.go#L60) which represents each of the unique plugin implementations provided by that binary. +[`kindAndName`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/registry.go#L42) is a struct which combines the plugin kind (`ObjectStore`, `VolumeSnapshotter`) and the plugin name ("velero.io/aws", "velero.io/azure"). Each plugin version registration must be unique (to allow for multiple versions to be implemented within the same plugin binary). This will be achieved by adding a specific registration method for each version to the Server interface in the plugin framework. For example, if adding a V2 `RestoreItemAction` plugin, the Server interface would be modified to add the `RegisterRestoreItemActionV2` method. -This would require [adding a new plugin Kind const](https://github.com/velero-io/velero/blob/main/pkg/plugin/framework/plugin_kinds.go#L28-L46) to represent the new plugin version, e.g. `PluginKindRestoreItemActionV2`. -It also requires the creation of a new implementation of the go-plugin interface ([example](https://github.com/velero-io/velero/blob/main/pkg/plugin/framework/object_store.go)) to support that version and use the generated gRPC code from the proto definition (including a client and server implementation). +This would require [adding a new plugin Kind const](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/framework/plugin_kinds.go#L28-L46) to represent the new plugin version, e.g. `PluginKindRestoreItemActionV2`. +It also requires the creation of a new implementation of the go-plugin interface ([example](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/framework/object_store.go)) to support that version and use the generated gRPC code from the proto definition (including a client and server implementation). The Server will also need to be adapted to recognize this new plugin Kind and to serve the new implementation. Existing plugin Kind consts and registration methods will be left unchanged and will correspond to the current version of the plugin APIs (assumed to be v1). @@ -241,7 +241,7 @@ In cases where the methods signatures remain the same, the adaptation layer will Examples where an adaptation may be safe: - A method signature is being changed to add a new parameter but the parameter could be optional (for example, adding a context parameter). The adaptation could call through to the method provided in the previous version but omit the parameter. - A method signature is being changed to remove a parameter, but it is safe to pass a default value to the previous version. The adaptation could call through to the method provided in the previous version but use a default value for the parameter. -- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/velero-io/velero/blob/main/design/Implemented/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed. +- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed. - A method is being deleted as it is no longer used. The adaptation would call through to any methods which are still included but would omit the deleted method in the adaptation. Examples where an adaptation may not be safe: diff --git a/design/Implemented/pv-cloning.md b/design/Implemented/pv-cloning.md index 8140a0641..f840bda84 100644 --- a/design/Implemented/pv-cloning.md +++ b/design/Implemented/pv-cloning.md @@ -32,11 +32,11 @@ It will also update the `spec.volumeName` of the related persistent volume claim ## Detailed Design -In `pkg/restore/restore.go`, around [line 872](https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L872), Velero has special-case code for persistent volumes. +In `pkg/restore/restore.go`, around [line 872](https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L872), Velero has special-case code for persistent volumes. This code will be updated to check for the two preconditions described in the previous section. If the preconditions are met, the object will be given a new name. The persistent volume will also be annotated with the original name, e.g. `velero.io/original-pv-name=NAME`. -Importantly, the name change will occur **before** [line 890](https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L890), where Velero checks to see if it should restore the persistent volume. +Importantly, the name change will occur **before** [line 890](https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L890), where Velero checks to see if it should restore the persistent volume. Additionally, the old and new persistent volume names will be recorded in a new field that will be added to the `context` struct, `renamedPVs map[string]string`. In the special-case code for persistent volume claims starting on [line 987](https://github.com/heptio/velero/blob/main/pkg/restore/restore.go#L987), Velero will check to see if the claimed persistent volume has been renamed by looking in `ctx.renamedPVs`. diff --git a/design/Implemented/pv_backup_info.md b/design/Implemented/pv_backup_info.md index ff080a797..90cd998cb 100644 --- a/design/Implemented/pv_backup_info.md +++ b/design/Implemented/pv_backup_info.md @@ -9,7 +9,7 @@ This new additional metadata file is needed when: * Retrieve the PV's snapshot information for backup. ## Background -There is already a [PR](https://github.com/velero-io/velero/pull/6496) to track the skipped PVC in the backup. This design will depend on it and go further to get a summary of PVC and PV information, then persist into a metadata file in the backup repository. +There is already a [PR](https://github.com/vmware-tanzu/velero/pull/6496) to track the skipped PVC in the backup. This design will depend on it and go further to get a summary of PVC and PV information, then persist into a metadata file in the backup repository. In the restore process, the Velero server needs to decide how the PV resource should be restored according to how the PV is backed up. The current logic is to check whether it's backed up by Velero-native snapshot, by file-system backup, or having `DeletionPolicy` set as `Delete`. @@ -28,7 +28,7 @@ Another thing that needs noticing is when describing the backup, there is no gen ## High-Level Design Create _backup-name_-volumes-info.json metadata file in the backup's repository. This file will be encoded to contain all the PVC and PV information included in the backup. The information covers whether the PV or PVC's data is skipped during backup, how its data is backed up, and the backed-up detail information. -Please notice that the new metadata file includes all skipped volume information. This is used to address [the second phase needs of skipped volumes information](https://github.com/velero-io/velero/issues/5834#issuecomment-1526624211). +Please notice that the new metadata file includes all skipped volume information. This is used to address [the second phase needs of skipped volumes information](https://github.com/vmware-tanzu/velero/issues/5834#issuecomment-1526624211). The `restoreItem` function can decode the _backup-name_-volumes-info.json file to determine how to handle the PV resource. @@ -169,13 +169,13 @@ After introducing the VolumeInfo array, the following logic will be added. _backup-name_-volumes-info.json file is deleted during backup deletion. ## Alternatives Considered -The restore process needs more information about how the PVs are backed up to determine whether this PV should be restored. The released branches also need a similar function, but backporting a new feature into previous releases may not be a good idea, so according to [Anshul Ahuja's suggestion](https://github.com/velero-io/velero/issues/6595#issuecomment-1731081580), adding more cases here to support checking PV backed-up by CSI plugin and CSI snapshot data mover: https://github.com/velero-io/velero/blob/5ff5073cc3f364bafcfbd26755e2a92af68ba180/pkg/restore/restore.go#L1206-L1324. +The restore process needs more information about how the PVs are backed up to determine whether this PV should be restored. The released branches also need a similar function, but backporting a new feature into previous releases may not be a good idea, so according to [Anshul Ahuja's suggestion](https://github.com/vmware-tanzu/velero/issues/6595#issuecomment-1731081580), adding more cases here to support checking PV backed-up by CSI plugin and CSI snapshot data mover: https://github.com/vmware-tanzu/velero/blob/5ff5073cc3f364bafcfbd26755e2a92af68ba180/pkg/restore/restore.go#L1206-L1324. ## Security Considerations There should be no security impact introduced by this design. ## Compatibility -After this design is implemented, there should be no impact on the existing [skipped PVC summary feature](https://github.com/velero-io/velero/pull/6496). +After this design is implemented, there should be no impact on the existing [skipped PVC summary feature](https://github.com/vmware-tanzu/velero/pull/6496). To support older version backup, which doesn't have the VolumeInfo metadata file, the old logic, which is checking the Velero native snapshots list, PodVolumeBackup list, and PVC DeletionPolicy, is still kept, and supporting CSI snapshots and snapshot data mover logic will be added too. diff --git a/design/Implemented/pv_restore_info.md b/design/Implemented/pv_restore_info.md index 91df863af..d2e49655c 100644 --- a/design/Implemented/pv_restore_info.md +++ b/design/Implemented/pv_restore_info.md @@ -139,5 +139,5 @@ The data structures referenced by volume info is shared between both restore and we must make sure there will only be incremental changes to the metadata, such that no break change will be introduced to the client. ## Open Issues -https://github.com/velero-io/velero/issues/7546 -https://github.com/velero-io/velero/issues/6478 +https://github.com/vmware-tanzu/velero/issues/7546 +https://github.com/vmware-tanzu/velero/issues/6478 diff --git a/design/Implemented/repo_maintenance_job_config.md b/design/Implemented/repo_maintenance_job_config.md index cda8a9a5c..195b5b9dc 100644 --- a/design/Implemented/repo_maintenance_job_config.md +++ b/design/Implemented/repo_maintenance_job_config.md @@ -20,7 +20,7 @@ This design reuses the data structure introduced by design [Velero Generic Data - Let user can choose repository maintenance Job running on which nodes. ## Non Goals -- There was an [issue](https://github.com/velero-io/velero/issues/7911) to require the whole Job's PodSpec should be configurable. That's not in the scope of this design. +- There was an [issue](https://github.com/vmware-tanzu/velero/issues/7911) to require the whole Job's PodSpec should be configurable. That's not in the scope of this design. - Please notice this new configuration is dedicated for the repository maintenance. Repository itself configuration is not covered. @@ -43,7 +43,7 @@ Propose to deprecate the `velero server` parameters `--maintenance-job-cpu-reque That means those parameters will be deleted in release-1.17. After deletion, those resources-related parameters are replaced by the ConfigMap specified by `velero server` CLI's parameter `--repo-maintenance-job-configmap`. `--keep-latest-maintenance-jobs` is deleted from `velero server` CLI. It turns into a non-configurable internal parameter, and its value is 3. -Please check [issue 7923](https://github.com/velero-io/velero/issues/7923) for more information why deleting this parameter. +Please check [issue 7923](https://github.com/vmware-tanzu/velero/issues/7923) for more information why deleting this parameter. ## Design This design introduces a new ConfigMap specified by `velero server` CLI parameter `--repo-maintenance-job-configmap` as the source of the repository maintenance job configuration. The specified ConfigMap is read from the namespace where Velero is installed. @@ -92,7 +92,7 @@ The other keys in the map is the combination of three elements of a BackupReposi * The BackupRepository referenced BackupStorageLocation's name. * The BackupRepository's type. Possible values are `kopia` and `restic`. -Those three keys can identify a [unique BackupRepository](https://github.com/velero-io/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/repository/backup_repo_op.go#L32-L37). +Those three keys can identify a [unique BackupRepository](https://github.com/vmware-tanzu/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/repository/backup_repo_op.go#L32-L37). If there is a key match with BackupRepository, the key's value is applied to the BackupRepository's maintenance jobs. By this way, it's possible to let user configure before the BackupRepository is created. diff --git a/design/Implemented/resource-status-restore.md b/design/Implemented/resource-status-restore.md index 9d394c1b8..f57e86a4f 100644 --- a/design/Implemented/resource-status-restore.md +++ b/design/Implemented/resource-status-restore.md @@ -76,7 +76,7 @@ metadata: We are targeting the implementation of this design for Velero 1.16 release. -Current restoreStatus logic resides here: https://github.com/velero-io/velero/blob/32a8c62920ad96c70f1465252c0197b83d5fa6b6/pkg/restore/restore.go#L1652 +Current restoreStatus logic resides here: https://github.com/vmware-tanzu/velero/blob/32a8c62920ad96c70f1465252c0197b83d5fa6b6/pkg/restore/restore.go#L1652 The modified logic would look somewhat like: diff --git a/design/Implemented/restore-finalizing-phase_design.md b/design/Implemented/restore-finalizing-phase_design.md index 7e84a2e61..0d4d0170d 100644 --- a/design/Implemented/restore-finalizing-phase_design.md +++ b/design/Implemented/restore-finalizing-phase_design.md @@ -9,7 +9,7 @@ Currently, the restore process enters a terminal phase once all item restoration To address this, a new finalization phase should be added to the existing restore workflow. in this phase, all plugin operations and item restoration has been fully completed, which provides a clean opportunity to perform any wrap-up work before termination, improving the overall restore process. Wrap-up tasks in Velero can serve several purposes: -- Post-restore modification - Velero can modify the restored data that was temporarily changed for some purpose but required to be changed back finally or data that was newly created but missing some information. For example, [issue6435](https://github.com/velero-io/velero/issues/6435) indicates that some custom settings(like labels, reclaim policy) on restored PVs was lost because those restored PVs was newly dynamically provisioned. Velero can address it by patching the PVs' custom settings back in the finalization phase. +- Post-restore modification - Velero can modify the restored data that was temporarily changed for some purpose but required to be changed back finally or data that was newly created but missing some information. For example, [issue6435](https://github.com/vmware-tanzu/velero/issues/6435) indicates that some custom settings(like labels, reclaim policy) on restored PVs was lost because those restored PVs was newly dynamically provisioned. Velero can address it by patching the PVs' custom settings back in the finalization phase. - Clean up unused data - Velero can identify and delete any data that are no longer needed after a successful restore in the finalization phase. - Post-restore validation - Velero can validate the state of restored data and report any errors to help users locate the issue in the finalization phase. diff --git a/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md b/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md index 65891a898..e5580f948 100644 --- a/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md +++ b/design/Implemented/restore-with-EnableAPIGroupVersions-feature.md @@ -8,7 +8,7 @@ This document proposes a solution to select an API group version to restore from ## Background -It is possible that between the time a backup has been made and a restore occurs that the target Kubernetes version has incremented more than one version. In such a case where at least a versions of Kubernetes was skipped, the preferred source cluster's API group versions for resources may no longer be supported by the target cluster. With [PR#2373](https://github.com/velero-io/velero/pull/2373), all supported API group versions were backed up if the EnableAPIGroupVersions feature flag was set for Velero. The next step (outlined by this design proposal) will be to see if any of the backed up versions are supported in the target cluster and if so, choose one to restore for each backed up resource. +It is possible that between the time a backup has been made and a restore occurs that the target Kubernetes version has incremented more than one version. In such a case where at least a versions of Kubernetes was skipped, the preferred source cluster's API group versions for resources may no longer be supported by the target cluster. With [PR#2373](https://github.com/vmware-tanzu/velero/pull/2373), all supported API group versions were backed up if the EnableAPIGroupVersions feature flag was set for Velero. The next step (outlined by this design proposal) will be to see if any of the backed up versions are supported in the target cluster and if so, choose one to restore for each backed up resource. ## Goals @@ -50,19 +50,19 @@ There are six objectives to achieve the above stated goals: ### Objective 1: Determine if the APIGroupVersionsFeatureFlag is enabled and Backup Objects use Status.FormatVersion 1.1.0 -For restore to be able to choose from multiple supported backed up versions, the feature flag must have been enabled during the restore processes. Backup objects must also have [Status.FormatVersion == "1.1.0"](https://github.com/velero-io/velero/blob/a1e182e723a8c5f6d4175d8db2361233a94d2502/pkg/backup/backup.go#L58). +For restore to be able to choose from multiple supported backed up versions, the feature flag must have been enabled during the restore processes. Backup objects must also have [Status.FormatVersion == "1.1.0"](https://github.com/vmware-tanzu/velero/blob/a1e182e723a8c5f6d4175d8db2361233a94d2502/pkg/backup/backup.go#L58). The reason for checking for the feature flag during restore is to ensure the user would like to restore a version that might not be the source cluster preferred version. This check is done via `features.IsEnabled(velerov1api.APIGroupVersionsFeatureFlag)`. The reason for checking `Status.FormatVersion` is to ensure the changes made by this proposed design is backward compatible. Only with Velero version 1.4 and forward was Format Version 1.1.0 used to structure the backup directories. Format Version 1.1.0 is required for the restore process proposed in this design doc to work. Before v1.4, the backed up files were in a directory structure that will not be recognized by the proposed code changes. In this case, restore should not attempt to restore from multiple versions as they will not exist. -The [`Status.FormatVersion`](https://github.com/velero-io/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/apis/velero/v1/backup.go#L235) is stored in a `restoreContext` struct field called [`backup`](https://github.com/velero-io/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/restore/restore.go#L229). The full chain is `ctx.backup.Status.FormatVersion`. +The [`Status.FormatVersion`](https://github.com/vmware-tanzu/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/apis/velero/v1/backup.go#L235) is stored in a `restoreContext` struct field called [`backup`](https://github.com/vmware-tanzu/velero/blob/6808acd92e30848056a21faf373af03ddb8a3b71/pkg/restore/restore.go#L229). The full chain is `ctx.backup.Status.FormatVersion`. The above two checks can be done inside a new method on the `*restoreContext` object with the method signature `meetsAPIGVRestoreReqs() bool`. This method can remain in the `restore` package, but for organizational purposes, it can be moved to a file called `prioritize_group_version.go`. ### Objective 2: List the backed up API group versions -Currently, in `pkg/restore/restore.go`, in the `execute(...)` method, around [line 363](https://github.com/velero-io/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L363), the resources and their backed up items are saved in a map called `backupResources`. +Currently, in `pkg/restore/restore.go`, in the `execute(...)` method, around [line 363](https://github.com/vmware-tanzu/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L363), the resources and their backed up items are saved in a map called `backupResources`. At this point, the feature flag and format versions can be checked (described in Objective #1). If the requirements are met, the `backedupResources` map can be sent to a method (to be created) with the signature `ctx.chooseAPIVersionsToRestore(backupResources)`. The `ctx` object has the type `*restore.Context`. @@ -158,7 +158,7 @@ To see example cases with version priorities, see a blog post written by Rafael ### Objective 6: Modify the paths to the backup files in the tarball -The method doing the bulk of the restoration work is `ctx.restoreResource(...)`. Inside this method, around [line 714](https://github.com/velero-io/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L714) in `pkg/restore/restore.go`, the path to backup json file for the item being restored is set. +The method doing the bulk of the restoration work is `ctx.restoreResource(...)`. Inside this method, around [line 714](https://github.com/vmware-tanzu/velero/blob/7a103b9eda878769018386ecae78da4e4f8dde83/pkg/restore/restore.go#L714) in `pkg/restore/restore.go`, the path to backup json file for the item being restored is set. After the groupResource is instantiated at pkg/restore/restore.go:733, and before the `for` loop that ranges through the `items`, the `ctx.chosenGRVsToRestore` map can be checked. If the groupResource exists in the map, the path saved to `resource` variable can be updated. diff --git a/design/Implemented/retry-patching-configuration_design.md b/design/Implemented/retry-patching-configuration_design.md index 0c2296774..5975db6dd 100644 --- a/design/Implemented/retry-patching-configuration_design.md +++ b/design/Implemented/retry-patching-configuration_design.md @@ -7,7 +7,7 @@ If a patch call fails to update status to completion, it should be retried up to This design proposes a way to configure timeout for this retry time limit. ## Background -Original Issue: https://github.com/velero-io/velero/issues/7207 +Original Issue: https://github.com/vmware-tanzu/velero/issues/7207 Velero was performing a restore when the API server was rolling out to a new version. It had trouble connecting to the API server, but eventually, the restore was successful. @@ -17,7 +17,7 @@ After the connection was restored, it didn't attempt to update, causing the rest This can lead to incorrect decisions for other components that rely on the backup/restore CR status to determine completion. ## Goals -- Make timeout configurable for retry patching by reusing existing [`--resource-timeout` server flag](https://github.com/velero-io/velero/blob/d9ca14747925630664c9e4f85a682b5fc356806d/pkg/cmd/server/server.go#L245) +- Make timeout configurable for retry patching by reusing existing [`--resource-timeout` server flag](https://github.com/vmware-tanzu/velero/blob/d9ca14747925630664c9e4f85a682b5fc356806d/pkg/cmd/server/server.go#L245) ## Non Goals - Create a new timeout flag @@ -97,7 +97,7 @@ func RetryOnErrorMaxBackOff(maxDuration time.Duration, fn func() error) error { ``` ## Alternatives Considered - - Requeuing InProgress backups that is not known by current velero instance to still be in progress as failed (attempted in [#7863](https://github.com/velero-io/velero/pull/7863)) + - Requeuing InProgress backups that is not known by current velero instance to still be in progress as failed (attempted in [#7863](https://github.com/vmware-tanzu/velero/pull/7863)) - It was deemed as making backup restore flow hard to enhance for future reconciler updates such as adding cancel or adding parallel backups. ## Security Considerations @@ -107,5 +107,5 @@ None Retry should only trigger a restore or backup that is already in progress and not patching successfully by current instance. Prior InProgress backups/restores will not be re-processed and will remain stuck InProgress until there is another velero server (re)start. ## Implementation -There is a past implementation in [#7845](https://github.com/velero-io/velero/pull/7845/) where implementation for this design will be based upon. +There is a past implementation in [#7845](https://github.com/vmware-tanzu/velero/pull/7845/) where implementation for this design will be based upon. diff --git a/design/Implemented/schedule-skip-immediately-config_design.md b/design/Implemented/schedule-skip-immediately-config_design.md index f8dd8ea83..223e6b15a 100644 --- a/design/Implemented/schedule-skip-immediately-config_design.md +++ b/design/Implemented/schedule-skip-immediately-config_design.md @@ -6,7 +6,7 @@ New Schedules also create new backup immediately. This design allows user to *skip **immediately due** backup run upon unpausing or schedule creation*. ## Background -Currently, the default behavior of schedule when `.Status.LastBackup` is nil or is due immediately after unpausing, a backup will be created. This may not be a desired by all users (https://github.com/velero-io/velero/issues/6517) +Currently, the default behavior of schedule when `.Status.LastBackup` is nil or is due immediately after unpausing, a backup will be created. This may not be a desired by all users (https://github.com/vmware-tanzu/velero/issues/6517) User want ability to skip the first immediately due backup when schedule is unpaused and or created. diff --git a/design/Implemented/secrets.md b/design/Implemented/secrets.md index 56be05237..b1999c037 100644 --- a/design/Implemented/secrets.md +++ b/design/Implemented/secrets.md @@ -138,12 +138,12 @@ If we instead wanted to use an unique file each time, we could work around the o Once the credentials have been serialized, this path will be made available to the plugins. Instead of setting the necessary environment variable for the plugin process, the `config` map for the BSL will be modified to include an addiitional entry with the path to the credentials file: `credentialsFile`. -This will be passed through when [initializing the BSL](https://github.com/velero-io/velero/blob/main/pkg/plugin/velero/object_store.go#L27-L30) and it will be the responsibility of the plugin to use the passed credentials when starting a session. -For an example of how this would affect the AWS plugin, see [this PR](https://github.com/velero-io/velero-plugin-for-aws/pull/69). +This will be passed through when [initializing the BSL](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/velero/object_store.go#L27-L30) and it will be the responsibility of the plugin to use the passed credentials when starting a session. +For an example of how this would affect the AWS plugin, see [this PR](https://github.com/vmware-tanzu/velero-plugin-for-aws/pull/69). The restic controllers will also need to be updated to use the correct credentials. The BackupStorageLocation for a given PVB/PVR will be fetched and the `Credential` field from that BSL will be serialized. -The existing setup for the restic commands use the credentials from the environment variables with [some repo provider specific overrides](https://github.com/velero-io/velero/blob/main/pkg/controller/pod_volume_backup_controller.go#L260-L273). +The existing setup for the restic commands use the credentials from the environment variables with [some repo provider specific overrides](https://github.com/vmware-tanzu/velero/blob/main/pkg/controller/pod_volume_backup_controller.go#L260-L273). Instead of relying on the existing environment variables, if there are credentials for a particular BSL, the environment will be specifically created for each `RepoIdentifier`. This will use a lot of the existing logic with the exception that it will be modified to work with a serialized secret rather than find the secret file from an environment variable. Currently, GCP is the only provider that relies on the existing environment variables with no specific overrides. @@ -214,16 +214,16 @@ Prior to using any secret for a BSL, it will need to be serialized to disk. Using the details in the `Credential` field in the BSL, the contents of the Secret will be read and serialized to a file. Each plugin process would still have the same set of environment variables set, however the value used for each of these variables would instead be the path to the serialized secret. -To set the environment variables for a plugin process, the plugin manager must be modified so that when creating an ObjectStore, we pass in the entire BSL object, rather than [just the provider](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L132-L158). -The plugin manager currently stores a map of [plugin executables to an associated `RestartableProcess`](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L59-L70). -New restartable processes are created only [with the executable that the process would run](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L122). -This could be modified to also take the necessary environment variables so that when [underlying go-plugin process is created](https://github.com/velero-io/velero/blob/main/pkg/plugin/clientmgmt/client_builder.go#L78), these environment variables could be provided and would be set on the plugin process. +To set the environment variables for a plugin process, the plugin manager must be modified so that when creating an ObjectStore, we pass in the entire BSL object, rather than [just the provider](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L132-L158). +The plugin manager currently stores a map of [plugin executables to an associated `RestartableProcess`](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L59-L70). +New restartable processes are created only [with the executable that the process would run](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/manager.go#L122). +This could be modified to also take the necessary environment variables so that when [underlying go-plugin process is created](https://github.com/vmware-tanzu/velero/blob/main/pkg/plugin/clientmgmt/client_builder.go#L78), these environment variables could be provided and would be set on the plugin process. Taking this approach would not require any changes from plugins as the credentials information would be made available to them in the same way. However, it is quite a significant change in how we initialize and invoke plugins. We would also need to ensure that the restic controllers are updated in the same way so that correct credentials are used (when creating a `ResticRepository` or processing `PodVolumeBackup`/`PodVolumeRestore`). -This could be achieved by modifying the existing function to [run a restic command](https://github.com/velero-io/velero/blob/main/pkg/restic/repository_manager.go#L237-L290). +This could be achieved by modifying the existing function to [run a restic command](https://github.com/vmware-tanzu/velero/blob/main/pkg/restic/repository_manager.go#L237-L290). This function already sets environment variables for the restic process depending on which storage provider is being used. #### Include the details of the secret in `config` map passed to a plugin diff --git a/design/Implemented/supporting-volumeattributes-resource-policy.md b/design/Implemented/supporting-volumeattributes-resource-policy.md index d8f606d7f..a4f4d1bfc 100644 --- a/design/Implemented/supporting-volumeattributes-resource-policy.md +++ b/design/Implemented/supporting-volumeattributes-resource-policy.md @@ -1,7 +1,7 @@ # Adding Support For VolumeAttributes in Resource Policy ## Abstract -Currently [Velero Resource policies](https://velero.io/docs/main/resource-filtering/#creating-resource-policies) are only supporting "Driver" to be filtered for [CSI volume conditions](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28) +Currently [Velero Resource policies](https://velero.io/docs/main/resource-filtering/#creating-resource-policies) are only supporting "Driver" to be filtered for [CSI volume conditions](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28) If user want to skip certain CSI volumes based on other volume attributes like protocol or SKU, etc, they can't do it with the current Velero resource policies. It would be convenient if Velero resource policies could be extended to filter on volume attributes along with existing driver filter in the resource policies `conditions` to handle the backup of volumes just by `some specific volumes attributes conditions`. @@ -37,7 +37,7 @@ parameters: ``` ## High-Level Design -Modifying the existing Resource Policies code for [csiVolumeSource](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28C6-L28C22) to add the new `VolumeAttributes` filter for CSI volumes and adding validations in existing [csiCondition](https://github.com/velero-io/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources.go#L150) to match with volume attributes in the conditions from Resource Policy config map and original persistent volume. +Modifying the existing Resource Policies code for [csiVolumeSource](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28C6-L28C22) to add the new `VolumeAttributes` filter for CSI volumes and adding validations in existing [csiCondition](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources.go#L150) to match with volume attributes in the conditions from Resource Policy config map and original persistent volume. ## Detailed Design The volume resources policies should contain a list of policies which is the combination of conditions and related `action`, when target volumes meet the conditions, the related `action` will take effection. diff --git a/design/Implemented/velero-debug.md b/design/Implemented/velero-debug.md index bde147585..7da56e48f 100644 --- a/design/Implemented/velero-debug.md +++ b/design/Implemented/velero-debug.md @@ -3,7 +3,7 @@ ## Abstract To simplify the communication between velero users and developers, this document proposes the `velero debug` command to generate a tarball including the logs needed for debugging. -Github issue: https://github.com/velero-io/velero/issues/675 +Github issue: https://github.com/vmware-tanzu/velero/issues/675 ## Background Gathering information to troubleshoot a Velero deployment is currently spread across multiple commands, and is not very efficient. Logs for the Velero server itself are accessed via a kubectl logs command, while information on specific backups or restores are accessed via a Velero subcommand. Restic logs are even more complicated to retrieve, since one must gather logs for every instance of the daemonset, and there’s currently no good mechanism to locate which node a particular restic backup ran against. diff --git a/design/Implemented/vgdp-affinity-enhancement.md b/design/Implemented/vgdp-affinity-enhancement.md index b0edeca44..dc9e458c7 100644 --- a/design/Implemented/vgdp-affinity-enhancement.md +++ b/design/Implemented/vgdp-affinity-enhancement.md @@ -191,7 +191,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/velero-io/velero/pull/7982). +Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/vmware-tanzu/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/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md b/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md index bba5e67ca..0766bc9d4 100644 --- a/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md +++ b/design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md @@ -654,9 +654,9 @@ CLI is not changed. [2]: ../volume-snapshot-data-movement/volume-snapshot-data-movement.md [3]: ../vgdp-micro-service/vgdp-micro-service.md [4]: ../node-agent-concurrency.md -[5]: https://github.com/velero-io/velero/issues/8955 -[6]: https://github.com/velero-io/velero/issues/8956 -[7]: https://github.com/velero-io/velero/issues/8289 +[5]: https://github.com/vmware-tanzu/velero/issues/8955 +[6]: https://github.com/vmware-tanzu/velero/issues/8956 +[7]: https://github.com/vmware-tanzu/velero/issues/8289 [8]: https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/ -[9]: https://github.com/velero-io/velero/issues/7725 -[10]: https://github.com/velero-io/velero/issues/8423 \ No newline at end of file +[9]: https://github.com/vmware-tanzu/velero/issues/7725 +[10]: https://github.com/vmware-tanzu/velero/issues/8423 \ No newline at end of file diff --git a/design/Implemented/volume-group-snapshot.md b/design/Implemented/volume-group-snapshot.md index d10cb6941..83bc5a574 100644 --- a/design/Implemented/volume-group-snapshot.md +++ b/design/Implemented/volume-group-snapshot.md @@ -308,7 +308,7 @@ Backup workflow: } ``` -- Changes to the Existing [PVC ItemBlockAction plugin](https://github.com/velero-io/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/itemblock/actions/pvc_action.go#L64) (Update the GetRelatedItems function): +- Changes to the Existing [PVC ItemBlockAction plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/itemblock/actions/pvc_action.go#L64) (Update the GetRelatedItems function): ```go // Retrieve the VGS label key from the Backup spec. vgsLabelKey := backup.Spec.VolumeGroupSnapshotLabelKey @@ -338,7 +338,7 @@ Backup workflow: } ``` -- Updates to [CSI PVC plugin](https://github.com/velero-io/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/backup/actions/csi/pvc_action.go#L200) (Update the Execute method): +- Updates to [CSI PVC plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/backup/actions/csi/pvc_action.go#L200) (Update the Execute method): ```go func (p *pvcBackupItemAction) Execute( item runtime.Unstructured, diff --git a/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md b/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md index 25a3a5456..8f46276b8 100644 --- a/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md +++ b/design/Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md @@ -931,7 +931,7 @@ For 3, Velero leverage on DMs to decide how to save the log, but they will not g DMs need to be configured during installation so that they can be installed. Plugin DMs may have their own configuration, for VGDM, the only requirement is to install Velero node-agent. Moreover, the DMP is also required during the installation. -From release-1.14, the `github.com/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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/vmware-tanzu/velero` repository. The reason to merge the CSI plugin is: * The VolumeSnapshot data mover depends on the CSI plugin, it's reasonabe to integrate them. * This change reduces the Velero deploying complexity. diff --git a/design/Implemented/wait-for-additional-items.md b/design/Implemented/wait-for-additional-items.md index 852c0a2f4..8cff712b0 100644 --- a/design/Implemented/wait-for-additional-items.md +++ b/design/Implemented/wait-for-additional-items.md @@ -44,7 +44,7 @@ When each `RestoreItemAction` `Execute()` call returns, the restored. After restoring these items, Velero needs to be able to wait for them to be ready before moving on to the next item. Right after looping over the additional items at -https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L960-L991 +https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L960-L991 we still have a reference to the additional items (`GroupResource` and namespaced name), as well as a reference to the `RestoreItemAction` @@ -53,7 +53,7 @@ plugin which required it. At this point, if the `RestoreItemActionExecuteOutput` `WaitForAdditionalItems` field is set to `true` we need to call a func similar to `crdAvailable` which we will call `itemsAvailable` -https://github.com/velero-io/velero/blob/main/pkg/restore/restore.go#L623 +https://github.com/vmware-tanzu/velero/blob/main/pkg/restore/restore.go#L623 This func should also be defined within restore.go Instead of the one minute CRD timeout, we'll use a timeout specific to @@ -182,7 +182,7 @@ use an explicit `AreAdditionalItemsReady` func. Since this will break backwards compatibility with current `RestoreItemAction` plugins, implementation of this feature should wait until Velero plugin versioning, as described in -https://github.com/velero-io/velero/issues/3285 is +https://github.com/vmware-tanzu/velero/issues/3285 is implemented. With plugin versioning in place, existing (non-versioned or 1.0-versioned) `RestoreItemAction` plugins which do not define `AreAdditionalItemsReady` would be able to coexist with a diff --git a/design/Implemented/wildcard-namespace-support-design.md b/design/Implemented/wildcard-namespace-support-design.md index c9076e662..45c4d4641 100644 --- a/design/Implemented/wildcard-namespace-support-design.md +++ b/design/Implemented/wildcard-namespace-support-design.md @@ -7,7 +7,7 @@ Velero currently treats namespace patterns with glob characters as literal strin ## Background -Requested in [#1874](https://github.com/velero-io/velero/issues/1874) for more flexible namespace selection. +Requested in [#1874](https://github.com/vmware-tanzu/velero/issues/1874) for more flexible namespace selection. ## Goals diff --git a/design/cli-install-changes.md b/design/cli-install-changes.md index c9f278190..3464ce0e5 100644 --- a/design/cli-install-changes.md +++ b/design/cli-install-changes.md @@ -276,9 +276,9 @@ The value for these flags will be stored as annotations. #### Handling CA certs -In anticipation of a new configuration implementation to handle custom CA certs (as per design doc https://github.com/velero-io/velero/blob/main/design/custom-ca-support.md), a new flag `velero storage-location create/set --cacert-file mapStringString` is proposed. It sets the configuration to use for creating a secret containing a custom certificate for an S3 location of a plugin provider. Format is provider:path-to-file. +In anticipation of a new configuration implementation to handle custom CA certs (as per design doc https://github.com/vmware-tanzu/velero/blob/main/design/custom-ca-support.md), a new flag `velero storage-location create/set --cacert-file mapStringString` is proposed. It sets the configuration to use for creating a secret containing a custom certificate for an S3 location of a plugin provider. Format is provider:path-to-file. -See discussion https://github.com/velero-io/velero/pull/2259#discussion_r384700723 for more clarification. +See discussion https://github.com/vmware-tanzu/velero/pull/2259#discussion_r384700723 for more clarification. #### Renaming "provider" to "location-plugin" @@ -344,7 +344,7 @@ Another new behavior that must be added: the server needs to identify when there As it is today, a valid VSL would not be required to create backups, unless the backup included a PV. -To make it easier for the user to identify if their Velero server is ready to create backups or not, a `velero status` command should be added. This issue has been created some time ago for this purpose: https://github.com/velero-io/velero/issues/1094. +To make it easier for the user to identify if their Velero server is ready to create backups or not, a `velero status` command should be added. This issue has been created some time ago for this purpose: https://github.com/vmware-tanzu/velero/issues/1094. ## Alternatives Considered diff --git a/design/new-prepost-backuprestore-plugin-hooks.md b/design/new-prepost-backuprestore-plugin-hooks.md index 15fd02728..65e305147 100644 --- a/design/new-prepost-backuprestore-plugin-hooks.md +++ b/design/new-prepost-backuprestore-plugin-hooks.md @@ -8,7 +8,7 @@ The proposed plugin hooks are to be executed only once: pre-backup (before backu ### PreBackup and PostBackup Actions -For the backup, the sequence of events of Velero backup are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/velero-io/velero/issues/3533) ): +For the backup, the sequence of events of Velero backup are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/vmware-tanzu/velero/issues/3533) ): ``` New Backup Request @@ -40,16 +40,16 @@ New Backup Request ``` These plugin hooks will be invoked: -- PreBackupAction: plugin actions are executed after the backup object is created and validated but before the backup is being processed, more precisely _before_ function [c.backupper.Backup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L590). If the PreBackupActions return an err, the backup object is not processed and the Backup phase will be set as `FailedPreBackupActions`. +- PreBackupAction: plugin actions are executed after the backup object is created and validated but before the backup is being processed, more precisely _before_ function [c.backupper.Backup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L590). If the PreBackupActions return an err, the backup object is not processed and the Backup phase will be set as `FailedPreBackupActions`. -- PostBackupAction: plugin actions are executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). +- PostBackupAction: plugin actions are executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). The proposed plugin hooks will execute actions that will have statuses on their own: `Backup.Status.PreBackupActionsStatuses` and `Backup.Status.PostBackupActionsStatuses` which will be an array of a proposed struct `ActionStatus` with PluginName, StartTimestamp, CompletionTimestamp and Phase. ### PreRestore and PostRestore Actions -For the restore, the sequence of events of Velero restore are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/velero-io/velero/issues/3533) ): +For the restore, the sequence of events of Velero restore are the following (these sequence depicted is prior upcoming changes for [upload progress #3533](https://github.com/vmware-tanzu/velero/issues/3533) ): ``` New Restore Request |--> Validation of the request @@ -84,9 +84,9 @@ New Restore Request These plugin hooks will be invoked: -- PreRestoreAction: plugin actions are executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. +- PreRestoreAction: plugin actions are executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. -- PostRestoreAction: plugin actions are executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). +- PostRestoreAction: plugin actions are executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). The proposed plugin hooks will execute actions that will have statuses on their own: `Restore.Status.PreRestoreActionsStatuses` and `Restore.Status.PostRestoreActionsStatuses` which will be an array of a proposed struct `ActionStatus` with PluginName, StartTimestamp, CompletionTimestamp and Phase. @@ -148,7 +148,7 @@ The PostBackupAction plugin API will resemble the BackupItemAction plugin design By this stage, the backup has already been executed, with items backed up and volumes snapshots processed and persisted. The `PostBackupAction` interface will only have an `Execute()` method since the plugin will be executed only once per Backup, not per item. -If there are any PostBackupAction plugins registered, they will be executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/velero-io/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). +If there are any PostBackupAction plugins registered, they will be executed after the backup is finished and persisted, more precisely _after_ function [c.runBackup](https://github.com/vmware-tanzu/velero/blob/74476db9d791fa91bba0147eac8ec189820adb3d/pkg/controller/backup_controller.go#L274). The Velero restore controller package will be modified for `PreRestoreAction` and `PostRestoreAction`. @@ -156,13 +156,13 @@ The PreRestoreAction plugin API will resemble the RestoreItemAction plugin desig It will not receive any resource list items because the restore has not yet been running at that stage. In addition, the `PreRestoreAction` interface will only have an `Execute()` method since the plugin will be executed only once per Restore creation, not per item. -The Velero restore controller will be modified so that if there are any PreRestoreAction plugins registered, they will be executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. +The Velero restore controller will be modified so that if there are any PreRestoreAction plugins registered, they will be executed after the restore object is created and validated and before the backup object is fetched, more precisely in function `runValidatedRestore` _after_ function [info.backupStore.GetBackupVolumeSnapshots](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L460). If the PreRestoreActions return an err, the restore object is not processed and the Restore phase will be set a `FailedPreRestoreActions`. The PostRestoreAction plugin API will resemble the RestoreItemAction plugin design, but with the fundamental difference that it will receive only as input the Velero `Restore` object without any resource list items. At this stage, the restore has already been executed. The `PostRestoreAction` interface will only have an `Execute()` method since the plugin will be executed only once per Restore, not per item. -If any PostRestoreAction plugins are registered, they will be executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/velero-io/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). +If any PostRestoreAction plugins are registered, they will be executed after the restore finishes processing all items and volumes snapshots are restored and logs persisted, more precisely in function `processRestore` _after_ setting [`restore.Status.CompletionTimestamp`](https://github.com/vmware-tanzu/velero/blob/7c75cd6cf854064c9a454e53ba22cc5881d3f1f0/pkg/controller/restore_controller.go#L273). ## Detailed Design diff --git a/design/restore-progress.md b/design/restore-progress.md index 3ce38414e..d86b2cfa6 100644 --- a/design/restore-progress.md +++ b/design/restore-progress.md @@ -217,4 +217,4 @@ TBD ## Open Issues -https://github.com/velero-io/velero/issues/21 \ No newline at end of file +https://github.com/vmware-tanzu/velero/issues/21 \ No newline at end of file diff --git a/go.mod b/go.mod index a4f26fd35..25b753d8c 100644 --- a/go.mod +++ b/go.mod @@ -1,4 +1,4 @@ -module github.com/velero-io/velero +module github.com/vmware-tanzu/velero go 1.26.0 diff --git a/hack/issue-template-gen/main.go b/hack/issue-template-gen/main.go index 5950f84c5..dcdcf782e 100644 --- a/hack/issue-template-gen/main.go +++ b/hack/issue-template-gen/main.go @@ -24,7 +24,7 @@ import ( "os" "text/template" - "github.com/velero-io/velero/pkg/cmd/cli/bug" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/bug" ) func main() { diff --git a/hack/release-tools/brew-update.sh b/hack/release-tools/brew-update.sh index 5241340eb..dfb1f52be 100755 --- a/hack/release-tools/brew-update.sh +++ b/hack/release-tools/brew-update.sh @@ -13,7 +13,7 @@ then fi # GitHub URL which contains the source code archive for the tagged release -URL=https://github.com/velero-io/velero/archive/$VELERO_VERSION.tar.gz +URL=https://github.com/vmware-tanzu/velero/archive/$VELERO_VERSION.tar.gz # Update brew so we're sure we have the latest Velero formula brew update diff --git a/hack/release-tools/gen-docs.sh b/hack/release-tools/gen-docs.sh index 956153805..595de2ee6 100755 --- a/hack/release-tools/gen-docs.sh +++ b/hack/release-tools/gen-docs.sh @@ -100,7 +100,7 @@ rm $DATA_DOCS_DIRECTORY/$NEW_DOCS_TOC.yml && cp $DATA_DOCS_DIRECTORY/$MAIN_BRANC if [[ $(uname) == "Darwin" ]]; then echo "[OS X] updating version-specific links" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://velero.io/docs/$MAIN_BRANCH|https://velero.io/docs/$VELERO_VERSION|g" - find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://github.com/velero-io/velero/blob/$MAIN_BRANCH|https://github.com/velero-io/velero/blob/$VELERO_VERSION|g" + find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i '' "s|https://github.com/vmware-tanzu/velero/blob/$MAIN_BRANCH|https://github.com/vmware-tanzu/velero/blob/$VELERO_VERSION|g" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "_index.md" | xargs sed -i '' "s|version: $MAIN_BRANCH|version: $NEW_DOCS_VERSION|g" echo "[OS X] Updating latest version in $CONFIG_FILE" @@ -121,7 +121,7 @@ ${NEW_DOCS_VERSION}: ${NEW_DOCS_TOC} else echo "[Linux] updating version-specific links" find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://velero.io/docs/$MAIN_BRANCH|https://velero.io/docs/$VELERO_VERSION|g" - find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://github.com/velero-io/velero/blob/$MAIN_BRANCH|https://github.com/velero-io/velero/blob/$VELERO_VERSION|g" + find $DOCS_DIRECTORY/${NEW_DOCS_VERSION} -type f -name "*.md" | xargs sed -i'' "s|https://github.com/vmware-tanzu/velero/blob/$MAIN_BRANCH|https://github.com/vmware-tanzu/velero/blob/$VELERO_VERSION|g" echo "[Linux] Updating latest version in $CONFIG_FILE" sed -i'' "s/latest: ${PREVIOUS_DOCS_VERSION}/latest: ${NEW_DOCS_VERSION}/" $CONFIG_FILE diff --git a/hack/update-1fmt.sh b/hack/update-1fmt.sh index 002f3d27f..a23261cb2 100755 --- a/hack/update-1fmt.sh +++ b/hack/update-1fmt.sh @@ -47,7 +47,7 @@ else fi echo "${ACTION} goimports" -output=$(goimports "${MODE}" -local github.com/velero-io/velero ${files}) +output=$(goimports "${MODE}" -local github.com/vmware-tanzu/velero ${files}) if [[ -n "${output}" ]]; then VERIFY_IMPORTS_FAILED=1 echo "${output}" diff --git a/hack/update-2proto.sh b/hack/update-2proto.sh index cd7e85cb0..07cc732f5 100755 --- a/hack/update-2proto.sh +++ b/hack/update-2proto.sh @@ -23,7 +23,7 @@ protoc \ -I pkg/plugin/proto/ \ -I /usr/include \ --go_out=pkg/plugin/generated/ \ - --go_opt=module=github.com/velero-io/velero/pkg/plugin/generated \ + --go_opt=module=github.com/vmware-tanzu/velero/pkg/plugin/generated \ --go-grpc_out=pkg/plugin/generated \ --go-grpc_opt=paths=source_relative \ --go-grpc_opt=require_unimplemented_servers=false \ diff --git a/internal/credentials/file_store.go b/internal/credentials/file_store.go index 53d15cf68..d1f1fb10a 100644 --- a/internal/credentials/file_store.go +++ b/internal/credentials/file_store.go @@ -25,8 +25,8 @@ import ( corev1api "k8s.io/api/core/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // FileStore defines operations for interacting with credentials diff --git a/internal/credentials/file_store_test.go b/internal/credentials/file_store_test.go index ae84bd9be..d748ca29e 100644 --- a/internal/credentials/file_store_test.go +++ b/internal/credentials/file_store_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestNamespacedFileStore(t *testing.T) { diff --git a/internal/credentials/secret_store.go b/internal/credentials/secret_store.go index d6307f23b..f4d2111a5 100644 --- a/internal/credentials/secret_store.go +++ b/internal/credentials/secret_store.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // SecretStore defines operations for interacting with credentials diff --git a/internal/delete/actions/csi/volumesnapshotcontent_action.go b/internal/delete/actions/csi/volumesnapshotcontent_action.go index 791cdb5c3..9473686e0 100644 --- a/internal/delete/actions/csi/volumesnapshotcontent_action.go +++ b/internal/delete/actions/csi/volumesnapshotcontent_action.go @@ -29,10 +29,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/client" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/client" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) // volumeSnapshotContentDeleteItemAction is a restore item action plugin for Velero diff --git a/internal/delete/actions/csi/volumesnapshotcontent_action_test.go b/internal/delete/actions/csi/volumesnapshotcontent_action_test.go index c5c6fc734..e8a0b5865 100644 --- a/internal/delete/actions/csi/volumesnapshotcontent_action_test.go +++ b/internal/delete/actions/csi/volumesnapshotcontent_action_test.go @@ -32,11 +32,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) // fakeClientWithErrors wraps a real client and injects errors for specific operations. diff --git a/internal/delete/delete_item_action_handler.go b/internal/delete/delete_item_action_handler.go index 2e4f7588b..ba242c0ca 100644 --- a/internal/delete/delete_item_action_handler.go +++ b/internal/delete/delete_item_action_handler.go @@ -19,7 +19,7 @@ package delete import ( "io" - "github.com/velero-io/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -27,11 +27,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/filesystem" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // Context provides the necessary environment to run DeleteItemAction plugins diff --git a/internal/delete/delete_item_action_handler_test.go b/internal/delete/delete_item_action_handler_test.go index 4d20fc3e0..6743cd1f9 100644 --- a/internal/delete/delete_item_action_handler_test.go +++ b/internal/delete/delete_item_action_handler_test.go @@ -29,12 +29,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestInvokeDeleteItemActionsRunForCorrectItems(t *testing.T) { diff --git a/internal/hook/item_hook_handler.go b/internal/hook/item_hook_handler.go index bb0fe1c9f..52dd815ab 100644 --- a/internal/hook/item_hook_handler.go +++ b/internal/hook/item_hook_handler.go @@ -34,13 +34,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/podexec" - "github.com/velero-io/velero/pkg/restorehelper" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/podexec" + "github.com/vmware-tanzu/velero/pkg/restorehelper" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type HookPhase string @@ -147,7 +147,7 @@ func (i *InitContainerRestoreHookHandler) HandleRestoreHooks( labels := labels.Set(metadata.GetLabels()) // Apply the hook according to the target namespace in which the pod will be restored - // more details see https://github.com/velero-io/velero/issues/4720 + // more details see https://github.com/vmware-tanzu/velero/issues/4720 if namespaceMapping != nil { if n, ok := namespaceMapping[namespace]; ok { namespace = n diff --git a/internal/hook/item_hook_handler_test.go b/internal/hook/item_hook_handler_test.go index 747af28f7..37f1500a3 100644 --- a/internal/hook/item_hook_handler_test.go +++ b/internal/hook/item_hook_handler_test.go @@ -32,12 +32,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) func TestHandleHooksSkips(t *testing.T) { diff --git a/internal/hook/wait_exec_hook_handler.go b/internal/hook/wait_exec_hook_handler.go index 85c804f20..92a905c8c 100644 --- a/internal/hook/wait_exec_hook_handler.go +++ b/internal/hook/wait_exec_hook_handler.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/tools/cache" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/podexec" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/podexec" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type WaitExecHookHandler interface { diff --git a/internal/hook/wait_exec_hook_handler_test.go b/internal/hook/wait_exec_hook_handler_test.go index bc3da65f4..fb102b16f 100644 --- a/internal/hook/wait_exec_hook_handler_test.go +++ b/internal/hook/wait_exec_hook_handler_test.go @@ -32,10 +32,10 @@ import ( "k8s.io/client-go/tools/cache" fcache "k8s.io/client-go/tools/cache/testing" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) type fakeListWatchFactory struct { diff --git a/internal/resourcemodifiers/resource_modifiers.go b/internal/resourcemodifiers/resource_modifiers.go index 8ee1e0e20..cc780df03 100644 --- a/internal/resourcemodifiers/resource_modifiers.go +++ b/internal/resourcemodifiers/resource_modifiers.go @@ -30,7 +30,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/yaml" - "github.com/velero-io/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) const ( diff --git a/internal/resourcepolicies/resource_policies.go b/internal/resourcepolicies/resource_policies.go index e605b1e15..ce32dba19 100644 --- a/internal/resourcepolicies/resource_policies.go +++ b/internal/resourcepolicies/resource_policies.go @@ -28,7 +28,7 @@ import ( corev1api "k8s.io/api/core/v1" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) type VolumeActionType string diff --git a/internal/restartabletest/restartable_delegate.go b/internal/restartabletest/restartable_delegate.go index 0d9633b88..41d56cf31 100644 --- a/internal/restartabletest/restartable_delegate.go +++ b/internal/restartabletest/restartable_delegate.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" ) type MockRestartableProcess struct { diff --git a/internal/storage/storagelocation.go b/internal/storage/storagelocation.go index 370c85118..d5fe548c0 100644 --- a/internal/storage/storagelocation.go +++ b/internal/storage/storagelocation.go @@ -25,7 +25,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // DefaultBackupLocationInfo holds server default backup storage location information diff --git a/internal/storage/storagelocation_test.go b/internal/storage/storagelocation_test.go index fad95988d..44eabff48 100644 --- a/internal/storage/storagelocation_test.go +++ b/internal/storage/storagelocation_test.go @@ -23,10 +23,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util" ) func TestIsReadyToValidate(t *testing.T) { diff --git a/internal/velero/images.go b/internal/velero/images.go index 18903e1cc..cefbd1441 100644 --- a/internal/velero/images.go +++ b/internal/velero/images.go @@ -19,7 +19,7 @@ package velero import ( "fmt" - "github.com/velero-io/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/buildinfo" ) // Use Dockerhub as the default registry if the build process didn't supply a registry diff --git a/internal/velero/images_test.go b/internal/velero/images_test.go index ecdf2d995..5a68a4fd1 100644 --- a/internal/velero/images_test.go +++ b/internal/velero/images_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/buildinfo" ) func TestImageTag(t *testing.T) { diff --git a/internal/velero/serverstatusrequest.go b/internal/velero/serverstatusrequest.go index f4013774a..c9c8acc0a 100644 --- a/internal/velero/serverstatusrequest.go +++ b/internal/velero/serverstatusrequest.go @@ -17,9 +17,9 @@ limitations under the License. package velero import ( - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" ) type PluginLister interface { diff --git a/internal/volume/snapshotlocation.go b/internal/volume/snapshotlocation.go index 5fb52aa00..ad23fa1f4 100644 --- a/internal/volume/snapshotlocation.go +++ b/internal/volume/snapshotlocation.go @@ -19,8 +19,8 @@ package volume import ( "github.com/pkg/errors" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // UpdateVolumeSnapshotLocationWithCredentialConfig adds the credentials file path to the config diff --git a/internal/volume/utils.go b/internal/volume/utils.go index fd613d3f0..fbb3ec67b 100644 --- a/internal/volume/utils.go +++ b/internal/volume/utils.go @@ -20,7 +20,7 @@ import ( "regexp" ) -// it has to have the same value as "github.com/velero-io/velero/pkg/restore".ItemRestoreResultCreated +// it has to have the same value as "github.com/vmware-tanzu/velero/pkg/restore".ItemRestoreResultCreated const itemRestoreResultCreated = "created" // RestoredPVCFromRestoredResourceList returns a set of PVCs that were restored from the given restoredResourceList. diff --git a/internal/volume/volumes_information.go b/internal/volume/volumes_information.go index f3ebe0548..4d5961bdb 100644 --- a/internal/volume/volumes_information.go +++ b/internal/volume/volumes_information.go @@ -29,13 +29,13 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/label" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" ) type Method string diff --git a/internal/volume/volumes_information_test.go b/internal/volume/volumes_information_test.go index ba6143dda..b39ba82f8 100644 --- a/internal/volume/volumes_information_test.go +++ b/internal/volume/volumes_information_test.go @@ -31,14 +31,14 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func TestGenerateVolumeInfoForSkippedPV(t *testing.T) { diff --git a/internal/volumehelper/volume_policy_helper.go b/internal/volumehelper/volume_policy_helper.go index 84ab0768e..339b80011 100644 --- a/internal/volumehelper/volume_policy_helper.go +++ b/internal/volumehelper/volume_policy_helper.go @@ -12,13 +12,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/resourcepolicies" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/util/boolptr" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" - vhutil "github.com/velero-io/velero/pkg/util/volumehelper" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" + vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" ) type volumeHelperImpl struct { diff --git a/internal/volumehelper/volume_policy_helper_test.go b/internal/volumehelper/volume_policy_helper_test.go index 979803c3f..5e52ae73b 100644 --- a/internal/volumehelper/volume_policy_helper_test.go +++ b/internal/volumehelper/volume_policy_helper_test.go @@ -29,12 +29,12 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/utils/ptr" - "github.com/velero-io/velero/internal/resourcepolicies" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - velerotest "github.com/velero-io/velero/pkg/test" - podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" ) func TestVolumeHelperImpl_ShouldPerformSnapshot(t *testing.T) { diff --git a/pkg/apis/velero/v1/pod_volume_backup_types.go b/pkg/apis/velero/v1/pod_volume_backup_types.go index 2eea3b545..b246906fb 100644 --- a/pkg/apis/velero/v1/pod_volume_backup_types.go +++ b/pkg/apis/velero/v1/pod_volume_backup_types.go @@ -20,7 +20,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" ) // PodVolumeBackupSpec is the specification for a PodVolumeBackup. diff --git a/pkg/apis/velero/v1/pod_volume_restore_type.go b/pkg/apis/velero/v1/pod_volume_restore_type.go index ae84f1c5d..c1d75b71c 100644 --- a/pkg/apis/velero/v1/pod_volume_restore_type.go +++ b/pkg/apis/velero/v1/pod_volume_restore_type.go @@ -20,7 +20,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" ) // PodVolumeRestoreSpec is the specification for a PodVolumeRestore. diff --git a/pkg/apis/velero/v2alpha1/data_download_types.go b/pkg/apis/velero/v2alpha1/data_download_types.go index 93e194ff5..4ea7128ec 100644 --- a/pkg/apis/velero/v2alpha1/data_download_types.go +++ b/pkg/apis/velero/v2alpha1/data_download_types.go @@ -19,7 +19,7 @@ package v2alpha1 import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" ) // DataDownloadSpec is the specification for a DataDownload. diff --git a/pkg/apis/velero/v2alpha1/data_upload_types.go b/pkg/apis/velero/v2alpha1/data_upload_types.go index b40475c1b..751da4555 100644 --- a/pkg/apis/velero/v2alpha1/data_upload_types.go +++ b/pkg/apis/velero/v2alpha1/data_upload_types.go @@ -19,7 +19,7 @@ package v2alpha1 import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" ) // DataUploadSpec is the specification for a DataUpload. diff --git a/pkg/archive/extractor.go b/pkg/archive/extractor.go index 42c65be39..aae9a7a85 100644 --- a/pkg/archive/extractor.go +++ b/pkg/archive/extractor.go @@ -26,7 +26,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // Extractor unzips/extracts a backup tarball to a local diff --git a/pkg/archive/extractor_test.go b/pkg/archive/extractor_test.go index dde69d4aa..a4daf02ca 100644 --- a/pkg/archive/extractor_test.go +++ b/pkg/archive/extractor_test.go @@ -26,8 +26,8 @@ import ( "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) func TestUnzipAndExtractBackup(t *testing.T) { diff --git a/pkg/archive/filesystem.go b/pkg/archive/filesystem.go index c3a196930..73b0d1dcf 100644 --- a/pkg/archive/filesystem.go +++ b/pkg/archive/filesystem.go @@ -22,8 +22,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/filesystem" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // GetItemFilePath returns an item's file path once extracted from a Velero backup archive. diff --git a/pkg/archive/filesystem_test.go b/pkg/archive/filesystem_test.go index 08e526466..bf7f16c76 100644 --- a/pkg/archive/filesystem_test.go +++ b/pkg/archive/filesystem_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestGetItemFilePath(t *testing.T) { diff --git a/pkg/archive/parser.go b/pkg/archive/parser.go index 4f682d333..166e03114 100644 --- a/pkg/archive/parser.go +++ b/pkg/archive/parser.go @@ -25,8 +25,8 @@ import ( "github.com/sirupsen/logrus" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/filesystem" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) var ErrNotExist = errors.New("does not exist") diff --git a/pkg/archive/parser_test.go b/pkg/archive/parser_test.go index 3ea837bb5..1af8077e8 100644 --- a/pkg/archive/parser_test.go +++ b/pkg/archive/parser_test.go @@ -24,7 +24,7 @@ import ( "github.com/stretchr/testify/require" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestParse(t *testing.T) { diff --git a/pkg/backup/actions/backup_pv_action.go b/pkg/backup/actions/backup_pv_action.go index b1c9a4826..c3f378fac 100644 --- a/pkg/backup/actions/backup_pv_action.go +++ b/pkg/backup/actions/backup_pv_action.go @@ -25,9 +25,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) // PVCAction inspects a PersistentVolumeClaim for the PersistentVolume diff --git a/pkg/backup/actions/backup_pv_action_test.go b/pkg/backup/actions/backup_pv_action_test.go index 5b0fc3a47..41af9e9bf 100644 --- a/pkg/backup/actions/backup_pv_action_test.go +++ b/pkg/backup/actions/backup_pv_action_test.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBackupPVAction(t *testing.T) { diff --git a/pkg/backup/actions/csi/pvc_action.go b/pkg/backup/actions/csi/pvc_action.go index fa6414f39..7f5fd2afa 100644 --- a/pkg/backup/actions/csi/pvc_action.go +++ b/pkg/backup/actions/csi/pvc_action.go @@ -44,21 +44,21 @@ import ( "k8s.io/apimachinery/pkg/api/resource" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - veleroclient "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/label" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/utils/volumehelper" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - uploaderUtil "github.com/velero-io/velero/pkg/uploader/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" - vhutil "github.com/velero-io/velero/pkg/util/volumehelper" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/label" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/utils/volumehelper" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + uploaderUtil "github.com/vmware-tanzu/velero/pkg/uploader/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" + vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" ) // TODO: Replace hardcoded VolumeSnapshot finalizer strings with constants from diff --git a/pkg/backup/actions/csi/pvc_action_test.go b/pkg/backup/actions/csi/pvc_action_test.go index 9d9818571..629c5e9cd 100644 --- a/pkg/backup/actions/csi/pvc_action_test.go +++ b/pkg/backup/actions/csi/pvc_action_test.go @@ -23,7 +23,7 @@ import ( "testing" "time" - "github.com/velero-io/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/kuberesource" volumegroupsnapshotv1beta2 "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumegroupsnapshot/v1beta2" "github.com/stretchr/testify/assert" @@ -31,7 +31,7 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/utils/pointer" - "github.com/velero-io/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/label" "github.com/google/go-cmp/cmp" "github.com/google/go-cmp/cmp/cmpopts" @@ -50,13 +50,13 @@ import ( "k8s.io/apimachinery/pkg/util/wait" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) const testDriver = "csi.example.com" diff --git a/pkg/backup/actions/csi/volumesnapshot_action.go b/pkg/backup/actions/csi/volumesnapshot_action.go index 5eefde544..0e0e9a840 100644 --- a/pkg/backup/actions/csi/volumesnapshot_action.go +++ b/pkg/backup/actions/csi/volumesnapshot_action.go @@ -30,16 +30,16 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/label" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/label" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) // volumeSnapshotBackupItemAction is a backup item action plugin to backup diff --git a/pkg/backup/actions/csi/volumesnapshot_action_test.go b/pkg/backup/actions/csi/volumesnapshot_action_test.go index 1684c2371..1db5cd475 100644 --- a/pkg/backup/actions/csi/volumesnapshot_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshot_action_test.go @@ -28,12 +28,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestVSExecute(t *testing.T) { diff --git a/pkg/backup/actions/csi/volumesnapshotclass_action.go b/pkg/backup/actions/csi/volumesnapshotclass_action.go index b54a59271..8200b465f 100644 --- a/pkg/backup/actions/csi/volumesnapshotclass_action.go +++ b/pkg/backup/actions/csi/volumesnapshotclass_action.go @@ -24,11 +24,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - csiutil "github.com/velero-io/velero/pkg/util/csi" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) // volumeSnapshotClassBackupItemAction is a backup item action plugin to diff --git a/pkg/backup/actions/csi/volumesnapshotclass_action_test.go b/pkg/backup/actions/csi/volumesnapshotclass_action_test.go index 92999361a..3bd90a8aa 100644 --- a/pkg/backup/actions/csi/volumesnapshotclass_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshotclass_action_test.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func TestVSClassExecute(t *testing.T) { diff --git a/pkg/backup/actions/csi/volumesnapshotcontent_action.go b/pkg/backup/actions/csi/volumesnapshotcontent_action.go index e0e2d9d32..d4cd6d46c 100644 --- a/pkg/backup/actions/csi/volumesnapshotcontent_action.go +++ b/pkg/backup/actions/csi/volumesnapshotcontent_action.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - csiutil "github.com/velero-io/velero/pkg/util/csi" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) // volumeSnapshotContentBackupItemAction is a backup item action plugin to backup diff --git a/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go b/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go index f858d6054..e24623d9a 100644 --- a/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go +++ b/pkg/backup/actions/csi/volumesnapshotcontent_action_test.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestVSCExecute(t *testing.T) { diff --git a/pkg/backup/actions/pod_action.go b/pkg/backup/actions/pod_action.go index 8a2c81018..8ed5e3b44 100644 --- a/pkg/backup/actions/pod_action.go +++ b/pkg/backup/actions/pod_action.go @@ -22,9 +22,9 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) // PodAction implements ItemAction. diff --git a/pkg/backup/actions/pod_action_test.go b/pkg/backup/actions/pod_action_test.go index a363043ec..d0d30b653 100644 --- a/pkg/backup/actions/pod_action_test.go +++ b/pkg/backup/actions/pod_action_test.go @@ -23,9 +23,9 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestPodActionAppliesTo(t *testing.T) { diff --git a/pkg/backup/actions/remap_crd_version_action.go b/pkg/backup/actions/remap_crd_version_action.go index c7ad51bdc..3f8c2f79d 100644 --- a/pkg/backup/actions/remap_crd_version_action.go +++ b/pkg/backup/actions/remap_crd_version_action.go @@ -30,10 +30,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RemapCRDVersionAction inspects CustomResourceDefinition and decides if it is a v1 diff --git a/pkg/backup/actions/remap_crd_version_action_test.go b/pkg/backup/actions/remap_crd_version_action_test.go index 4eb03f5bd..8f21fb151 100644 --- a/pkg/backup/actions/remap_crd_version_action_test.go +++ b/pkg/backup/actions/remap_crd_version_action_test.go @@ -31,11 +31,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestRemapCRDVersionAction(t *testing.T) { diff --git a/pkg/backup/actions/service_account_action.go b/pkg/backup/actions/service_account_action.go index 810de51c1..b563f7a03 100644 --- a/pkg/backup/actions/service_account_action.go +++ b/pkg/backup/actions/service_account_action.go @@ -22,10 +22,10 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) // ServiceAccountAction implements ItemAction. diff --git a/pkg/backup/actions/service_account_action_test.go b/pkg/backup/actions/service_account_action_test.go index c5164d40b..90d09005b 100644 --- a/pkg/backup/actions/service_account_action_test.go +++ b/pkg/backup/actions/service_account_action_test.go @@ -28,10 +28,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/actionhelpers" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) func newV1ClusterRoleBindingList(rbacCRBList []rbacv1.ClusterRoleBinding) []actionhelpers.ClusterRoleBinding { diff --git a/pkg/backup/backup.go b/pkg/backup/backup.go index 0c75cf447..9edaf6a85 100644 --- a/pkg/backup/backup.go +++ b/pkg/backup/backup.go @@ -42,28 +42,28 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/volume" - "github.com/velero-io/velero/internal/volumehelper" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/itemblock" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podexec" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/volume" + "github.com/vmware-tanzu/velero/internal/volumehelper" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/itemblock" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podexec" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // BackupVersion is the current backup major version for Velero. @@ -327,7 +327,7 @@ func (kb *kubernetesBackupper) BackupWithResolvers( // check if there are any namespaces included in the backup which are managed by argoCD // We will check for the existence of a ArgoCD label in the includedNamespaces and add a warning // so that users are at least aware about the existence of argoCD managed ns in their backup - // Related Issue: https://github.com/velero-io/velero/issues/7905 + // Related Issue: https://github.com/vmware-tanzu/velero/issues/7905 if len(nsManagedByArgoCD) > 0 { log.Warnf("backup operation may encounter complications and potentially produce undesirable results due to the inclusion of namespaces %v managed by ArgoCD in the backup.", nsManagedByArgoCD) } diff --git a/pkg/backup/backup_test.go b/pkg/backup/backup_test.go index c4215eaf9..f9351245c 100644 --- a/pkg/backup/backup_test.go +++ b/pkg/backup/backup_test.go @@ -41,26 +41,26 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/internal/volume" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/persistence" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/test" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/volume" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/persistence" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/test" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestBackedUpItemsMatchesTarballContents(t *testing.T) { @@ -1180,7 +1180,7 @@ func TestBackupResourceCohabitation(t *testing.T) { // TestBackupUsesNewCohabitatingResourcesForEachBackup ensures that when two backups are // run that each include cohabiting resources, one copy of the relevant resources is // backed up in each backup. Verification is done by looking at the contents of the backup -// tarball. This covers a specific issue that was fixed by https://github.com/velero-io/velero/pull/485. +// tarball. This covers a specific issue that was fixed by https://github.com/vmware-tanzu/velero/pull/485. func TestBackupUsesNewCohabitatingResourcesForEachBackup(t *testing.T) { h := newHarness(t, nil) defer h.itemBlockPool.Stop() diff --git a/pkg/backup/delete_helpers.go b/pkg/backup/delete_helpers.go index 4641ed597..fa4cbb744 100644 --- a/pkg/backup/delete_helpers.go +++ b/pkg/backup/delete_helpers.go @@ -21,8 +21,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/label" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/label" ) // NewDeleteBackupRequest creates a DeleteBackupRequest for the backup identified by name and uid. diff --git a/pkg/backup/item_backupper.go b/pkg/backup/item_backupper.go index 9a5476cd9..2ca266e91 100644 --- a/pkg/backup/item_backupper.go +++ b/pkg/backup/item_backupper.go @@ -37,23 +37,23 @@ import ( "k8s.io/apimachinery/pkg/util/sets" kbClient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemblock" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/util/boolptr" - csiutil "github.com/velero-io/velero/pkg/util/csi" - "github.com/velero-io/velero/pkg/util/volumehelper" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemblock" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" + "github.com/vmware-tanzu/velero/pkg/util/volumehelper" ) const ( diff --git a/pkg/backup/item_backupper_test.go b/pkg/backup/item_backupper_test.go index 0e56e5aca..be91b6d34 100644 --- a/pkg/backup/item_backupper_test.go +++ b/pkg/backup/item_backupper_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" ctrlfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/pkg/kuberesource" "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" @@ -34,7 +34,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/builder" ) func Test_resourceKey(t *testing.T) { diff --git a/pkg/backup/item_collector.go b/pkg/backup/item_collector.go index 17b71a8c1..3dace71fd 100644 --- a/pkg/backup/item_collector.go +++ b/pkg/backup/item_collector.go @@ -35,11 +35,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/client-go/tools/pager" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) // itemCollector collects items from the Kubernetes API according to @@ -150,7 +150,7 @@ func (nt *nsTracker) init( // Skip the backup when the backup's namespace filter has // default value, and the namespace doesn't match backup // LabelSelector and OrLabelSelector. - // https://github.com/velero-io/velero/issues/7105 + // https://github.com/vmware-tanzu/velero/issues/7105 if nt.namespaceFilter.IncludeEverything() && (nt.singleLabelSelector != nil || len(nt.orLabelSelector) > 0) { continue diff --git a/pkg/backup/item_collector_test.go b/pkg/backup/item_collector_test.go index 2349994ee..54e2ed4c3 100644 --- a/pkg/backup/item_collector_test.go +++ b/pkg/backup/item_collector_test.go @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/collections" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) func TestSortCoreGroup(t *testing.T) { diff --git a/pkg/backup/itemblock.go b/pkg/backup/itemblock.go index 81febefd4..dee553f72 100644 --- a/pkg/backup/itemblock.go +++ b/pkg/backup/itemblock.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/pkg/itemblock" + "github.com/vmware-tanzu/velero/pkg/itemblock" ) type BackupItemBlock struct { diff --git a/pkg/backup/request.go b/pkg/backup/request.go index eb712387e..ca2e638c2 100644 --- a/pkg/backup/request.go +++ b/pkg/backup/request.go @@ -22,13 +22,13 @@ import ( "github.com/gobwas/glob" "k8s.io/apimachinery/pkg/labels" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) type itemKey struct { diff --git a/pkg/backup/snapshots.go b/pkg/backup/snapshots.go index a06e74413..c77e1cd6e 100644 --- a/pkg/backup/snapshots.go +++ b/pkg/backup/snapshots.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/util/sets" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/util/boolptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) // GetBackupCSIResources is used to get CSI snapshot related resources. diff --git a/pkg/backup/volume_snapshotter_cache.go b/pkg/backup/volume_snapshotter_cache.go index 0c72a03f2..620ebc337 100644 --- a/pkg/backup/volume_snapshotter_cache.go +++ b/pkg/backup/volume_snapshotter_cache.go @@ -3,8 +3,8 @@ package backup import ( "sync" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" ) type VolumeSnapshotterCache struct { diff --git a/pkg/builder/backup_builder.go b/pkg/builder/backup_builder.go index a5e368c1b..d5b955e43 100644 --- a/pkg/builder/backup_builder.go +++ b/pkg/builder/backup_builder.go @@ -23,13 +23,13 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/internal/resourcepolicies" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) /* diff --git a/pkg/builder/backup_storage_location_builder.go b/pkg/builder/backup_storage_location_builder.go index d1d5ef25a..33becd2a7 100644 --- a/pkg/builder/backup_storage_location_builder.go +++ b/pkg/builder/backup_storage_location_builder.go @@ -22,7 +22,7 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // BackupStorageLocationBuilder builds BackupStorageLocation objects. diff --git a/pkg/builder/container_builder.go b/pkg/builder/container_builder.go index 64275cc7c..762462c86 100644 --- a/pkg/builder/container_builder.go +++ b/pkg/builder/container_builder.go @@ -23,7 +23,7 @@ import ( corev1api "k8s.io/api/core/v1" apimachineryRuntime "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/label" ) // ContainerBuilder builds Container objects diff --git a/pkg/builder/container_builder_test.go b/pkg/builder/container_builder_test.go index b8f57eb15..b23cbddfd 100644 --- a/pkg/builder/container_builder_test.go +++ b/pkg/builder/container_builder_test.go @@ -89,8 +89,8 @@ func TestGetName(t *testing.T) { }, { name: "pull by digest", - image: "quay.io/velero-io/velero@sha256:a75f9e8c3ced3943515f249597be389f8233e1258d289b11184796edceaa7dab", - expected: "velero-io-velero", + image: "quay.io/vmware-tanzu/velero@sha256:a75f9e8c3ced3943515f249597be389f8233e1258d289b11184796edceaa7dab", + expected: "vmware-tanzu-velero", }, } diff --git a/pkg/builder/data_download_builder.go b/pkg/builder/data_download_builder.go index f219275cb..20cea868f 100644 --- a/pkg/builder/data_download_builder.go +++ b/pkg/builder/data_download_builder.go @@ -19,8 +19,8 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) // DataDownloadBuilder builds DataDownload objects. diff --git a/pkg/builder/data_upload_builder.go b/pkg/builder/data_upload_builder.go index 0ef01f66d..c8fa34956 100644 --- a/pkg/builder/data_upload_builder.go +++ b/pkg/builder/data_upload_builder.go @@ -19,8 +19,8 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) // DataUploadBuilder builds DataUpload objects diff --git a/pkg/builder/delete_backup_request_builder.go b/pkg/builder/delete_backup_request_builder.go index aa3fd1f9c..c0dfdbdbf 100644 --- a/pkg/builder/delete_backup_request_builder.go +++ b/pkg/builder/delete_backup_request_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // DeleteBackupRequestBuilder builds DeleteBackupRequest objects diff --git a/pkg/builder/download_request_builder.go b/pkg/builder/download_request_builder.go index cca81db11..05d5c0daa 100644 --- a/pkg/builder/download_request_builder.go +++ b/pkg/builder/download_request_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // DownloadRequestBuilder builds DownloadRequest objects. diff --git a/pkg/builder/item_operation_builder.go b/pkg/builder/item_operation_builder.go index b76de79b2..210752b82 100644 --- a/pkg/builder/item_operation_builder.go +++ b/pkg/builder/item_operation_builder.go @@ -22,8 +22,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // OperationStatusBuilder builds OperationStatus objects diff --git a/pkg/builder/pod_volume_backup_builder.go b/pkg/builder/pod_volume_backup_builder.go index dbcc72c9a..9db8beacd 100644 --- a/pkg/builder/pod_volume_backup_builder.go +++ b/pkg/builder/pod_volume_backup_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // PodVolumeBackupBuilder builds PodVolumeBackup objects diff --git a/pkg/builder/pod_volume_restore_builder.go b/pkg/builder/pod_volume_restore_builder.go index 02108cb4a..50f277eac 100644 --- a/pkg/builder/pod_volume_restore_builder.go +++ b/pkg/builder/pod_volume_restore_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // PodVolumeRestoreBuilder builds PodVolumeRestore objects. diff --git a/pkg/builder/restore_builder.go b/pkg/builder/restore_builder.go index 168136552..bad4327e9 100644 --- a/pkg/builder/restore_builder.go +++ b/pkg/builder/restore_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // RestoreBuilder builds Restore objects. diff --git a/pkg/builder/schedule_builder.go b/pkg/builder/schedule_builder.go index ef9e03a1a..7c9a9b1d9 100644 --- a/pkg/builder/schedule_builder.go +++ b/pkg/builder/schedule_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // ScheduleBuilder builds Schedule objects. diff --git a/pkg/builder/server_status_request_builder.go b/pkg/builder/server_status_request_builder.go index 80fc8078c..bc8876718 100644 --- a/pkg/builder/server_status_request_builder.go +++ b/pkg/builder/server_status_request_builder.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // ServerStatusRequestBuilder builds ServerStatusRequest objects. diff --git a/pkg/builder/testcr_builder.go b/pkg/builder/testcr_builder.go index 02da95b73..85bc83b1c 100644 --- a/pkg/builder/testcr_builder.go +++ b/pkg/builder/testcr_builder.go @@ -19,7 +19,7 @@ package builder import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // CustomResourceBuilder builds objects based on velero APIVersion CRDs. diff --git a/pkg/builder/volume_snapshot_location_builder.go b/pkg/builder/volume_snapshot_location_builder.go index 848dff401..af94471e3 100644 --- a/pkg/builder/volume_snapshot_location_builder.go +++ b/pkg/builder/volume_snapshot_location_builder.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // VolumeSnapshotLocationBuilder builds VolumeSnapshotLocation objects. diff --git a/pkg/cbtservice/mocks/Service.go b/pkg/cbtservice/mocks/Service.go index 68016f393..f7a9567a8 100644 --- a/pkg/cbtservice/mocks/Service.go +++ b/pkg/cbtservice/mocks/Service.go @@ -8,7 +8,7 @@ import ( "context" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/cbtservice" + "github.com/vmware-tanzu/velero/pkg/cbtservice" ) // NewService creates a new instance of Service. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/client/client.go b/pkg/client/client.go index f37091b03..dccdc05fc 100644 --- a/pkg/client/client.go +++ b/pkg/client/client.go @@ -24,7 +24,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/clientcmd" - "github.com/velero-io/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/buildinfo" ) // Config returns a *rest.Config, using either the kubeconfig (if specified) or an in-cluster diff --git a/pkg/client/factory.go b/pkg/client/factory.go index 0590dff02..51dfb62c3 100644 --- a/pkg/client/factory.go +++ b/pkg/client/factory.go @@ -35,8 +35,8 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/rest" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) //go:generate mockery --name Factory diff --git a/pkg/cmd/cli/backup/backup.go b/pkg/cmd/cli/backup/backup.go index 147336bec..34a0f9e97 100644 --- a/pkg/cmd/cli/backup/backup.go +++ b/pkg/cmd/cli/backup/backup.go @@ -19,7 +19,7 @@ package backup import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backup/backup_test.go b/pkg/cmd/cli/backup/backup_test.go index 1b8e8ecf7..0c316ca8c 100644 --- a/pkg/cmd/cli/backup/backup_test.go +++ b/pkg/cmd/cli/backup/backup_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" ) func TestNewBackupCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/create.go b/pkg/cmd/cli/backup/create.go index c15a95cc9..31564aae8 100644 --- a/pkg/cmd/cli/backup/create.go +++ b/pkg/cmd/cli/backup/create.go @@ -28,14 +28,14 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/create_test.go b/pkg/cmd/cli/backup/create_test.go index 5709e912e..c8fd15baa 100644 --- a/pkg/cmd/cli/backup/create_test.go +++ b/pkg/cmd/cli/backup/create_test.go @@ -33,12 +33,12 @@ import ( controllerclient "sigs.k8s.io/controller-runtime/pkg/client" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - "github.com/velero-io/velero/pkg/test" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestCreateOptions_BuildBackup(t *testing.T) { diff --git a/pkg/cmd/cli/backup/delete.go b/pkg/cmd/cli/backup/delete.go index afacf53f8..692b82dbf 100644 --- a/pkg/cmd/cli/backup/delete.go +++ b/pkg/cmd/cli/backup/delete.go @@ -27,13 +27,13 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" - "github.com/velero-io/velero/pkg/cmd/util/confirm" - "github.com/velero-io/velero/pkg/label" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + "github.com/vmware-tanzu/velero/pkg/label" ) // NewDeleteCommand creates a new command that deletes a backup. diff --git a/pkg/cmd/cli/backup/delete_test.go b/pkg/cmd/cli/backup/delete_test.go index a0954127f..3278e8153 100644 --- a/pkg/cmd/cli/backup/delete_test.go +++ b/pkg/cmd/cli/backup/delete_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/cmd/cli" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/describe.go b/pkg/cmd/cli/backup/describe.go index 35b910085..b0ef4a93e 100644 --- a/pkg/cmd/cli/backup/describe.go +++ b/pkg/cmd/cli/backup/describe.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" - "github.com/velero-io/velero/pkg/label" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/label" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/describe_test.go b/pkg/cmd/cli/backup/describe_test.go index 9a22d6da7..5d5486473 100644 --- a/pkg/cmd/cli/backup/describe_test.go +++ b/pkg/cmd/cli/backup/describe_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/client-go/rest" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewDescribeCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/download.go b/pkg/cmd/cli/backup/download.go index 2c2d1b0cc..8bb973ff0 100644 --- a/pkg/cmd/cli/backup/download.go +++ b/pkg/cmd/cli/backup/download.go @@ -28,11 +28,11 @@ import ( "github.com/spf13/pflag" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" ) func NewDownloadCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backup/download_test.go b/pkg/cmd/cli/backup/download_test.go index 921cc9174..999799ff3 100644 --- a/pkg/cmd/cli/backup/download_test.go +++ b/pkg/cmd/cli/backup/download_test.go @@ -27,11 +27,11 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewDownloadCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/get.go b/pkg/cmd/cli/backup/get.go index 81a6d3028..159fac30d 100644 --- a/pkg/cmd/cli/backup/get.go +++ b/pkg/cmd/cli/backup/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backup/get_test.go b/pkg/cmd/cli/backup/get_test.go index c0d587eb0..28c41a6de 100644 --- a/pkg/cmd/cli/backup/get_test.go +++ b/pkg/cmd/cli/backup/get_test.go @@ -27,11 +27,11 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backup/logs.go b/pkg/cmd/cli/backup/logs.go index 62ec71942..a0149acf1 100644 --- a/pkg/cmd/cli/backup/logs.go +++ b/pkg/cmd/cli/backup/logs.go @@ -27,11 +27,11 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" ) type LogsOptions struct { diff --git a/pkg/cmd/cli/backup/logs_test.go b/pkg/cmd/cli/backup/logs_test.go index 598ca06f4..87e100732 100644 --- a/pkg/cmd/cli/backup/logs_test.go +++ b/pkg/cmd/cli/backup/logs_test.go @@ -33,12 +33,12 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewLogsCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/backup_location.go b/pkg/cmd/cli/backuplocation/backup_location.go index 3b8d28fb0..f008b2a1e 100644 --- a/pkg/cmd/cli/backuplocation/backup_location.go +++ b/pkg/cmd/cli/backuplocation/backup_location.go @@ -19,7 +19,7 @@ package backuplocation import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/backup_location_test.go b/pkg/cmd/cli/backuplocation/backup_location_test.go index 735cbbfd3..7fc73d63d 100644 --- a/pkg/cmd/cli/backuplocation/backup_location_test.go +++ b/pkg/cmd/cli/backuplocation/backup_location_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" ) func TestNewCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/create.go b/pkg/cmd/cli/backuplocation/create.go index 191bc64d0..343bc790a 100644 --- a/pkg/cmd/cli/backuplocation/create.go +++ b/pkg/cmd/cli/backuplocation/create.go @@ -31,13 +31,13 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/storage" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/create_test.go b/pkg/cmd/cli/backuplocation/create_test.go index aa0f88f9e..25d5b2cd6 100644 --- a/pkg/cmd/cli/backuplocation/create_test.go +++ b/pkg/cmd/cli/backuplocation/create_test.go @@ -30,9 +30,9 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" - velerotest "github.com/velero-io/velero/pkg/test" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBuildBackupStorageLocationSetsNamespace(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/delete.go b/pkg/cmd/cli/backuplocation/delete.go index 4ffde572c..f2c3bcc3d 100644 --- a/pkg/cmd/cli/backuplocation/delete.go +++ b/pkg/cmd/cli/backuplocation/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" - "github.com/velero-io/velero/pkg/cmd/util/confirm" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting backup-locations. diff --git a/pkg/cmd/cli/backuplocation/delete_test.go b/pkg/cmd/cli/backuplocation/delete_test.go index 9c524e1a3..70ff7568b 100644 --- a/pkg/cmd/cli/backuplocation/delete_test.go +++ b/pkg/cmd/cli/backuplocation/delete_test.go @@ -27,12 +27,12 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/cmd/cli" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/get.go b/pkg/cmd/cli/backuplocation/get.go index 58090212f..fd7c057c2 100644 --- a/pkg/cmd/cli/backuplocation/get.go +++ b/pkg/cmd/cli/backuplocation/get.go @@ -24,10 +24,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/get_test.go b/pkg/cmd/cli/backuplocation/get_test.go index 6887a674e..d45231fce 100644 --- a/pkg/cmd/cli/backuplocation/get_test.go +++ b/pkg/cmd/cli/backuplocation/get_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/backuplocation/set.go b/pkg/cmd/cli/backuplocation/set.go index 1ece5ff82..8aa018e29 100644 --- a/pkg/cmd/cli/backuplocation/set.go +++ b/pkg/cmd/cli/backuplocation/set.go @@ -28,13 +28,13 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/storage" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) func NewSetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/backuplocation/set_test.go b/pkg/cmd/cli/backuplocation/set_test.go index efd24c7f1..0ebf8a8d3 100644 --- a/pkg/cmd/cli/backuplocation/set_test.go +++ b/pkg/cmd/cli/backuplocation/set_test.go @@ -28,12 +28,12 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewSetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/bug/bug.go b/pkg/cmd/cli/bug/bug.go index 54836a3b6..33fbb38b7 100644 --- a/pkg/cmd/cli/bug/bug.go +++ b/pkg/cmd/cli/bug/bug.go @@ -31,16 +31,16 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/features" ) const ( // kubectlTimeout is how long we wait in seconds for `kubectl version` // before killing the process kubectlTimeout = 5 * time.Second - issueURL = "https://github.com/velero-io/velero/issues/new" + issueURL = "https://github.com/vmware-tanzu/velero/issues/new" // IssueTemplate is used to generate .github/ISSUE_TEMPLATE/bug_report.md // as well as the initial text that's place in a new Github issue as // the result of running `velero bug`. @@ -95,7 +95,7 @@ Please provide the output of the following commands (Pasting long output into a **Vote on this issue!** -This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/velero-io/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). +This is an invitation to the Velero community to vote on issues, you can see the project's [top voted issues listed here](https://github.com/vmware-tanzu/velero/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). Use the "reaction smiley face" up to the right of this comment to vote. - :+1: for "I would like to see this bug fixed as soon as possible" diff --git a/pkg/cmd/cli/client/client.go b/pkg/cmd/cli/client/client.go index 75f996c6a..5d0650b10 100644 --- a/pkg/cmd/cli/client/client.go +++ b/pkg/cmd/cli/client/client.go @@ -19,7 +19,7 @@ package client import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/cmd/cli/client/config" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/client/config" ) func NewCommand() *cobra.Command { diff --git a/pkg/cmd/cli/client/config/get.go b/pkg/cmd/cli/client/config/get.go index a1c70382b..f69a8cadf 100644 --- a/pkg/cmd/cli/client/config/get.go +++ b/pkg/cmd/cli/client/config/get.go @@ -22,8 +22,8 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" ) func NewGetCommand() *cobra.Command { diff --git a/pkg/cmd/cli/client/config/set.go b/pkg/cmd/cli/client/config/set.go index afcb34c96..229ca1553 100644 --- a/pkg/cmd/cli/client/config/set.go +++ b/pkg/cmd/cli/client/config/set.go @@ -23,8 +23,8 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" ) func NewSetCommand() *cobra.Command { diff --git a/pkg/cmd/cli/create/create.go b/pkg/cmd/cli/create/create.go index 07ed10eef..e158d1560 100644 --- a/pkg/cmd/cli/create/create.go +++ b/pkg/cmd/cli/create/create.go @@ -19,12 +19,12 @@ package create import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" - "github.com/velero-io/velero/pkg/cmd/cli/restore" - "github.com/velero-io/velero/pkg/cmd/cli/schedule" - "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/datamover/backup.go b/pkg/cmd/cli/datamover/backup.go index 8b266bc0a..2b647bb24 100644 --- a/pkg/cmd/cli/datamover/backup.go +++ b/pkg/cmd/cli/datamover/backup.go @@ -30,22 +30,22 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/klog/v2" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/datamover" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/datamover" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/datamover/backup_test.go b/pkg/cmd/cli/datamover/backup_test.go index fc91f3910..2dd1e681d 100644 --- a/pkg/cmd/cli/datamover/backup_test.go +++ b/pkg/cmd/cli/datamover/backup_test.go @@ -24,10 +24,10 @@ import ( "github.com/stretchr/testify/mock" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/internal/credentials" + cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) func fakeCreateDataPathServiceWithErr(_ *dataMoverBackup) (dataPathService, error) { diff --git a/pkg/cmd/cli/datamover/data_mover.go b/pkg/cmd/cli/datamover/data_mover.go index e56bdb6b6..265d57bd8 100644 --- a/pkg/cmd/cli/datamover/data_mover.go +++ b/pkg/cmd/cli/datamover/data_mover.go @@ -18,7 +18,7 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/datamover/restore.go b/pkg/cmd/cli/datamover/restore.go index d6091c9f1..b2efdbc34 100644 --- a/pkg/cmd/cli/datamover/restore.go +++ b/pkg/cmd/cli/datamover/restore.go @@ -31,19 +31,19 @@ import ( "k8s.io/klog/v2" ctrl "sigs.k8s.io/controller-runtime" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/datamover" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/datamover" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/datamover/restore_test.go b/pkg/cmd/cli/datamover/restore_test.go index 8fbc44fec..664c2bdbc 100644 --- a/pkg/cmd/cli/datamover/restore_test.go +++ b/pkg/cmd/cli/datamover/restore_test.go @@ -20,8 +20,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func fakeCreateDataPathRestoreWithErr(_ *dataMoverRestore) (dataPathService, error) { diff --git a/pkg/cmd/cli/debug/debug.go b/pkg/cmd/cli/debug/debug.go index a2f92a313..400eddde1 100644 --- a/pkg/cmd/cli/debug/debug.go +++ b/pkg/cmd/cli/debug/debug.go @@ -35,9 +35,9 @@ import ( "k8s.io/client-go/tools/clientcmd" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" ) //go:embed cshd-scripts/velero.cshd diff --git a/pkg/cmd/cli/delete/delete.go b/pkg/cmd/cli/delete/delete.go index 389247a59..1eb910307 100644 --- a/pkg/cmd/cli/delete/delete.go +++ b/pkg/cmd/cli/delete/delete.go @@ -19,11 +19,11 @@ package delete import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" - "github.com/velero-io/velero/pkg/cmd/cli/restore" - "github.com/velero-io/velero/pkg/cmd/cli/schedule" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/delete_options.go b/pkg/cmd/cli/delete_options.go index b6b923945..78c7ae337 100644 --- a/pkg/cmd/cli/delete_options.go +++ b/pkg/cmd/cli/delete_options.go @@ -23,8 +23,8 @@ import ( "github.com/spf13/pflag" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/util/confirm" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" ) // DeleteOptions contains parameters used for deleting a restore. diff --git a/pkg/cmd/cli/describe/describe.go b/pkg/cmd/cli/describe/describe.go index b7c93d78f..9f45260fa 100644 --- a/pkg/cmd/cli/describe/describe.go +++ b/pkg/cmd/cli/describe/describe.go @@ -19,10 +19,10 @@ package describe import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/cli/restore" - "github.com/velero-io/velero/pkg/cmd/cli/schedule" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/get/get.go b/pkg/cmd/cli/get/get.go index e12abe08c..24ad16afb 100644 --- a/pkg/cmd/cli/get/get.go +++ b/pkg/cmd/cli/get/get.go @@ -19,13 +19,13 @@ package get import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" - "github.com/velero-io/velero/pkg/cmd/cli/plugin" - "github.com/velero-io/velero/pkg/cmd/cli/restore" - "github.com/velero-io/velero/pkg/cmd/cli/schedule" - "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/plugin" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/install/install.go b/pkg/cmd/cli/install/install.go index 01ef58f75..8115e1353 100644 --- a/pkg/cmd/cli/install/install.go +++ b/pkg/cmd/cli/install/install.go @@ -28,16 +28,16 @@ import ( "github.com/spf13/pflag" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/velero" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" - "github.com/velero-io/velero/pkg/install" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/install" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) // Options collects all the options for installing Velero into a Kubernetes cluster. diff --git a/pkg/cmd/cli/install/install_test.go b/pkg/cmd/cli/install/install_test.go index 2a0572db2..1e0e7a4cf 100644 --- a/pkg/cmd/cli/install/install_test.go +++ b/pkg/cmd/cli/install/install_test.go @@ -27,8 +27,8 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestPriorityClassNameFlag(t *testing.T) { diff --git a/pkg/cmd/cli/nodeagent/node_agent.go b/pkg/cmd/cli/nodeagent/node_agent.go index 96a46b4a7..7b0b6ebf0 100644 --- a/pkg/cmd/cli/nodeagent/node_agent.go +++ b/pkg/cmd/cli/nodeagent/node_agent.go @@ -19,7 +19,7 @@ package nodeagent import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/nodeagent/server.go b/pkg/cmd/cli/nodeagent/server.go index ed9aa1adb..bb1764cb3 100644 --- a/pkg/cmd/cli/nodeagent/server.go +++ b/pkg/cmd/cli/nodeagent/server.go @@ -47,23 +47,23 @@ import ( ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/manager" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/controller" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/nodeagent" - repository "github.com/velero-io/velero/pkg/repository/manager" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/controller" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + repository "github.com/vmware-tanzu/velero/pkg/repository/manager" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) var ( diff --git a/pkg/cmd/cli/nodeagent/server_test.go b/pkg/cmd/cli/nodeagent/server_test.go index 5ddb3bfe5..152016ab6 100644 --- a/pkg/cmd/cli/nodeagent/server_test.go +++ b/pkg/cmd/cli/nodeagent/server_test.go @@ -31,12 +31,12 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/kubernetes/fake" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/nodeagent" - testutil "github.com/velero-io/velero/pkg/test" - velerotypes "github.com/velero-io/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + testutil "github.com/vmware-tanzu/velero/pkg/test" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func Test_validatePodVolumesHostPath(t *testing.T) { diff --git a/pkg/cmd/cli/plugin/add.go b/pkg/cmd/cli/plugin/add.go index 17f203227..9ea199fa9 100644 --- a/pkg/cmd/cli/plugin/add.go +++ b/pkg/cmd/cli/plugin/add.go @@ -29,11 +29,11 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/confirm" - "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" ) const ( diff --git a/pkg/cmd/cli/plugin/get.go b/pkg/cmd/cli/plugin/get.go index 45d91b741..60a939257 100644 --- a/pkg/cmd/cli/plugin/get.go +++ b/pkg/cmd/cli/plugin/get.go @@ -24,10 +24,10 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli/serverstatus" - "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/serverstatus" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/plugin/helpers.go b/pkg/cmd/cli/plugin/helpers.go index 328e7b063..28f681993 100644 --- a/pkg/cmd/cli/plugin/helpers.go +++ b/pkg/cmd/cli/plugin/helpers.go @@ -25,11 +25,11 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/client-go/kubernetes" - "github.com/velero-io/velero/pkg/install" + "github.com/vmware-tanzu/velero/pkg/install" ) // veleroDeployment returns a Velero deployment object, selected with label and container name, -// refer to https://github.com/velero-io/velero/issues/3961 for more information +// refer to https://github.com/vmware-tanzu/velero/issues/3961 for more information func veleroDeployment(ctx context.Context, kubeClient kubernetes.Interface, namespace string) (*appsv1api.Deployment, error) { veleroLabels := labels.FormatLabels(install.Labels()) diff --git a/pkg/cmd/cli/plugin/plugin.go b/pkg/cmd/cli/plugin/plugin.go index ee6cbee67..0ba2f6177 100644 --- a/pkg/cmd/cli/plugin/plugin.go +++ b/pkg/cmd/cli/plugin/plugin.go @@ -19,7 +19,7 @@ package plugin import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/plugin/remove.go b/pkg/cmd/cli/plugin/remove.go index 8983fa08e..ed25dc680 100644 --- a/pkg/cmd/cli/plugin/remove.go +++ b/pkg/cmd/cli/plugin/remove.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" ) func NewRemoveCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/podvolume/backup.go b/pkg/cmd/cli/podvolume/backup.go index a8c9f1fdc..ed2d6c09a 100644 --- a/pkg/cmd/cli/podvolume/backup.go +++ b/pkg/cmd/cli/podvolume/backup.go @@ -30,21 +30,21 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/klog/v2" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/podvolume/backup_test.go b/pkg/cmd/cli/podvolume/backup_test.go index 4ce5192d9..1c59af751 100644 --- a/pkg/cmd/cli/podvolume/backup_test.go +++ b/pkg/cmd/cli/podvolume/backup_test.go @@ -24,10 +24,10 @@ import ( "github.com/stretchr/testify/mock" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/internal/credentials" + cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) func fakeCreateDataPathServiceWithErr(_ *podVolumeBackup) (dataPathService, error) { diff --git a/pkg/cmd/cli/podvolume/podvolume.go b/pkg/cmd/cli/podvolume/podvolume.go index 480538f1a..998e4683a 100644 --- a/pkg/cmd/cli/podvolume/podvolume.go +++ b/pkg/cmd/cli/podvolume/podvolume.go @@ -18,7 +18,7 @@ import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/podvolume/restore.go b/pkg/cmd/cli/podvolume/restore.go index 3be43e731..4c1596a04 100644 --- a/pkg/cmd/cli/podvolume/restore.go +++ b/pkg/cmd/cli/podvolume/restore.go @@ -31,18 +31,18 @@ import ( "k8s.io/klog/v2" ctrl "sigs.k8s.io/controller-runtime" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ctlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctlclient "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/cmd/cli/podvolume/restore_test.go b/pkg/cmd/cli/podvolume/restore_test.go index 3bc688781..74fbb8090 100644 --- a/pkg/cmd/cli/podvolume/restore_test.go +++ b/pkg/cmd/cli/podvolume/restore_test.go @@ -20,8 +20,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" - cacheMock "github.com/velero-io/velero/pkg/cmd/cli/datamover/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + cacheMock "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func fakeCreateRestoreDataPathServiceWithErr(_ *podVolumeRestore) (dataPathService, error) { diff --git a/pkg/cmd/cli/repo/get.go b/pkg/cmd/cli/repo/get.go index adf4bbb66..ec57b9845 100644 --- a/pkg/cmd/cli/repo/get.go +++ b/pkg/cmd/cli/repo/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/repo/repo.go b/pkg/cmd/cli/repo/repo.go index 7c193c434..957dad793 100644 --- a/pkg/cmd/cli/repo/repo.go +++ b/pkg/cmd/cli/repo/repo.go @@ -19,7 +19,7 @@ package repo import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/repomantenance/maintenance.go b/pkg/cmd/cli/repomantenance/maintenance.go index 4cdcd4ddd..46c54f7d2 100644 --- a/pkg/cmd/cli/repomantenance/maintenance.go +++ b/pkg/cmd/cli/repomantenance/maintenance.go @@ -18,16 +18,16 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerocli "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerocli "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/logging" - repokey "github.com/velero-io/velero/pkg/repository/keys" - "github.com/velero-io/velero/pkg/repository/maintenance" - repomanager "github.com/velero-io/velero/pkg/repository/manager" + repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" + "github.com/vmware-tanzu/velero/pkg/repository/maintenance" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" ) type Options struct { diff --git a/pkg/cmd/cli/restore/create.go b/pkg/cmd/cli/restore/create.go index 1bc04224b..2fb21433e 100644 --- a/pkg/cmd/cli/restore/create.go +++ b/pkg/cmd/cli/restore/create.go @@ -31,15 +31,15 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/resourcemodifiers" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/velero/restore" + "github.com/vmware-tanzu/velero/internal/resourcemodifiers" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/velero/restore" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/create_test.go b/pkg/cmd/cli/restore/create_test.go index 6f7344555..8cc369dea 100644 --- a/pkg/cmd/cli/restore/create_test.go +++ b/pkg/cmd/cli/restore/create_test.go @@ -26,11 +26,11 @@ import ( controllerclient "sigs.k8s.io/controller-runtime/pkg/client" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestMostRecentBackup(t *testing.T) { diff --git a/pkg/cmd/cli/restore/delete.go b/pkg/cmd/cli/restore/delete.go index 41e4eb0dc..a2e70953d 100644 --- a/pkg/cmd/cli/restore/delete.go +++ b/pkg/cmd/cli/restore/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" - "github.com/velero-io/velero/pkg/cmd/util/confirm" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting restores. diff --git a/pkg/cmd/cli/restore/delete_test.go b/pkg/cmd/cli/restore/delete_test.go index fd6b778a7..e98f9b804 100644 --- a/pkg/cmd/cli/restore/delete_test.go +++ b/pkg/cmd/cli/restore/delete_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/cmd/cli" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestDeleteCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/describe.go b/pkg/cmd/cli/restore/describe.go index 939b359f6..6404ef21d 100644 --- a/pkg/cmd/cli/restore/describe.go +++ b/pkg/cmd/cli/restore/describe.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" - "github.com/velero-io/velero/pkg/label" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/pkg/label" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/describe_test.go b/pkg/cmd/cli/restore/describe_test.go index 43c32cb72..7c2ffe5f8 100644 --- a/pkg/cmd/cli/restore/describe_test.go +++ b/pkg/cmd/cli/restore/describe_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/client-go/rest" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewDescribeCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/get.go b/pkg/cmd/cli/restore/get.go index ebacf90cc..9a4014b25 100644 --- a/pkg/cmd/cli/restore/get.go +++ b/pkg/cmd/cli/restore/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/restore/get_test.go b/pkg/cmd/cli/restore/get_test.go index 3c63e0466..22b10e152 100644 --- a/pkg/cmd/cli/restore/get_test.go +++ b/pkg/cmd/cli/restore/get_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - velerotest "github.com/velero-io/velero/pkg/test" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func TestNewGetCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/logs.go b/pkg/cmd/cli/restore/logs.go index e11fc591f..f4315c917 100644 --- a/pkg/cmd/cli/restore/logs.go +++ b/pkg/cmd/cli/restore/logs.go @@ -26,11 +26,11 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" ) func NewLogsCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/restore/logs_test.go b/pkg/cmd/cli/restore/logs_test.go index a06fc0d93..61c2392b6 100644 --- a/pkg/cmd/cli/restore/logs_test.go +++ b/pkg/cmd/cli/restore/logs_test.go @@ -25,12 +25,12 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - cmdtest "github.com/velero-io/velero/pkg/cmd/test" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + cmdtest "github.com/vmware-tanzu/velero/pkg/cmd/test" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewLogsCommand(t *testing.T) { diff --git a/pkg/cmd/cli/restore/restore.go b/pkg/cmd/cli/restore/restore.go index 8ee152b19..728c800ed 100644 --- a/pkg/cmd/cli/restore/restore.go +++ b/pkg/cmd/cli/restore/restore.go @@ -19,7 +19,7 @@ package restore import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/restore/restore_test.go b/pkg/cmd/cli/restore/restore_test.go index 1820882e1..85f4b662a 100644 --- a/pkg/cmd/cli/restore/restore_test.go +++ b/pkg/cmd/cli/restore/restore_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" ) func TestNewRestoreCommand(t *testing.T) { diff --git a/pkg/cmd/cli/schedule/create.go b/pkg/cmd/cli/schedule/create.go index 29b9bffe3..47c19318f 100644 --- a/pkg/cmd/cli/schedule/create.go +++ b/pkg/cmd/cli/schedule/create.go @@ -26,12 +26,12 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/internal/resourcepolicies" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/util/output" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/delete.go b/pkg/cmd/cli/schedule/delete.go index a6dd9b284..77b0bf883 100644 --- a/pkg/cmd/cli/schedule/delete.go +++ b/pkg/cmd/cli/schedule/delete.go @@ -27,11 +27,11 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" controllerclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" - "github.com/velero-io/velero/pkg/cmd/util/confirm" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" ) // NewDeleteCommand creates and returns a new cobra command for deleting schedules. diff --git a/pkg/cmd/cli/schedule/describe.go b/pkg/cmd/cli/schedule/describe.go index 39b86ec61..82c88dac7 100644 --- a/pkg/cmd/cli/schedule/describe.go +++ b/pkg/cmd/cli/schedule/describe.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewDescribeCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/get.go b/pkg/cmd/cli/schedule/get.go index 2b9c5564b..88bd49fe0 100644 --- a/pkg/cmd/cli/schedule/get.go +++ b/pkg/cmd/cli/schedule/get.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/labels" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/pause.go b/pkg/cmd/cli/schedule/pause.go index 24b11ed03..820e887a7 100644 --- a/pkg/cmd/cli/schedule/pause.go +++ b/pkg/cmd/cli/schedule/pause.go @@ -28,10 +28,10 @@ import ( kubeerrs "k8s.io/apimachinery/pkg/util/errors" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" ) // NewPauseCommand creates the command for pause diff --git a/pkg/cmd/cli/schedule/schedule.go b/pkg/cmd/cli/schedule/schedule.go index 91eb5e2c7..85c51c399 100644 --- a/pkg/cmd/cli/schedule/schedule.go +++ b/pkg/cmd/cli/schedule/schedule.go @@ -19,7 +19,7 @@ package schedule import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/schedule/skip_options.go b/pkg/cmd/cli/schedule/skip_options.go index a425e23af..14ea1b4ce 100644 --- a/pkg/cmd/cli/schedule/skip_options.go +++ b/pkg/cmd/cli/schedule/skip_options.go @@ -3,7 +3,7 @@ package schedule import ( "github.com/spf13/pflag" - "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" ) type SkipOptions struct { diff --git a/pkg/cmd/cli/schedule/unpause.go b/pkg/cmd/cli/schedule/unpause.go index bb1278cb8..72197a934 100644 --- a/pkg/cmd/cli/schedule/unpause.go +++ b/pkg/cmd/cli/schedule/unpause.go @@ -19,9 +19,9 @@ package schedule import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli" ) // NewUnpauseCommand creates the command for unpause diff --git a/pkg/cmd/cli/select_option.go b/pkg/cmd/cli/select_option.go index 5dab105f0..b0f18f4ef 100644 --- a/pkg/cmd/cli/select_option.go +++ b/pkg/cmd/cli/select_option.go @@ -23,7 +23,7 @@ import ( "golang.org/x/text/cases" "golang.org/x/text/language" - "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" ) // SelectOptions defines the options for selecting resources diff --git a/pkg/cmd/cli/select_option_test.go b/pkg/cmd/cli/select_option_test.go index c53ca759a..ea726bd4e 100644 --- a/pkg/cmd/cli/select_option_test.go +++ b/pkg/cmd/cli/select_option_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" ) func TestCompleteOfSelectOption(t *testing.T) { diff --git a/pkg/cmd/cli/serverstatus/server_status.go b/pkg/cmd/cli/serverstatus/server_status.go index 885ed3078..ab994e2d6 100644 --- a/pkg/cmd/cli/serverstatus/server_status.go +++ b/pkg/cmd/cli/serverstatus/server_status.go @@ -24,9 +24,9 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - veleroclient "github.com/velero-io/velero/pkg/client" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" ) type Getter interface { diff --git a/pkg/cmd/cli/snapshotlocation/create.go b/pkg/cmd/cli/snapshotlocation/create.go index 7cdb5fd56..db55ad834 100644 --- a/pkg/cmd/cli/snapshotlocation/create.go +++ b/pkg/cmd/cli/snapshotlocation/create.go @@ -25,12 +25,12 @@ import ( "github.com/spf13/pflag" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewCreateCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/get.go b/pkg/cmd/cli/snapshotlocation/get.go index 58ebf8eb3..2acddbf7f 100644 --- a/pkg/cmd/cli/snapshotlocation/get.go +++ b/pkg/cmd/cli/snapshotlocation/get.go @@ -23,10 +23,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/output" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewGetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/set.go b/pkg/cmd/cli/snapshotlocation/set.go index 9326db185..f6b8ac368 100644 --- a/pkg/cmd/cli/snapshotlocation/set.go +++ b/pkg/cmd/cli/snapshotlocation/set.go @@ -26,12 +26,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/cmd/util/output" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/output" ) func NewSetCommand(f client.Factory, use string) *cobra.Command { diff --git a/pkg/cmd/cli/snapshotlocation/snapshot_location.go b/pkg/cmd/cli/snapshotlocation/snapshot_location.go index 3993515c7..baebff451 100644 --- a/pkg/cmd/cli/snapshotlocation/snapshot_location.go +++ b/pkg/cmd/cli/snapshotlocation/snapshot_location.go @@ -19,7 +19,7 @@ package snapshotlocation import ( "github.com/spf13/cobra" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/uninstall/uninstall.go b/pkg/cmd/cli/uninstall/uninstall.go index 5968b5643..80a349c92 100644 --- a/pkg/cmd/cli/uninstall/uninstall.go +++ b/pkg/cmd/cli/uninstall/uninstall.go @@ -41,14 +41,14 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller/controllerutil" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/util/confirm" - "github.com/velero-io/velero/pkg/controller" - "github.com/velero-io/velero/pkg/install" - kubeutil "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/util/confirm" + "github.com/vmware-tanzu/velero/pkg/controller" + "github.com/vmware-tanzu/velero/pkg/install" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" ) var gracefulDeletionMaximumDuration = 1 * time.Minute @@ -213,7 +213,7 @@ func deleteNamespace(ctx context.Context, kbClient kbclient.Client, namespace st fmt.Print(".") } - // Must wait until the namespace is deleted to avoid the issue https://github.com/velero-io/velero/issues/3974 + // Must wait until the namespace is deleted to avoid the issue https://github.com/vmware-tanzu/velero/issues/3974 wait.Until(checkFunc, 5*time.Millisecond, ctx.Done()) if err != nil { return err diff --git a/pkg/cmd/cli/version/version.go b/pkg/cmd/cli/version/version.go index 57a42ece5..f8d261116 100644 --- a/pkg/cmd/cli/version/version.go +++ b/pkg/cmd/cli/version/version.go @@ -27,10 +27,10 @@ import ( "golang.org/x/mod/semver" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/cli/serverstatus" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/serverstatus" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/cli/version/version_test.go b/pkg/cmd/cli/version/version_test.go index cb629653d..355626802 100644 --- a/pkg/cmd/cli/version/version_test.go +++ b/pkg/cmd/cli/version/version_test.go @@ -26,10 +26,10 @@ import ( "github.com/stretchr/testify/mock" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/buildinfo" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestPrintVersion(t *testing.T) { diff --git a/pkg/cmd/server/config/config.go b/pkg/cmd/server/config/config.go index b2802edb1..e19086217 100644 --- a/pkg/cmd/server/config/config.go +++ b/pkg/cmd/server/config/config.go @@ -5,18 +5,18 @@ import ( "strings" "time" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" "github.com/sirupsen/logrus" "github.com/spf13/pflag" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/constant" - podvolumeconfigs "github.com/velero-io/velero/pkg/podvolume/configs" - "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/constant" + podvolumeconfigs "github.com/vmware-tanzu/velero/pkg/podvolume/configs" + "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) const ( diff --git a/pkg/cmd/server/plugin/plugin.go b/pkg/cmd/server/plugin/plugin.go index d706bde07..071f0bbe5 100644 --- a/pkg/cmd/server/plugin/plugin.go +++ b/pkg/cmd/server/plugin/plugin.go @@ -21,22 +21,22 @@ import ( "github.com/spf13/cobra" apiextensions "k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/datamover" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/datamover" - dia "github.com/velero-io/velero/internal/delete/actions/csi" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - bia "github.com/velero-io/velero/pkg/backup/actions" - csibia "github.com/velero-io/velero/pkg/backup/actions/csi" - "github.com/velero-io/velero/pkg/client" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - iba "github.com/velero-io/velero/pkg/itemblock/actions" - veleroplugin "github.com/velero-io/velero/pkg/plugin/framework" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - ria "github.com/velero-io/velero/pkg/restore/actions" - csiria "github.com/velero-io/velero/pkg/restore/actions/csi" - "github.com/velero-io/velero/pkg/util/actionhelpers" + dia "github.com/vmware-tanzu/velero/internal/delete/actions/csi" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + bia "github.com/vmware-tanzu/velero/pkg/backup/actions" + csibia "github.com/vmware-tanzu/velero/pkg/backup/actions/csi" + "github.com/vmware-tanzu/velero/pkg/client" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + iba "github.com/vmware-tanzu/velero/pkg/itemblock/actions" + veleroplugin "github.com/vmware-tanzu/velero/pkg/plugin/framework" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + ria "github.com/vmware-tanzu/velero/pkg/restore/actions" + csiria "github.com/vmware-tanzu/velero/pkg/restore/actions/csi" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/server/server.go b/pkg/cmd/server/server.go index ffcf6c7b4..44c88b980 100644 --- a/pkg/cmd/server/server.go +++ b/pkg/cmd/server/server.go @@ -55,38 +55,38 @@ import ( ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/manager" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/storage" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/backup" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd" - "github.com/velero-io/velero/pkg/cmd/server/config" - "github.com/velero-io/velero/pkg/cmd/util/signals" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/controller" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/podexec" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/repository" - repokey "github.com/velero-io/velero/pkg/repository/keys" - repomanager "github.com/velero-io/velero/pkg/repository/manager" - "github.com/velero-io/velero/pkg/restore" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/backup" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd" + "github.com/vmware-tanzu/velero/pkg/cmd/server/config" + "github.com/vmware-tanzu/velero/pkg/cmd/util/signals" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/controller" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/podexec" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/repository" + repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + "github.com/vmware-tanzu/velero/pkg/restore" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func NewCommand(f client.Factory) *cobra.Command { diff --git a/pkg/cmd/server/server_test.go b/pkg/cmd/server/server_test.go index 5ffacb436..c602f7c9e 100644 --- a/pkg/cmd/server/server_test.go +++ b/pkg/cmd/server/server_test.go @@ -31,15 +31,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/cmd/server/config" - "github.com/velero-io/velero/pkg/constant" - discovery_mocks "github.com/velero-io/velero/pkg/discovery/mocks" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/cmd/server/config" + "github.com/vmware-tanzu/velero/pkg/constant" + discovery_mocks "github.com/vmware-tanzu/velero/pkg/discovery/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" ) func TestVeleroResourcesExist(t *testing.T) { diff --git a/pkg/cmd/util/cacert/bsl_cacert.go b/pkg/cmd/util/cacert/bsl_cacert.go index fe202bb84..d11729945 100644 --- a/pkg/cmd/util/cacert/bsl_cacert.go +++ b/pkg/cmd/util/cacert/bsl_cacert.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/types" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // GetCACertFromBackup fetches the BackupStorageLocation for a backup and returns its cacert diff --git a/pkg/cmd/util/cacert/bsl_cacert_test.go b/pkg/cmd/util/cacert/bsl_cacert_test.go index ac2f936ff..03e14b724 100644 --- a/pkg/cmd/util/cacert/bsl_cacert_test.go +++ b/pkg/cmd/util/cacert/bsl_cacert_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/util" ) func TestGetCACertFromBackup(t *testing.T) { diff --git a/pkg/cmd/util/downloadrequest/downloadrequest.go b/pkg/cmd/util/downloadrequest/downloadrequest.go index 8cdf6fbb7..6e1d30c37 100644 --- a/pkg/cmd/util/downloadrequest/downloadrequest.go +++ b/pkg/cmd/util/downloadrequest/downloadrequest.go @@ -32,8 +32,8 @@ import ( "github.com/pkg/errors" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroV1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" + veleroV1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" ) // ErrNotFound is exported for external packages to check for when a file is diff --git a/pkg/cmd/util/downloadrequest/downloadrequest_test.go b/pkg/cmd/util/downloadrequest/downloadrequest_test.go index 40372b614..995e83dc6 100644 --- a/pkg/cmd/util/downloadrequest/downloadrequest_test.go +++ b/pkg/cmd/util/downloadrequest/downloadrequest_test.go @@ -39,10 +39,10 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/util" ) // createSelfSignedCertificate creates a self-signed certificate for testing. diff --git a/pkg/cmd/util/output/backup_describer.go b/pkg/cmd/util/output/backup_describer.go index 24f4410be..e0637a4bd 100644 --- a/pkg/cmd/util/output/backup_describer.go +++ b/pkg/cmd/util/output/backup_describer.go @@ -34,15 +34,15 @@ import ( "github.com/fatih/color" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" - "github.com/velero-io/velero/pkg/itemoperation" + veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + "github.com/vmware-tanzu/velero/pkg/itemoperation" - "github.com/velero-io/velero/internal/volume" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/volume" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/results" ) // DescribeBackup describes a backup in human-readable format. diff --git a/pkg/cmd/util/output/backup_describer_test.go b/pkg/cmd/util/output/backup_describer_test.go index 9b4923404..0de03bdaa 100644 --- a/pkg/cmd/util/output/backup_describer_test.go +++ b/pkg/cmd/util/output/backup_describer_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" ) func TestDescribeUploaderConfig(t *testing.T) { diff --git a/pkg/cmd/util/output/backup_printer.go b/pkg/cmd/util/output/backup_printer.go index 4ffb8c929..873bc9fc3 100644 --- a/pkg/cmd/util/output/backup_printer.go +++ b/pkg/cmd/util/output/backup_printer.go @@ -27,7 +27,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/util/duration" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/backup_printer_test.go b/pkg/cmd/util/output/backup_printer_test.go index 6495e1058..1a00bf6c1 100644 --- a/pkg/cmd/util/output/backup_printer_test.go +++ b/pkg/cmd/util/output/backup_printer_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/assert" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestSortBackups(t *testing.T) { diff --git a/pkg/cmd/util/output/backup_repo_printer.go b/pkg/cmd/util/output/backup_repo_printer.go index 4da5b25ad..1e68cb949 100644 --- a/pkg/cmd/util/output/backup_repo_printer.go +++ b/pkg/cmd/util/output/backup_repo_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/backup_storage_location_printer.go b/pkg/cmd/util/output/backup_storage_location_printer.go index 6cb5cc010..90960ca52 100644 --- a/pkg/cmd/util/output/backup_storage_location_printer.go +++ b/pkg/cmd/util/output/backup_storage_location_printer.go @@ -20,8 +20,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd" ) var ( diff --git a/pkg/cmd/util/output/backup_structured_describer.go b/pkg/cmd/util/output/backup_structured_describer.go index d65560328..904afa34e 100644 --- a/pkg/cmd/util/output/backup_structured_describer.go +++ b/pkg/cmd/util/output/backup_structured_describer.go @@ -28,11 +28,11 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + "github.com/vmware-tanzu/velero/pkg/util/results" ) // DescribeBackupInSF describes a backup in structured format. diff --git a/pkg/cmd/util/output/backup_structured_describer_test.go b/pkg/cmd/util/output/backup_structured_describer_test.go index de7fa3278..c5ede1b36 100644 --- a/pkg/cmd/util/output/backup_structured_describer_test.go +++ b/pkg/cmd/util/output/backup_structured_describer_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestDescribeBackupInSF(t *testing.T) { diff --git a/pkg/cmd/util/output/output.go b/pkg/cmd/util/output/output.go index 7b1c02dcf..a0f8ce704 100644 --- a/pkg/cmd/util/output/output.go +++ b/pkg/cmd/util/output/output.go @@ -29,9 +29,9 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/cli-runtime/pkg/printers" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/util/encode" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/util/encode" ) const ( diff --git a/pkg/cmd/util/output/output_test.go b/pkg/cmd/util/output/output_test.go index 12fb5e74a..1d3d67ae3 100644 --- a/pkg/cmd/util/output/output_test.go +++ b/pkg/cmd/util/output/output_test.go @@ -6,7 +6,7 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" "testing" ) diff --git a/pkg/cmd/util/output/plugin_printer.go b/pkg/cmd/util/output/plugin_printer.go index 3566e777a..faa957314 100644 --- a/pkg/cmd/util/output/plugin_printer.go +++ b/pkg/cmd/util/output/plugin_printer.go @@ -21,7 +21,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/restore_describer.go b/pkg/cmd/util/output/restore_describer.go index b67fab071..a89943e74 100644 --- a/pkg/cmd/util/output/restore_describer.go +++ b/pkg/cmd/util/output/restore_describer.go @@ -25,7 +25,7 @@ import ( "sort" "strings" - "github.com/velero-io/velero/internal/volume" + "github.com/vmware-tanzu/velero/internal/volume" corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" @@ -33,12 +33,12 @@ import ( "github.com/fatih/color" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd/util/cacert" - "github.com/velero-io/velero/pkg/cmd/util/downloadrequest" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/results" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd/util/cacert" + "github.com/vmware-tanzu/velero/pkg/cmd/util/downloadrequest" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func DescribeRestore( diff --git a/pkg/cmd/util/output/restore_describer_test.go b/pkg/cmd/util/output/restore_describer_test.go index 3b92fc025..6348dfaf0 100644 --- a/pkg/cmd/util/output/restore_describer_test.go +++ b/pkg/cmd/util/output/restore_describer_test.go @@ -11,12 +11,12 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestDescribeResult(t *testing.T) { diff --git a/pkg/cmd/util/output/restore_printer.go b/pkg/cmd/util/output/restore_printer.go index 331388a6a..782eb3485 100644 --- a/pkg/cmd/util/output/restore_printer.go +++ b/pkg/cmd/util/output/restore_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/schedule_describe_test.go b/pkg/cmd/util/output/schedule_describe_test.go index 68f92e221..12e8c5858 100644 --- a/pkg/cmd/util/output/schedule_describe_test.go +++ b/pkg/cmd/util/output/schedule_describe_test.go @@ -5,8 +5,8 @@ import ( "github.com/stretchr/testify/assert" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" ) func TestDescribeSchedule(t *testing.T) { diff --git a/pkg/cmd/util/output/schedule_describer.go b/pkg/cmd/util/output/schedule_describer.go index ceb66aefb..73abb51a1 100644 --- a/pkg/cmd/util/output/schedule_describer.go +++ b/pkg/cmd/util/output/schedule_describer.go @@ -21,7 +21,7 @@ import ( "github.com/fatih/color" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func DescribeSchedule(schedule *v1.Schedule) string { diff --git a/pkg/cmd/util/output/schedule_printer.go b/pkg/cmd/util/output/schedule_printer.go index c1c5ce7dd..e39ee9069 100644 --- a/pkg/cmd/util/output/schedule_printer.go +++ b/pkg/cmd/util/output/schedule_printer.go @@ -22,7 +22,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/util/output/volume_snapshot_location_printer.go b/pkg/cmd/util/output/volume_snapshot_location_printer.go index 46ec1cb69..d6168818c 100644 --- a/pkg/cmd/util/output/volume_snapshot_location_printer.go +++ b/pkg/cmd/util/output/volume_snapshot_location_printer.go @@ -20,7 +20,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) var ( diff --git a/pkg/cmd/velero/velero.go b/pkg/cmd/velero/velero.go index 4487aacdc..42f07b03a 100644 --- a/pkg/cmd/velero/velero.go +++ b/pkg/cmd/velero/velero.go @@ -25,35 +25,35 @@ import ( "github.com/spf13/cobra" "k8s.io/klog/v2" - "github.com/velero-io/velero/pkg/cmd/cli/debug" - "github.com/velero-io/velero/pkg/cmd/cli/podvolume" - "github.com/velero-io/velero/pkg/cmd/cli/repomantenance" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/debug" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/podvolume" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/repomantenance" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/cmd/cli/backup" - "github.com/velero-io/velero/pkg/cmd/cli/backuplocation" - "github.com/velero-io/velero/pkg/cmd/cli/bug" - cliclient "github.com/velero-io/velero/pkg/cmd/cli/client" - "github.com/velero-io/velero/pkg/cmd/cli/completion" - "github.com/velero-io/velero/pkg/cmd/cli/create" - "github.com/velero-io/velero/pkg/cmd/cli/delete" - "github.com/velero-io/velero/pkg/cmd/cli/describe" - "github.com/velero-io/velero/pkg/cmd/cli/get" - "github.com/velero-io/velero/pkg/cmd/cli/install" - "github.com/velero-io/velero/pkg/cmd/cli/plugin" - "github.com/velero-io/velero/pkg/cmd/cli/repo" - "github.com/velero-io/velero/pkg/cmd/cli/restore" - "github.com/velero-io/velero/pkg/cmd/cli/schedule" - "github.com/velero-io/velero/pkg/cmd/cli/snapshotlocation" - "github.com/velero-io/velero/pkg/cmd/cli/uninstall" - "github.com/velero-io/velero/pkg/cmd/cli/version" - "github.com/velero-io/velero/pkg/cmd/server" - runplugin "github.com/velero-io/velero/pkg/cmd/server/plugin" - veleroflag "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backup" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/backuplocation" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/bug" + cliclient "github.com/vmware-tanzu/velero/pkg/cmd/cli/client" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/completion" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/create" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/delete" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/describe" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/get" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/plugin" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/repo" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/restore" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/schedule" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/snapshotlocation" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/uninstall" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/version" + "github.com/vmware-tanzu/velero/pkg/cmd/server" + runplugin "github.com/vmware-tanzu/velero/pkg/cmd/server/plugin" + veleroflag "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/features" - "github.com/velero-io/velero/pkg/cmd/cli/datamover" - "github.com/velero-io/velero/pkg/cmd/cli/nodeagent" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/datamover" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/nodeagent" ) func NewCommand(name string) *cobra.Command { diff --git a/pkg/controller/backup_controller.go b/pkg/controller/backup_controller.go index acb292416..496875bbf 100644 --- a/pkg/controller/backup_controller.go +++ b/pkg/controller/backup_controller.go @@ -42,27 +42,27 @@ import ( "sigs.k8s.io/controller-runtime/pkg/event" "sigs.k8s.io/controller-runtime/pkg/predicate" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/internal/storage" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - pkgbackup "github.com/velero-io/velero/pkg/backup" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/encode" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" - "github.com/velero-io/velero/pkg/util/results" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/storage" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/encode" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/results" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ) const ( @@ -766,7 +766,7 @@ func (b *backupReconciler) runBackup(backup *pkgbackup.Request) error { } // native snapshots phase will either be failed or completed right away - // https://github.com/velero-io/velero/blob/de3ea52f0cc478e99efa7b9524c7f353514261a4/pkg/backup/item_backupper.go#L632-L639 + // https://github.com/vmware-tanzu/velero/blob/de3ea52f0cc478e99efa7b9524c7f353514261a4/pkg/backup/item_backupper.go#L632-L639 backup.Status.VolumeSnapshotsAttempted = len(backup.VolumeSnapshots.Get()) for _, snap := range backup.VolumeSnapshots.Get() { if snap.Status.Phase == volume.SnapshotPhaseCompleted { diff --git a/pkg/controller/backup_controller_test.go b/pkg/controller/backup_controller_test.go index 2b4fd3e9a..7b646edcf 100644 --- a/pkg/controller/backup_controller_test.go +++ b/pkg/controller/backup_controller_test.go @@ -44,24 +44,24 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" fakeClient "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - pkgbackup "github.com/velero-io/velero/pkg/backup" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) type fakeBackupper struct { diff --git a/pkg/controller/backup_deletion_controller.go b/pkg/controller/backup_deletion_controller.go index 33379b219..5fe29c5f1 100644 --- a/pkg/controller/backup_deletion_controller.go +++ b/pkg/controller/backup_deletion_controller.go @@ -37,27 +37,27 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/delete" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/repository" - repomanager "github.com/velero-io/velero/pkg/repository/manager" - repotypes "github.com/velero-io/velero/pkg/repository/types" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/delete" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/repository" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ) const ( diff --git a/pkg/controller/backup_deletion_controller_test.go b/pkg/controller/backup_deletion_controller_test.go index f6df13af1..24cc65846 100644 --- a/pkg/controller/backup_deletion_controller_test.go +++ b/pkg/controller/backup_deletion_controller_test.go @@ -44,21 +44,21 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - pkgbackup "github.com/velero-io/velero/pkg/backup" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/metrics" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/plugin/velero/mocks" - "github.com/velero-io/velero/pkg/repository" - repomanager "github.com/velero-io/velero/pkg/repository/manager" - repomocks "github.com/velero-io/velero/pkg/repository/mocks" - repotypes "github.com/velero-io/velero/pkg/repository/types" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/metrics" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" + "github.com/vmware-tanzu/velero/pkg/repository" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + repomocks "github.com/vmware-tanzu/velero/pkg/repository/mocks" + repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) type backupDeletionControllerTestData struct { @@ -292,7 +292,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/velero-io/velero/issues/1546) + // (https://github.com/vmware-tanzu/velero/issues/1546) input.Labels = nil backup := builder.ForBackup(velerov1api.DefaultNamespace, "foo").Result() @@ -527,7 +527,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { input := defaultTestDbr() // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/velero-io/velero/issues/1546) + // (https://github.com/vmware-tanzu/velero/issues/1546) input.Labels = nil location := &velerov1api.BackupStorageLocation{ @@ -612,7 +612,7 @@ func TestBackupDeletionControllerReconcile(t *testing.T) { input := defaultTestDbr() // Clear out resource labels to make sure the controller adds them and does not // panic when encountering a nil Labels map - // (https://github.com/velero-io/velero/issues/1546) + // (https://github.com/vmware-tanzu/velero/issues/1546) input.Labels = nil location := &velerov1api.BackupStorageLocation{ diff --git a/pkg/controller/backup_finalizer_controller.go b/pkg/controller/backup_finalizer_controller.go index 827089010..b24c132fa 100644 --- a/pkg/controller/backup_finalizer_controller.go +++ b/pkg/controller/backup_finalizer_controller.go @@ -30,17 +30,17 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - pkgbackup "github.com/velero-io/velero/pkg/backup" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/util/encode" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/util/encode" ) // backupFinalizerReconciler reconciles a Backup object diff --git a/pkg/controller/backup_finalizer_controller_test.go b/pkg/controller/backup_finalizer_controller_test.go index 1ac8474c3..ade3ce2cd 100644 --- a/pkg/controller/backup_finalizer_controller_test.go +++ b/pkg/controller/backup_finalizer_controller_test.go @@ -33,16 +33,16 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func mockBackupFinalizerReconciler(fakeClient kbclient.Client, fakeGlobalClient kbclient.Client, fakeClock *testclocks.FakeClock) (*backupFinalizerReconciler, *fakeBackupper) { diff --git a/pkg/controller/backup_operations_controller.go b/pkg/controller/backup_operations_controller.go index dd138ca52..1a5b49c0b 100644 --- a/pkg/controller/backup_operations_controller.go +++ b/pkg/controller/backup_operations_controller.go @@ -22,7 +22,7 @@ import ( "fmt" "time" - v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -34,15 +34,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/util/encode" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/util/encode" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( @@ -229,7 +229,7 @@ func (c *backupOperationsReconciler) updateBackupAndOperationsJSON( if len(operations.ErrsSinceUpdate) > 0 { c.metrics.RegisterBackupItemsErrorsGauge(backupScheduleName, backup.Status.Errors) - // FIXME: download/upload results once https://github.com/velero-io/velero/pull/5576 is merged + // FIXME: download/upload results once https://github.com/vmware-tanzu/velero/pull/5576 is merged } removeIfComplete := true defer func() { diff --git a/pkg/controller/backup_operations_controller_test.go b/pkg/controller/backup_operations_controller_test.go index 2b90571ce..0a25676d3 100644 --- a/pkg/controller/backup_operations_controller_test.go +++ b/pkg/controller/backup_operations_controller_test.go @@ -20,7 +20,7 @@ import ( "testing" "time" - v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" @@ -33,18 +33,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/metrics" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/metrics" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) var ( diff --git a/pkg/controller/backup_queue_controller.go b/pkg/controller/backup_queue_controller.go index 97d21de9a..c5cdc9461 100644 --- a/pkg/controller/backup_queue_controller.go +++ b/pkg/controller/backup_queue_controller.go @@ -35,10 +35,10 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/util/collections" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // backupQueueReconciler reconciles a Backup object diff --git a/pkg/controller/backup_queue_controller_test.go b/pkg/controller/backup_queue_controller_test.go index 4b3064d4c..2b479ed7e 100644 --- a/pkg/controller/backup_queue_controller_test.go +++ b/pkg/controller/backup_queue_controller_test.go @@ -30,9 +30,9 @@ import ( //"sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBackupQueueReconciler(t *testing.T) { diff --git a/pkg/controller/backup_repository_controller.go b/pkg/controller/backup_repository_controller.go index 3cdc8252a..11ebb5aec 100644 --- a/pkg/controller/backup_repository_controller.go +++ b/pkg/controller/backup_repository_controller.go @@ -39,14 +39,14 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/repository/maintenance" - repomanager "github.com/velero-io/velero/pkg/repository/manager" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/repository/maintenance" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) const ( diff --git a/pkg/controller/backup_repository_controller_test.go b/pkg/controller/backup_repository_controller_test.go index cd9cd6a01..ed952f4ae 100644 --- a/pkg/controller/backup_repository_controller_test.go +++ b/pkg/controller/backup_repository_controller_test.go @@ -32,17 +32,17 @@ import ( "k8s.io/utils/clock" ctrl "sigs.k8s.io/controller-runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/repository/maintenance" - repomaintenance "github.com/velero-io/velero/pkg/repository/maintenance" - repomanager "github.com/velero-io/velero/pkg/repository/manager" - repomokes "github.com/velero-io/velero/pkg/repository/mocks" - repotypes "github.com/velero-io/velero/pkg/repository/types" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/repository/maintenance" + repomaintenance "github.com/vmware-tanzu/velero/pkg/repository/maintenance" + repomanager "github.com/vmware-tanzu/velero/pkg/repository/manager" + repomokes "github.com/vmware-tanzu/velero/pkg/repository/mocks" + repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/logging" "sigs.k8s.io/controller-runtime/pkg/client" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" diff --git a/pkg/controller/backup_storage_location_controller.go b/pkg/controller/backup_storage_location_controller.go index e65b883b6..abcd1e59e 100644 --- a/pkg/controller/backup_storage_location_controller.go +++ b/pkg/controller/backup_storage_location_controller.go @@ -22,7 +22,7 @@ import ( "strings" "time" - "github.com/velero-io/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/metrics" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -32,12 +32,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - "github.com/velero-io/velero/internal/storage" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/backup_storage_location_controller_test.go b/pkg/controller/backup_storage_location_controller_test.go index 4eddeeed0..8a5dc4a4a 100644 --- a/pkg/controller/backup_storage_location_controller_test.go +++ b/pkg/controller/backup_storage_location_controller_test.go @@ -20,7 +20,7 @@ import ( "testing" "time" - "github.com/velero-io/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/metrics" . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" @@ -35,13 +35,13 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/client-go/kubernetes/scheme" - "github.com/velero-io/velero/internal/storage" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) var _ = Describe("Backup Storage Location Reconciler", func() { diff --git a/pkg/controller/backup_sync_controller.go b/pkg/controller/backup_sync_controller.go index 99d4ca3ed..b84ae6f0b 100644 --- a/pkg/controller/backup_sync_controller.go +++ b/pkg/controller/backup_sync_controller.go @@ -33,13 +33,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/builder" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/util/kube" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" diff --git a/pkg/controller/backup_sync_controller_test.go b/pkg/controller/backup_sync_controller_test.go index 8c88da72f..fe440ff09 100644 --- a/pkg/controller/backup_sync_controller_test.go +++ b/pkg/controller/backup_sync_controller_test.go @@ -37,13 +37,13 @@ import ( ctrlClient "sigs.k8s.io/controller-runtime/pkg/client" ctrlfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/label" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/label" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func defaultLocation(namespace string) *velerov1api.BackupStorageLocation { diff --git a/pkg/controller/data_download_controller.go b/pkg/controller/data_download_controller.go index c69dfdf5a..36fec450b 100644 --- a/pkg/controller/data_download_controller.go +++ b/pkg/controller/data_download_controller.go @@ -40,20 +40,20 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/constant" - datamover "github.com/velero-io/velero/pkg/datamover" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/nodeagent" - repository "github.com/velero-io/velero/pkg/repository/manager" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/constant" + datamover "github.com/vmware-tanzu/velero/pkg/datamover" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + repository "github.com/vmware-tanzu/velero/pkg/repository/manager" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // DataDownloadReconciler reconciles a DataDownload object diff --git a/pkg/controller/data_download_controller_test.go b/pkg/controller/data_download_controller_test.go index f49bfd3f0..397f931c0 100644 --- a/pkg/controller/data_download_controller_test.go +++ b/pkg/controller/data_download_controller_test.go @@ -40,18 +40,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" - "github.com/velero-io/velero/pkg/exposer" - exposermockes "github.com/velero-io/velero/pkg/exposer/mocks" - "github.com/velero-io/velero/pkg/metrics" - velerotest "github.com/velero-io/velero/pkg/test" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + "github.com/vmware-tanzu/velero/pkg/exposer" + exposermockes "github.com/vmware-tanzu/velero/pkg/exposer/mocks" + "github.com/vmware-tanzu/velero/pkg/metrics" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const dataDownloadName string = "datadownload-1" diff --git a/pkg/controller/data_upload_controller.go b/pkg/controller/data_upload_controller.go index 35c37f691..13be03994 100644 --- a/pkg/controller/data_upload_controller.go +++ b/pkg/controller/data_upload_controller.go @@ -41,19 +41,19 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/datamover" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/nodeagent" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/datamover" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/data_upload_controller_test.go b/pkg/controller/data_upload_controller_test.go index ec6b90711..a73e3de94 100644 --- a/pkg/controller/data_upload_controller_test.go +++ b/pkg/controller/data_upload_controller_test.go @@ -46,18 +46,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - datapathmocks "github.com/velero-io/velero/pkg/datapath/mocks" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - velerotest "github.com/velero-io/velero/pkg/test" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + datapathmocks "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const dataUploadName = "dataupload-1" diff --git a/pkg/controller/download_request_controller.go b/pkg/controller/download_request_controller.go index 0c817d4be..bd9565895 100644 --- a/pkg/controller/download_request_controller.go +++ b/pkg/controller/download_request_controller.go @@ -29,12 +29,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/download_request_controller_test.go b/pkg/controller/download_request_controller_test.go index d57bca316..81bdbab83 100644 --- a/pkg/controller/download_request_controller_test.go +++ b/pkg/controller/download_request_controller_test.go @@ -32,12 +32,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) var _ = Describe("Download Request Reconciler", func() { diff --git a/pkg/controller/gc_controller.go b/pkg/controller/gc_controller.go index c9141face..bb3c60ae5 100644 --- a/pkg/controller/gc_controller.go +++ b/pkg/controller/gc_controller.go @@ -31,13 +31,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/event" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - pkgbackup "github.com/velero-io/velero/pkg/backup" - veleroclient "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/util/kube" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + pkgbackup "github.com/vmware-tanzu/velero/pkg/backup" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ) const ( diff --git a/pkg/controller/gc_controller_test.go b/pkg/controller/gc_controller_test.go index 04c8b9c1c..754b46e0a 100644 --- a/pkg/controller/gc_controller_test.go +++ b/pkg/controller/gc_controller_test.go @@ -28,9 +28,9 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func mockGCReconciler(fakeClient kbclient.Client, fakeClock *testclocks.FakeClock, freq time.Duration) *gcReconciler { diff --git a/pkg/controller/pod_volume_backup_controller.go b/pkg/controller/pod_volume_backup_controller.go index 907aca868..0bcbfa6d2 100644 --- a/pkg/controller/pod_volume_backup_controller.go +++ b/pkg/controller/pod_volume_backup_controller.go @@ -40,16 +40,16 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/kube" + veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/pod_volume_backup_controller_test.go b/pkg/controller/pod_volume_backup_controller_test.go index 3806e4e99..b49d7eb5b 100644 --- a/pkg/controller/pod_volume_backup_controller_test.go +++ b/pkg/controller/pod_volume_backup_controller_test.go @@ -43,16 +43,16 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - datapathmocks "github.com/velero-io/velero/pkg/datapath/mocks" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/metrics" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + datapathmocks "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/metrics" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const pvbName = "pvb-1" diff --git a/pkg/controller/pod_volume_restore_controller.go b/pkg/controller/pod_volume_restore_controller.go index 62a6d793d..f40de528b 100644 --- a/pkg/controller/pod_volume_restore_controller.go +++ b/pkg/controller/pod_volume_restore_controller.go @@ -42,18 +42,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - veleroapishared "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/exposer" - "github.com/velero-io/velero/pkg/nodeagent" - repository "github.com/velero-io/velero/pkg/repository/manager" - "github.com/velero-io/velero/pkg/restorehelper" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/kube" + veleroapishared "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + repository "github.com/vmware-tanzu/velero/pkg/repository/manager" + "github.com/vmware-tanzu/velero/pkg/restorehelper" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func NewPodVolumeRestoreReconciler( diff --git a/pkg/controller/pod_volume_restore_controller_test.go b/pkg/controller/pod_volume_restore_controller_test.go index 87a17e639..1819cbc32 100644 --- a/pkg/controller/pod_volume_restore_controller_test.go +++ b/pkg/controller/pod_volume_restore_controller_test.go @@ -43,18 +43,18 @@ import ( "sigs.k8s.io/controller-runtime/pkg/manager" "sigs.k8s.io/controller-runtime/pkg/reconcile" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" - "github.com/velero-io/velero/pkg/exposer" - exposermockes "github.com/velero-io/velero/pkg/exposer/mocks" - "github.com/velero-io/velero/pkg/restorehelper" - "github.com/velero-io/velero/pkg/test" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + "github.com/vmware-tanzu/velero/pkg/exposer" + exposermockes "github.com/vmware-tanzu/velero/pkg/exposer/mocks" + "github.com/vmware-tanzu/velero/pkg/restorehelper" + "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestShouldProcess(t *testing.T) { diff --git a/pkg/controller/restore_controller.go b/pkg/controller/restore_controller.go index 9dca400f1..469951f27 100644 --- a/pkg/controller/restore_controller.go +++ b/pkg/controller/restore_controller.go @@ -42,24 +42,24 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller/controllerutil" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/resourcemodifiers" - "github.com/velero-io/velero/internal/volume" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - pkgrestore "github.com/velero-io/velero/pkg/restore" - "github.com/velero-io/velero/pkg/util/collections" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" - "github.com/velero-io/velero/pkg/util/results" - veleroutil "github.com/velero-io/velero/pkg/util/velero" - pkgrestoreUtil "github.com/velero-io/velero/pkg/util/velero/restore" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/resourcemodifiers" + "github.com/vmware-tanzu/velero/internal/volume" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + pkgrestore "github.com/vmware-tanzu/velero/pkg/restore" + "github.com/vmware-tanzu/velero/pkg/util/collections" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/results" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" + pkgrestoreUtil "github.com/vmware-tanzu/velero/pkg/util/velero/restore" ) // nonRestorableResources is an exclusion list for the restoration process. Any resources @@ -70,22 +70,22 @@ var nonRestorableResources = []string{ "events.events.k8s.io", // Don't ever restore backups - if appropriate, they'll be synced in from object storage. - // https://github.com/velero-io/velero/issues/622 + // https://github.com/vmware-tanzu/velero/issues/622 "backups.velero.io", // Restores are cluster-specific, and don't have value moving across clusters. - // https://github.com/velero-io/velero/issues/622 + // https://github.com/vmware-tanzu/velero/issues/622 "restores.velero.io", // TODO: Remove this in v1.11 or v1.12 // Restic repositories are automatically managed by Velero and will be automatically // created as needed if they don't exist. - // https://github.com/velero-io/velero/issues/1113 + // https://github.com/vmware-tanzu/velero/issues/1113 "resticrepositories.velero.io", // CSINode delegates cluster node for CSI operation. // VolumeAttachement records PV mounts to which node. - // https://github.com/velero-io/velero/issues/4823 + // https://github.com/vmware-tanzu/velero/issues/4823 "csinodes.storage.k8s.io", "volumeattachments.storage.k8s.io", diff --git a/pkg/controller/restore_controller_test.go b/pkg/controller/restore_controller_test.go index 1219cf1e9..b013ee64d 100644 --- a/pkg/controller/restore_controller_test.go +++ b/pkg/controller/restore_controller_test.go @@ -35,20 +35,20 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/resourcemodifiers" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/metrics" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/framework" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - pkgrestore "github.com/velero-io/velero/pkg/restore" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/logging" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/resourcemodifiers" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/metrics" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + pkgrestore "github.com/vmware-tanzu/velero/pkg/restore" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestFetchBackupInfo(t *testing.T) { diff --git a/pkg/controller/restore_finalizer_controller.go b/pkg/controller/restore_finalizer_controller.go index 00aa9db45..f82216bc3 100644 --- a/pkg/controller/restore_finalizer_controller.go +++ b/pkg/controller/restore_finalizer_controller.go @@ -36,18 +36,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/boolptr" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/results" ) type restoreFinalizerReconciler struct { diff --git a/pkg/controller/restore_finalizer_controller_test.go b/pkg/controller/restore_finalizer_controller_test.go index 6bf3f7c84..6fb5ba303 100644 --- a/pkg/controller/restore_finalizer_controller_test.go +++ b/pkg/controller/restore_finalizer_controller_test.go @@ -36,20 +36,20 @@ import ( ctrl "sigs.k8s.io/controller-runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/metrics" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" - pkgUtilKubeMocks "github.com/velero-io/velero/pkg/util/kube/mocks" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/metrics" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + pkgUtilKubeMocks "github.com/vmware-tanzu/velero/pkg/util/kube/mocks" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestRestoreFinalizerReconcile(t *testing.T) { diff --git a/pkg/controller/restore_operations_controller.go b/pkg/controller/restore_operations_controller.go index c5b6c00e8..0539e21a4 100644 --- a/pkg/controller/restore_operations_controller.go +++ b/pkg/controller/restore_operations_controller.go @@ -30,14 +30,14 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/restore_operations_controller_test.go b/pkg/controller/restore_operations_controller_test.go index aa50dd3e7..a1ec0f792 100644 --- a/pkg/controller/restore_operations_controller_test.go +++ b/pkg/controller/restore_operations_controller_test.go @@ -31,18 +31,18 @@ import ( ctrl "sigs.k8s.io/controller-runtime" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/itemoperationmap" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/metrics" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" - "github.com/velero-io/velero/pkg/plugin/clientmgmt" - pluginmocks "github.com/velero-io/velero/pkg/plugin/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/itemoperationmap" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/metrics" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt" + pluginmocks "github.com/vmware-tanzu/velero/pkg/plugin/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) var ( diff --git a/pkg/controller/schedule_controller.go b/pkg/controller/schedule_controller.go index f811ae81f..443b3c08b 100644 --- a/pkg/controller/schedule_controller.go +++ b/pkg/controller/schedule_controller.go @@ -33,11 +33,11 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/predicate" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/metrics" - "github.com/velero-io/velero/pkg/util/kube" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/metrics" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/controller/schedule_controller_test.go b/pkg/controller/schedule_controller_test.go index 153e82889..f4585763c 100644 --- a/pkg/controller/schedule_controller_test.go +++ b/pkg/controller/schedule_controller_test.go @@ -31,10 +31,10 @@ import ( ctrl "sigs.k8s.io/controller-runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/metrics" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/metrics" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) // Test reconcile function of schedule controller. Pause is not covered as event filter will not allow it through @@ -334,7 +334,7 @@ func TestGetNextRunTime(t *testing.T) { } func TestParseCronSchedule(t *testing.T) { - // From https://github.com/velero-io/velero/issues/30, where we originally were using cron.Parse(), + // From https://github.com/vmware-tanzu/velero/issues/30, where we originally were using cron.Parse(), // which treats the first field as seconds, and not minutes. We want to use cron.ParseStandard() // instead, which has the first field as minutes. diff --git a/pkg/controller/server_status_request_controller.go b/pkg/controller/server_status_request_controller.go index 15f7a9176..3fb1af80b 100644 --- a/pkg/controller/server_status_request_controller.go +++ b/pkg/controller/server_status_request_controller.go @@ -29,12 +29,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/controller" - "github.com/velero-io/velero/internal/velero" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/constant" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/internal/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" ) const ( diff --git a/pkg/controller/server_status_request_controller_test.go b/pkg/controller/server_status_request_controller_test.go index cc2ca223d..eb95c7e87 100644 --- a/pkg/controller/server_status_request_controller_test.go +++ b/pkg/controller/server_status_request_controller_test.go @@ -30,12 +30,12 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func statusRequestBuilder(resourceVersion string) *builder.ServerStatusRequestBuilder { diff --git a/pkg/controller/suite_test.go b/pkg/controller/suite_test.go index 2c221d22c..1e5e90717 100644 --- a/pkg/controller/suite_test.go +++ b/pkg/controller/suite_test.go @@ -25,8 +25,8 @@ import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/persistence" - persistencemocks "github.com/velero-io/velero/pkg/persistence/mocks" + "github.com/vmware-tanzu/velero/pkg/persistence" + persistencemocks "github.com/vmware-tanzu/velero/pkg/persistence/mocks" "k8s.io/klog/v2" "sigs.k8s.io/controller-runtime/pkg/envtest" @@ -35,8 +35,8 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" "k8s.io/client-go/kubernetes/scheme" "k8s.io/client-go/rest" diff --git a/pkg/datamover/backup_micro_service.go b/pkg/datamover/backup_micro_service.go index ef3c20238..4edd24c97 100644 --- a/pkg/datamover/backup_micro_service.go +++ b/pkg/datamover/backup_micro_service.go @@ -31,13 +31,13 @@ import ( cachetool "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/cache" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/datamover/backup_micro_service_test.go b/pkg/datamover/backup_micro_service_test.go index 60821eb72..79b4a834a 100644 --- a/pkg/datamover/backup_micro_service_test.go +++ b/pkg/datamover/backup_micro_service_test.go @@ -30,20 +30,20 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/uploader" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - velerotest "github.com/velero-io/velero/pkg/test" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" ) type backupMsTestHelper struct { diff --git a/pkg/datamover/dataupload_delete_action.go b/pkg/datamover/dataupload_delete_action.go index e0b1e7abc..6b36e1068 100644 --- a/pkg/datamover/dataupload_delete_action.go +++ b/pkg/datamover/dataupload_delete_action.go @@ -12,11 +12,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/velero" - repotypes "github.com/velero-io/velero/pkg/repository/types" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" ) type DataUploadDeleteAction struct { diff --git a/pkg/datamover/dataupload_delete_action_test.go b/pkg/datamover/dataupload_delete_action_test.go index 8ec70a0f7..cdbf4b006 100644 --- a/pkg/datamover/dataupload_delete_action_test.go +++ b/pkg/datamover/dataupload_delete_action_test.go @@ -32,11 +32,11 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func toUnstructured(t *testing.T, du *velerov2alpha1.DataUpload) runtime.Unstructured { diff --git a/pkg/datamover/restore_micro_service.go b/pkg/datamover/restore_micro_service.go index 0fbf2bb50..e1c95ee3d 100644 --- a/pkg/datamover/restore_micro_service.go +++ b/pkg/datamover/restore_micro_service.go @@ -29,13 +29,13 @@ import ( "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" cachetool "k8s.io/client-go/tools/cache" ) diff --git a/pkg/datamover/restore_micro_service_test.go b/pkg/datamover/restore_micro_service_test.go index 394fa4f02..bce4d94b7 100644 --- a/pkg/datamover/restore_micro_service_test.go +++ b/pkg/datamover/restore_micro_service_test.go @@ -31,15 +31,15 @@ import ( kbclient "sigs.k8s.io/controller-runtime/pkg/client" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" + "github.com/vmware-tanzu/velero/pkg/uploader" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestOnDataDownloadFailed(t *testing.T) { diff --git a/pkg/datapath/data_path.go b/pkg/datapath/data_path.go index fc6336cd7..68521c04b 100644 --- a/pkg/datapath/data_path.go +++ b/pkg/datapath/data_path.go @@ -24,14 +24,14 @@ import ( "github.com/sirupsen/logrus" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" - repokey "github.com/velero-io/velero/pkg/repository/keys" - repoProvider "github.com/velero-io/velero/pkg/repository/provider" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/uploader/provider" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" + repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" + repoProvider "github.com/vmware-tanzu/velero/pkg/repository/provider" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader/provider" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // InitParam define the input param for data path init @@ -167,7 +167,7 @@ func (dp *generalDataPath) close(ctx context.Context) { func (dp *generalDataPath) StartBackup(source AccessPoint, uploaderConfig map[string]string, param any) error { if !dp.initialized { - return errors.New("data path is not initialized") + return errors.New("file system data path is not initialized") } dp.wgDataPath.Add(1) @@ -243,7 +243,7 @@ func (dp *generalDataPath) UpdateProgress(p *uploader.Progress) { func (dp *generalDataPath) Cancel() { dp.cancel() - dp.log.WithField("user", dp.jobName).Info("Data path is canceled") + dp.log.WithField("user", dp.jobName).Info("FileSystemBR is canceled") } func (dp *generalDataPath) boostRepoConnect(ctx context.Context, repositoryType string, credentialGetter *credentials.CredentialGetter, cacheDir string) error { diff --git a/pkg/datapath/data_path_test.go b/pkg/datapath/data_path_test.go index 606822b2f..c063347c7 100644 --- a/pkg/datapath/data_path_test.go +++ b/pkg/datapath/data_path_test.go @@ -25,9 +25,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader/provider" - providerMock "github.com/velero-io/velero/pkg/uploader/provider/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader/provider" + providerMock "github.com/vmware-tanzu/velero/pkg/uploader/provider/mocks" ) func TestAsyncBackup(t *testing.T) { diff --git a/pkg/datapath/micro_service_watcher.go b/pkg/datapath/micro_service_watcher.go index ae523c05b..665b84b81 100644 --- a/pkg/datapath/micro_service_watcher.go +++ b/pkg/datapath/micro_service_watcher.go @@ -32,13 +32,13 @@ import ( "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/manager" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) const ( diff --git a/pkg/datapath/micro_service_watcher_test.go b/pkg/datapath/micro_service_watcher_test.go index 2687a323a..6724c290c 100644 --- a/pkg/datapath/micro_service_watcher_test.go +++ b/pkg/datapath/micro_service_watcher_test.go @@ -36,10 +36,10 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func TestReEnsureThisPod(t *testing.T) { diff --git a/pkg/datapath/mocks/asyncBR.go b/pkg/datapath/mocks/asyncBR.go index 05a75b4c1..ef87fde83 100644 --- a/pkg/datapath/mocks/asyncBR.go +++ b/pkg/datapath/mocks/asyncBR.go @@ -6,7 +6,7 @@ import ( context "context" mock "github.com/stretchr/testify/mock" - datapath "github.com/velero-io/velero/pkg/datapath" + datapath "github.com/vmware-tanzu/velero/pkg/datapath" ) // AsyncBR is an autogenerated mock type for the AsyncBR type diff --git a/pkg/datapath/types.go b/pkg/datapath/types.go index ebd4f14d6..a9c2331a6 100644 --- a/pkg/datapath/types.go +++ b/pkg/datapath/types.go @@ -19,7 +19,7 @@ package datapath import ( "context" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader" ) // Result represents the result of a backup/restore diff --git a/pkg/discovery/helper.go b/pkg/discovery/helper.go index 282c91bf6..11c2d623b 100644 --- a/pkg/discovery/helper.go +++ b/pkg/discovery/helper.go @@ -30,9 +30,9 @@ import ( "k8s.io/client-go/discovery" "k8s.io/client-go/restmapper" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/features" - kcmdutil "github.com/velero-io/velero/third_party/kubernetes/pkg/kubectl/cmd/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/features" + kcmdutil "github.com/vmware-tanzu/velero/third_party/kubernetes/pkg/kubectl/cmd/util" ) //go:generate mockery --name Helper diff --git a/pkg/discovery/helper_test.go b/pkg/discovery/helper_test.go index c8af4f62e..d70c10438 100644 --- a/pkg/discovery/helper_test.go +++ b/pkg/discovery/helper_test.go @@ -30,10 +30,10 @@ import ( "k8s.io/client-go/discovery/fake" clientgotesting "k8s.io/client-go/testing" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/features" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/features" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func TestSortResources(t *testing.T) { diff --git a/pkg/exposer/cache_volume.go b/pkg/exposer/cache_volume.go index e914c191c..85571c243 100644 --- a/pkg/exposer/cache_volume.go +++ b/pkg/exposer/cache_volume.go @@ -24,8 +24,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type CacheConfigs struct { diff --git a/pkg/exposer/csi_snapshot.go b/pkg/exposer/csi_snapshot.go index 316b2ae75..079a4b527 100644 --- a/pkg/exposer/csi_snapshot.go +++ b/pkg/exposer/csi_snapshot.go @@ -33,12 +33,12 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/nodeagent" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // CSISnapshotExposeParam define the input param for Expose of CSI snapshots diff --git a/pkg/exposer/csi_snapshot_priority_test.go b/pkg/exposer/csi_snapshot_priority_test.go index bb1ce9ea0..d1ffa4700 100644 --- a/pkg/exposer/csi_snapshot_priority_test.go +++ b/pkg/exposer/csi_snapshot_priority_test.go @@ -28,9 +28,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/client-go/kubernetes/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestCreateBackupPodWithPriorityClass(t *testing.T) { diff --git a/pkg/exposer/csi_snapshot_test.go b/pkg/exposer/csi_snapshot_test.go index 2e91f28ab..e1a9860eb 100644 --- a/pkg/exposer/csi_snapshot_test.go +++ b/pkg/exposer/csi_snapshot_test.go @@ -36,12 +36,12 @@ import ( "k8s.io/utils/pointer" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" storagev1api "k8s.io/api/storage/v1" ) diff --git a/pkg/exposer/generic_restore.go b/pkg/exposer/generic_restore.go index adfe89f9f..b711e7364 100644 --- a/pkg/exposer/generic_restore.go +++ b/pkg/exposer/generic_restore.go @@ -30,10 +30,10 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/nodeagent" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // GenericRestoreExposeParam define the input param for Generic Restore Expose diff --git a/pkg/exposer/generic_restore_priority_test.go b/pkg/exposer/generic_restore_priority_test.go index c0c2d677e..642e0cc43 100644 --- a/pkg/exposer/generic_restore_priority_test.go +++ b/pkg/exposer/generic_restore_priority_test.go @@ -27,9 +27,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/client-go/kubernetes/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // TestCreateRestorePodWithPriorityClass verifies that the priority class name is properly set in the restore pod diff --git a/pkg/exposer/generic_restore_test.go b/pkg/exposer/generic_restore_test.go index 397a8871f..799719a50 100644 --- a/pkg/exposer/generic_restore_test.go +++ b/pkg/exposer/generic_restore_test.go @@ -32,9 +32,9 @@ import ( "k8s.io/client-go/kubernetes/fake" clientTesting "k8s.io/client-go/testing" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/kube" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestRestoreExpose(t *testing.T) { diff --git a/pkg/exposer/host_path.go b/pkg/exposer/host_path.go index 0ba791454..e51178711 100644 --- a/pkg/exposer/host_path.go +++ b/pkg/exposer/host_path.go @@ -26,11 +26,11 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) var getVolumeDirectory = kube.GetVolumeDirectory diff --git a/pkg/exposer/host_path_test.go b/pkg/exposer/host_path_test.go index 7089fcbb3..e751afe0d 100644 --- a/pkg/exposer/host_path_test.go +++ b/pkg/exposer/host_path_test.go @@ -28,13 +28,13 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/nodeagent" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestGetPodVolumeHostPath(t *testing.T) { diff --git a/pkg/exposer/image.go b/pkg/exposer/image.go index 8bdc7634b..58658e1b7 100644 --- a/pkg/exposer/image.go +++ b/pkg/exposer/image.go @@ -24,7 +24,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/client-go/kubernetes" - "github.com/velero-io/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/nodeagent" ) type inheritedPodInfo struct { diff --git a/pkg/exposer/image_test.go b/pkg/exposer/image_test.go index 0edadf823..5c47f5c04 100644 --- a/pkg/exposer/image_test.go +++ b/pkg/exposer/image_test.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/kube" appsv1api "k8s.io/api/apps/v1" corev1api "k8s.io/api/core/v1" diff --git a/pkg/exposer/mocks/GenericRestoreExposer.go b/pkg/exposer/mocks/GenericRestoreExposer.go index e3214ad2a..7daae6d6d 100644 --- a/pkg/exposer/mocks/GenericRestoreExposer.go +++ b/pkg/exposer/mocks/GenericRestoreExposer.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/exposer" "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" ) diff --git a/pkg/exposer/mocks/PodVolumeExposer.go b/pkg/exposer/mocks/PodVolumeExposer.go index be0a20486..d601e5c5b 100644 --- a/pkg/exposer/mocks/PodVolumeExposer.go +++ b/pkg/exposer/mocks/PodVolumeExposer.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/exposer" + "github.com/vmware-tanzu/velero/pkg/exposer" "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" ) diff --git a/pkg/exposer/pod_volume.go b/pkg/exposer/pod_volume.go index 4de0fba57..aeb6f1903 100644 --- a/pkg/exposer/pod_volume.go +++ b/pkg/exposer/pod_volume.go @@ -31,10 +31,10 @@ import ( "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/exposer/pod_volume_test.go b/pkg/exposer/pod_volume_test.go index 48b7d1480..d65030e22 100644 --- a/pkg/exposer/pod_volume_test.go +++ b/pkg/exposer/pod_volume_test.go @@ -19,11 +19,11 @@ import ( clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/filesystem" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) func TestPodVolumeExpose(t *testing.T) { diff --git a/pkg/exposer/vgdp_counter.go b/pkg/exposer/vgdp_counter.go index b0c9f94d1..cf6737c14 100644 --- a/pkg/exposer/vgdp_counter.go +++ b/pkg/exposer/vgdp_counter.go @@ -9,8 +9,8 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/client-go/tools/cache" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" "sigs.k8s.io/controller-runtime/pkg/manager" diff --git a/pkg/exposer/vgdp_counter_test.go b/pkg/exposer/vgdp_counter_test.go index b67f61f55..725b5f8d6 100644 --- a/pkg/exposer/vgdp_counter_test.go +++ b/pkg/exposer/vgdp_counter_test.go @@ -9,11 +9,11 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) func TestIsConstrained(t *testing.T) { diff --git a/pkg/install/daemonset.go b/pkg/install/daemonset.go index 616b8b5fe..10d2764e6 100644 --- a/pkg/install/daemonset.go +++ b/pkg/install/daemonset.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/utils/ptr" - "github.com/velero-io/velero/internal/velero" - "github.com/velero-io/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/internal/velero" + "github.com/vmware-tanzu/velero/pkg/nodeagent" ) func DaemonSet(namespace string, opts ...podTemplateOption) *appsv1api.DaemonSet { diff --git a/pkg/install/deployment.go b/pkg/install/deployment.go index a33c597f6..7af17bc53 100644 --- a/pkg/install/deployment.go +++ b/pkg/install/deployment.go @@ -26,9 +26,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/utils/ptr" - "github.com/velero-io/velero/internal/velero" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/velero" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type podTemplateOption func(*podTemplateConfig) diff --git a/pkg/install/deployment_test.go b/pkg/install/deployment_test.go index decd38295..53b696f72 100644 --- a/pkg/install/deployment_test.go +++ b/pkg/install/deployment_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) func TestDeployment(t *testing.T) { diff --git a/pkg/install/import_test.go b/pkg/install/import_test.go index dfee28291..e77befe46 100644 --- a/pkg/install/import_test.go +++ b/pkg/install/import_test.go @@ -13,7 +13,7 @@ import ( // test that this package do not import cloud provider -// Prevent https://github.com/velero-io/velero/issues/8207 and https://github.com/velero-io/velero/issues/8157 +// Prevent https://github.com/vmware-tanzu/velero/issues/8207 and https://github.com/vmware-tanzu/velero/issues/8157 func TestPkgImportNoCloudProvider(t *testing.T) { _, filename, _, ok := runtime.Caller(0) if !ok { diff --git a/pkg/install/install.go b/pkg/install/install.go index 862405ef3..b60c4f9aa 100644 --- a/pkg/install/install.go +++ b/pkg/install/install.go @@ -36,8 +36,8 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // kindToResource translates a Kind (mixed case, singular) to a Resource (lowercase, plural) string. diff --git a/pkg/install/install_test.go b/pkg/install/install_test.go index 5f2045ae5..47a9aa273 100644 --- a/pkg/install/install_test.go +++ b/pkg/install/install_test.go @@ -21,8 +21,8 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "sigs.k8s.io/controller-runtime/pkg/client/fake" - v1crds "github.com/velero-io/velero/config/crd/v1/crds" - "github.com/velero-io/velero/pkg/test" + v1crds "github.com/vmware-tanzu/velero/config/crd/v1/crds" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestInstall(t *testing.T) { diff --git a/pkg/install/resources.go b/pkg/install/resources.go index 89eba79ba..5c7534774 100644 --- a/pkg/install/resources.go +++ b/pkg/install/resources.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1crds "github.com/velero-io/velero/config/crd/v1/crds" - v2alpha1crds "github.com/velero-io/velero/config/crd/v2alpha1/crds" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/kube" + v1crds "github.com/vmware-tanzu/velero/config/crd/v1/crds" + v2alpha1crds "github.com/vmware-tanzu/velero/config/crd/v2alpha1/crds" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/itemblock/actions/pod_action.go b/pkg/itemblock/actions/pod_action.go index 421e4a7c1..2596e78a2 100644 --- a/pkg/itemblock/actions/pod_action.go +++ b/pkg/itemblock/actions/pod_action.go @@ -22,9 +22,9 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) // PodAction implements ItemBlockAction. diff --git a/pkg/itemblock/actions/pod_action_test.go b/pkg/itemblock/actions/pod_action_test.go index c6cc34799..645feeee2 100644 --- a/pkg/itemblock/actions/pod_action_test.go +++ b/pkg/itemblock/actions/pod_action_test.go @@ -23,9 +23,9 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestPodActionAppliesTo(t *testing.T) { diff --git a/pkg/itemblock/actions/pvc_action.go b/pkg/itemblock/actions/pvc_action.go index 0b95307f5..6777ef566 100644 --- a/pkg/itemblock/actions/pvc_action.go +++ b/pkg/itemblock/actions/pvc_action.go @@ -25,13 +25,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/kuberesource" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" - "github.com/velero-io/velero/pkg/util/kube" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // PVCAction inspects a PersistentVolumeClaim for the PersistentVolume diff --git a/pkg/itemblock/actions/pvc_action_test.go b/pkg/itemblock/actions/pvc_action_test.go index 4e4f16ec4..8b3cf58d5 100644 --- a/pkg/itemblock/actions/pvc_action_test.go +++ b/pkg/itemblock/actions/pvc_action_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBackupPVAction(t *testing.T) { diff --git a/pkg/itemblock/actions/service_account_action.go b/pkg/itemblock/actions/service_account_action.go index 743299f95..91cdbbe59 100644 --- a/pkg/itemblock/actions/service_account_action.go +++ b/pkg/itemblock/actions/service_account_action.go @@ -22,10 +22,10 @@ import ( "k8s.io/apimachinery/pkg/api/meta" "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/actionhelpers" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) // ServiceAccountAction implements ItemBlockAction. diff --git a/pkg/itemblock/actions/service_account_action_test.go b/pkg/itemblock/actions/service_account_action_test.go index d357c9df3..01106b215 100644 --- a/pkg/itemblock/actions/service_account_action_test.go +++ b/pkg/itemblock/actions/service_account_action_test.go @@ -28,10 +28,10 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/actionhelpers" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/actionhelpers" ) func newV1ClusterRoleBindingList(rbacCRBList []rbacv1.ClusterRoleBinding) []actionhelpers.ClusterRoleBinding { diff --git a/pkg/itemoperation/backup_operation.go b/pkg/itemoperation/backup_operation.go index 14ee9e88d..84b207a3b 100644 --- a/pkg/itemoperation/backup_operation.go +++ b/pkg/itemoperation/backup_operation.go @@ -17,7 +17,7 @@ limitations under the License. package itemoperation import ( - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // BackupOperation stores information about an async item operation diff --git a/pkg/itemoperation/restore_operation.go b/pkg/itemoperation/restore_operation.go index f2162d166..d639d4b23 100644 --- a/pkg/itemoperation/restore_operation.go +++ b/pkg/itemoperation/restore_operation.go @@ -17,7 +17,7 @@ limitations under the License. package itemoperation import ( - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RestoreOperation stores information about an async item operation diff --git a/pkg/itemoperationmap/backup_operation_map.go b/pkg/itemoperationmap/backup_operation_map.go index 47663d64d..47cdcac81 100644 --- a/pkg/itemoperationmap/backup_operation_map.go +++ b/pkg/itemoperationmap/backup_operation_map.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/util/encode" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/util/encode" ) type BackupItemOperationsMap struct { diff --git a/pkg/itemoperationmap/restore_operation_map.go b/pkg/itemoperationmap/restore_operation_map.go index 5bc35bb67..4256591bc 100644 --- a/pkg/itemoperationmap/restore_operation_map.go +++ b/pkg/itemoperationmap/restore_operation_map.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/persistence" - "github.com/velero-io/velero/pkg/util/encode" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/persistence" + "github.com/vmware-tanzu/velero/pkg/util/encode" ) type RestoreItemOperationsMap struct { diff --git a/pkg/kopia/kopia_log_test.go b/pkg/kopia/kopia_log_test.go index efc8e9fc9..bb03a89cc 100644 --- a/pkg/kopia/kopia_log_test.go +++ b/pkg/kopia/kopia_log_test.go @@ -24,7 +24,7 @@ import ( "github.com/stretchr/testify/require" "go.uber.org/zap/zapcore" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestEnabled(t *testing.T) { diff --git a/pkg/label/label.go b/pkg/label/label.go index 2b97060aa..bfd28b836 100644 --- a/pkg/label/label.go +++ b/pkg/label/label.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/apimachinery/pkg/util/validation" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // GetValidName converts an input string to valid Kubernetes label string in accordance to rfc1035 DNS Label spec diff --git a/pkg/nodeagent/node_agent.go b/pkg/nodeagent/node_agent.go index 23ecaec01..87efb896a 100644 --- a/pkg/nodeagent/node_agent.go +++ b/pkg/nodeagent/node_agent.go @@ -29,8 +29,8 @@ import ( "k8s.io/client-go/kubernetes" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/kube" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/nodeagent/node_agent_test.go b/pkg/nodeagent/node_agent_test.go index 704c92876..168e91de1 100644 --- a/pkg/nodeagent/node_agent_test.go +++ b/pkg/nodeagent/node_agent_test.go @@ -30,9 +30,9 @@ import ( clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/pkg/builder" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type reactor struct { diff --git a/pkg/persistence/mocks/backup_store.go b/pkg/persistence/mocks/backup_store.go index b8392c242..b9c4184c3 100644 --- a/pkg/persistence/mocks/backup_store.go +++ b/pkg/persistence/mocks/backup_store.go @@ -21,15 +21,15 @@ import ( io "io" mock "github.com/stretchr/testify/mock" - itemoperation "github.com/velero-io/velero/pkg/itemoperation" + itemoperation "github.com/vmware-tanzu/velero/pkg/itemoperation" - persistence "github.com/velero-io/velero/pkg/persistence" + persistence "github.com/vmware-tanzu/velero/pkg/persistence" - results "github.com/velero-io/velero/pkg/util/results" + results "github.com/vmware-tanzu/velero/pkg/util/results" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - volume "github.com/velero-io/velero/internal/volume" + volume "github.com/vmware-tanzu/velero/internal/volume" volumesnapshotv1 "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumesnapshot/v1" ) diff --git a/pkg/persistence/object_store.go b/pkg/persistence/object_store.go index 22a91b3b5..fd441e943 100644 --- a/pkg/persistence/object_store.go +++ b/pkg/persistence/object_store.go @@ -30,13 +30,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/serializer" kerrors "k8s.io/apimachinery/pkg/util/errors" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/results" ) type BackupInfo struct { diff --git a/pkg/persistence/object_store_test.go b/pkg/persistence/object_store_test.go index 5f08d4cd7..e9a3bde36 100644 --- a/pkg/persistence/object_store_test.go +++ b/pkg/persistence/object_store_test.go @@ -33,17 +33,17 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/encode" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/encode" + "github.com/vmware-tanzu/velero/pkg/util/results" ) type objectBackupStoreTestHarness struct { diff --git a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go index 457eff760..4bc28e487 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action.go @@ -20,11 +20,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" ) // AdaptedBackupItemAction is a backup item action adapted to the v1 BackupItemAction API diff --git a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go index 75711d401..8dc113df5 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v1/restartable_backup_item_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/internal/restartabletest" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v1" + "github.com/vmware-tanzu/velero/internal/restartabletest" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v1" ) func TestRestartableGetBackupItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go index d3f2dd35e..84ddb54b2 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action.go @@ -20,12 +20,12 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" ) // AdaptedBackupItemAction is a v1 BackupItemAction adapted to implement the v2 API diff --git a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go index 649ee0fcb..bd1ee0ec2 100644 --- a/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go +++ b/pkg/plugin/clientmgmt/backupitemaction/v2/restartable_backup_item_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/internal/restartabletest" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - mocksv2 "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + "github.com/vmware-tanzu/velero/internal/restartabletest" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocksv2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" ) func TestRestartableGetBackupItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go index 9d69330c2..83742978f 100644 --- a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go +++ b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action.go @@ -20,11 +20,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" ) // AdaptedItemBlockAction is an ItemBlock action adapted to the v1 ItemBlockAction API diff --git a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go index a4c18c3fd..04dd60652 100644 --- a/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go +++ b/pkg/plugin/clientmgmt/itemblockaction/v1/restartable_item_block_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/internal/restartabletest" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/itemblockaction/v1" + "github.com/vmware-tanzu/velero/internal/restartabletest" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/itemblockaction/v1" ) func TestRestartableGetItemBlockAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/manager.go b/pkg/plugin/clientmgmt/manager.go index 747591c18..1c895d86e 100644 --- a/pkg/plugin/clientmgmt/manager.go +++ b/pkg/plugin/clientmgmt/manager.go @@ -24,21 +24,21 @@ import ( "github.com/sirupsen/logrus" - biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - biav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v2" - ibav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/itemblockaction/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - riav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" - vsv1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + biav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v2" + ibav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + riav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" + vsv1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // Manager manages the lifecycles of plugins. diff --git a/pkg/plugin/clientmgmt/manager_test.go b/pkg/plugin/clientmgmt/manager_test.go index 296bfa21f..7576c42c5 100644 --- a/pkg/plugin/clientmgmt/manager_test.go +++ b/pkg/plugin/clientmgmt/manager_test.go @@ -26,17 +26,17 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/internal/restartabletest" - biav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v1" - biav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/backupitemaction/v2" - ibav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/itemblockaction/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - riav2cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" - vsv1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/restartabletest" + biav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v1" + biav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/backupitemaction/v2" + ibav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + riav2cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v2" + vsv1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/test" ) type mockRegistry struct { diff --git a/pkg/plugin/clientmgmt/process/client_builder.go b/pkg/plugin/clientmgmt/process/client_builder.go index 3e86c2862..ceeac8db7 100644 --- a/pkg/plugin/clientmgmt/process/client_builder.go +++ b/pkg/plugin/clientmgmt/process/client_builder.go @@ -26,11 +26,11 @@ import ( hcplugin "github.com/hashicorp/go-plugin" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/plugin/framework" - biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/framework/common" - ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" ) // clientBuilder builds go-plugin Clients. diff --git a/pkg/plugin/clientmgmt/process/client_builder_test.go b/pkg/plugin/clientmgmt/process/client_builder_test.go index daf1de42f..14278ae8f 100644 --- a/pkg/plugin/clientmgmt/process/client_builder_test.go +++ b/pkg/plugin/clientmgmt/process/client_builder_test.go @@ -25,12 +25,12 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/plugin/framework" - biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/framework/common" - ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewClientBuilder(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/process/process.go b/pkg/plugin/clientmgmt/process/process.go index e21221f06..4d20a1784 100644 --- a/pkg/plugin/clientmgmt/process/process.go +++ b/pkg/plugin/clientmgmt/process/process.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" ) type Factory interface { diff --git a/pkg/plugin/clientmgmt/process/process_test.go b/pkg/plugin/clientmgmt/process/process_test.go index ef4138b08..e67de8db9 100644 --- a/pkg/plugin/clientmgmt/process/process_test.go +++ b/pkg/plugin/clientmgmt/process/process_test.go @@ -23,8 +23,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" ) type mockClientProtocol struct { diff --git a/pkg/plugin/clientmgmt/process/registry.go b/pkg/plugin/clientmgmt/process/registry.go index 4e2e36cf7..744048690 100644 --- a/pkg/plugin/clientmgmt/process/registry.go +++ b/pkg/plugin/clientmgmt/process/registry.go @@ -25,9 +25,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // Registry manages information about available plugins. diff --git a/pkg/plugin/clientmgmt/process/registry_test.go b/pkg/plugin/clientmgmt/process/registry_test.go index 02330fbd3..e188419b2 100644 --- a/pkg/plugin/clientmgmt/process/registry_test.go +++ b/pkg/plugin/clientmgmt/process/registry_test.go @@ -25,7 +25,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewRegistry(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restartable_delete_item_action.go b/pkg/plugin/clientmgmt/restartable_delete_item_action.go index c2a68a77f..b566ede6f 100644 --- a/pkg/plugin/clientmgmt/restartable_delete_item_action.go +++ b/pkg/plugin/clientmgmt/restartable_delete_item_action.go @@ -19,9 +19,9 @@ package clientmgmt import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // restartableDeleteItemAction is a delete item action for a given implementation (such as "pod"). It is associated with diff --git a/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go b/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go index 20722d2e8..52edf7ffb 100644 --- a/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go +++ b/pkg/plugin/clientmgmt/restartable_delete_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/restartabletest" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/plugin/velero/mocks" + "github.com/vmware-tanzu/velero/internal/restartabletest" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" ) func TestRestartableGetDeleteItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restartable_object_store.go b/pkg/plugin/clientmgmt/restartable_object_store.go index a37f4c47c..6e66d4b3e 100644 --- a/pkg/plugin/clientmgmt/restartable_object_store.go +++ b/pkg/plugin/clientmgmt/restartable_object_store.go @@ -22,9 +22,9 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // restartableObjectStore is an object store for a given implementation (such as "aws"). It is associated with diff --git a/pkg/plugin/clientmgmt/restartable_object_store_test.go b/pkg/plugin/clientmgmt/restartable_object_store_test.go index a334f70f5..0b25e02d8 100644 --- a/pkg/plugin/clientmgmt/restartable_object_store_test.go +++ b/pkg/plugin/clientmgmt/restartable_object_store_test.go @@ -26,10 +26,10 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/internal/restartabletest" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks" + "github.com/vmware-tanzu/velero/internal/restartabletest" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks" ) func TestRestartableGetObjectStore(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go index 4e07fa1cb..a03ccecd2 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action.go @@ -19,10 +19,10 @@ package v1 import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" ) // AdaptedRestoreItemAction is a restore item action adapted to the v1 RestoreItemAction API diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go index f2554fd92..08239fc93 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v1/restartable_restore_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/restartabletest" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v1" + "github.com/vmware-tanzu/velero/internal/restartabletest" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v1" ) func TestRestartableGetRestoreItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go index 9989f0d70..c23787cfb 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action.go @@ -19,12 +19,12 @@ package v2 import ( "github.com/pkg/errors" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - riav1cli "github.com/velero-io/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + riav1cli "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/restoreitemaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" ) // AdaptedRestoreItemAction is a v1 RestoreItemAction adapted to implement the v2 API diff --git a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go index bde2eb2ed..af6521e43 100644 --- a/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go +++ b/pkg/plugin/clientmgmt/restoreitemaction/v2/restartable_restore_item_action_test.go @@ -24,12 +24,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/restartabletest" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/internal/restartabletest" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/restoreitemaction/v2" ) func TestRestartableGetRestoreItemAction(t *testing.T) { diff --git a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go index dd26aa7f2..7aec39872 100644 --- a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go +++ b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter.go @@ -20,9 +20,9 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // AdaptedVolumeSnapshotter is a volume snapshotter adapted to the v1 VolumeSnapshotter API diff --git a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go index 4ff59d66f..8a2efe04c 100644 --- a/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go +++ b/pkg/plugin/clientmgmt/volumesnapshotter/v1/restartable_volume_snapshotter_test.go @@ -25,10 +25,10 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/restartabletest" - "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" - "github.com/velero-io/velero/pkg/plugin/framework/common" - providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/internal/restartabletest" + "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" ) func TestRestartableGetVolumeSnapshotter(t *testing.T) { diff --git a/pkg/plugin/framework/action_resolver.go b/pkg/plugin/framework/action_resolver.go index b3db6a12c..ac8a0b1d0 100644 --- a/pkg/plugin/framework/action_resolver.go +++ b/pkg/plugin/framework/action_resolver.go @@ -23,14 +23,14 @@ import ( "k8s.io/apimachinery/pkg/labels" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/plugin/velero" - biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" - riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - "github.com/velero-io/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" + riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/util/collections" ) /* diff --git a/pkg/plugin/framework/action_resolver_test.go b/pkg/plugin/framework/action_resolver_test.go index 104682bd4..cf0e411da 100644 --- a/pkg/plugin/framework/action_resolver_test.go +++ b/pkg/plugin/framework/action_resolver_test.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) type mockApplicable struct { diff --git a/pkg/plugin/framework/backup_item_action.go b/pkg/plugin/framework/backup_item_action.go index ea17b0639..9c1a5665d 100644 --- a/pkg/plugin/framework/backup_item_action.go +++ b/pkg/plugin/framework/backup_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protobiav1 "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protobiav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // BackupItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/backup_item_action_client.go b/pkg/plugin/framework/backup_item_action_client.go index 1ea17fc8d..724737d01 100644 --- a/pkg/plugin/framework/backup_item_action_client.go +++ b/pkg/plugin/framework/backup_item_action_client.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protobiav1 "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protobiav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // NewBackupItemActionPlugin constructs a BackupItemActionPlugin. diff --git a/pkg/plugin/framework/backup_item_action_server.go b/pkg/plugin/framework/backup_item_action_server.go index 047e49abb..7c18b4ef6 100644 --- a/pkg/plugin/framework/backup_item_action_server.go +++ b/pkg/plugin/framework/backup_item_action_server.go @@ -24,11 +24,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" - biav1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" ) // BackupItemActionGRPCServer implements the proto-generated BackupItemAction interface, and accepts diff --git a/pkg/plugin/framework/backup_item_action_test.go b/pkg/plugin/framework/backup_item_action_test.go index 982a47c8e..1472eb115 100644 --- a/pkg/plugin/framework/backup_item_action_test.go +++ b/pkg/plugin/framework/backup_item_action_test.go @@ -27,12 +27,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v1" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBackupItemActionGRPCServerExecute(t *testing.T) { diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go index 68d969b62..903ec378c 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" ) // BackupItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go index 9dd4090de..64695dbe3 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_client.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // NewBackupItemActionPlugin constructs a BackupItemActionPlugin. diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go index b95168968..f8c894eba 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_server.go @@ -27,12 +27,12 @@ import ( timestamppb "google.golang.org/protobuf/types/known/timestamppb" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/velero" - biav2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" ) // BackupItemActionGRPCServer implements the proto-generated BackupItemAction interface, and accepts diff --git a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go index ba630554d..502c37502 100644 --- a/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go +++ b/pkg/plugin/framework/backupitemaction/v2/backup_item_action_test.go @@ -27,13 +27,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - protobiav2 "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/backupitemaction/v2" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + protobiav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/backupitemaction/v2" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestBackupItemActionGRPCServerExecute(t *testing.T) { diff --git a/pkg/plugin/framework/common/client_dispenser_test.go b/pkg/plugin/framework/common/client_dispenser_test.go index 3441cc648..3aa0cd299 100644 --- a/pkg/plugin/framework/common/client_dispenser_test.go +++ b/pkg/plugin/framework/common/client_dispenser_test.go @@ -22,7 +22,7 @@ import ( "github.com/stretchr/testify/require" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/test" ) type fakeClient struct { diff --git a/pkg/plugin/framework/common/client_errors.go b/pkg/plugin/framework/common/client_errors.go index 7a452ec5b..1d9e6c22f 100644 --- a/pkg/plugin/framework/common/client_errors.go +++ b/pkg/plugin/framework/common/client_errors.go @@ -19,7 +19,7 @@ package common import ( "google.golang.org/grpc/status" - proto "github.com/velero-io/velero/pkg/plugin/generated" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // FromGRPCError takes a gRPC status error, extracts a stack trace diff --git a/pkg/plugin/framework/common/plugin_base_test.go b/pkg/plugin/framework/common/plugin_base_test.go index f4d48de9c..e9d5ec2e2 100644 --- a/pkg/plugin/framework/common/plugin_base_test.go +++ b/pkg/plugin/framework/common/plugin_base_test.go @@ -20,7 +20,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestClientLogger(t *testing.T) { diff --git a/pkg/plugin/framework/common/plugin_config_test.go b/pkg/plugin/framework/common/plugin_config_test.go index ec5ef9ef5..53cb0fb8f 100644 --- a/pkg/plugin/framework/common/plugin_config_test.go +++ b/pkg/plugin/framework/common/plugin_config_test.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestGetPluginConfig(t *testing.T) { diff --git a/pkg/plugin/framework/common/server_errors.go b/pkg/plugin/framework/common/server_errors.go index 20ea63893..60eff50f4 100644 --- a/pkg/plugin/framework/common/server_errors.go +++ b/pkg/plugin/framework/common/server_errors.go @@ -22,8 +22,8 @@ import ( "google.golang.org/grpc/status" "google.golang.org/protobuf/protoadapt" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/util/logging" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) // NewGRPCErrorWithCode wraps err in a gRPC status error with the error's stack trace diff --git a/pkg/plugin/framework/delete_item_action.go b/pkg/plugin/framework/delete_item_action.go index 8ef51f06d..db4329b7f 100644 --- a/pkg/plugin/framework/delete_item_action.go +++ b/pkg/plugin/framework/delete_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // DeleteItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/delete_item_action_client.go b/pkg/plugin/framework/delete_item_action_client.go index b8ca2d7b8..bec5088db 100644 --- a/pkg/plugin/framework/delete_item_action_client.go +++ b/pkg/plugin/framework/delete_item_action_client.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) var _ velero.DeleteItemAction = &DeleteItemActionGRPCClient{} diff --git a/pkg/plugin/framework/delete_item_action_server.go b/pkg/plugin/framework/delete_item_action_server.go index 154ec3452..01abe8dc3 100644 --- a/pkg/plugin/framework/delete_item_action_server.go +++ b/pkg/plugin/framework/delete_item_action_server.go @@ -24,10 +24,10 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // DeleteItemActionGRPCServer implements the proto-generated DeleteItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/examples_test.go b/pkg/plugin/framework/examples_test.go index e750be8f4..41bb8395e 100644 --- a/pkg/plugin/framework/examples_test.go +++ b/pkg/plugin/framework/examples_test.go @@ -20,7 +20,7 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func ExampleNewServer_volumeSnapshotter() { diff --git a/pkg/plugin/framework/import_test.go b/pkg/plugin/framework/import_test.go index 18aa0db91..ee1439329 100644 --- a/pkg/plugin/framework/import_test.go +++ b/pkg/plugin/framework/import_test.go @@ -13,7 +13,7 @@ import ( // test that this package do not import cloud provider -// Prevent https://github.com/velero-io/velero/issues/8207 and https://github.com/velero-io/velero/issues/8157 +// Prevent https://github.com/vmware-tanzu/velero/issues/8207 and https://github.com/vmware-tanzu/velero/issues/8157 func TestPkgImportNoCloudProvider(t *testing.T) { _, filename, _, ok := runtime.Caller(0) if !ok { diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action.go index 8e7852126..2115d2ecf 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" ) // ItemBlockActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go index f1a056f93..aa597c4af 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_client.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // NewItemBlockActionPlugin constructs a ItemBlockActionPlugin. diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go index 51c5e429e..2d940550c 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_server.go @@ -24,12 +24,12 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - ibav1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" ) // ItemBlockActionGRPCServer implements the proto-generated ItemBlockAction interface, and accepts diff --git a/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go b/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go index 045e8d5a7..6e2a0e4d5 100644 --- a/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go +++ b/pkg/plugin/framework/itemblockaction/v1/item_block_action_test.go @@ -26,13 +26,13 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - protoibav1 "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - mocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/itemblockaction/v1" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + protoibav1 "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + mocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/itemblockaction/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestItemBlockActionGRPCServerGetRelatedItems(t *testing.T) { diff --git a/pkg/plugin/framework/logger.go b/pkg/plugin/framework/logger.go index 22ac4f187..b7f13e4af 100644 --- a/pkg/plugin/framework/logger.go +++ b/pkg/plugin/framework/logger.go @@ -19,7 +19,7 @@ package framework import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) // newLogger returns a logger that is suitable for use within an diff --git a/pkg/plugin/framework/logger_test.go b/pkg/plugin/framework/logger_test.go index 7899da35e..7e9ba7bf2 100644 --- a/pkg/plugin/framework/logger_test.go +++ b/pkg/plugin/framework/logger_test.go @@ -21,7 +21,7 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func TestNewLogger(t *testing.T) { diff --git a/pkg/plugin/framework/object_store.go b/pkg/plugin/framework/object_store.go index 647295a4a..ea624da42 100644 --- a/pkg/plugin/framework/object_store.go +++ b/pkg/plugin/framework/object_store.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // ObjectStorePlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/object_store_client.go b/pkg/plugin/framework/object_store_client.go index b44c06668..b59f3d1b0 100644 --- a/pkg/plugin/framework/object_store_client.go +++ b/pkg/plugin/framework/object_store_client.go @@ -25,8 +25,8 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) const byteChunkSize = 16384 diff --git a/pkg/plugin/framework/object_store_server.go b/pkg/plugin/framework/object_store_server.go index 1dc54688d..fbed21ecf 100644 --- a/pkg/plugin/framework/object_store_server.go +++ b/pkg/plugin/framework/object_store_server.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // ObjectStoreGRPCServer implements the proto-generated ObjectStoreServer interface, and accepts diff --git a/pkg/plugin/framework/plugin_lister.go b/pkg/plugin/framework/plugin_lister.go index d58b802d6..6db81c66d 100644 --- a/pkg/plugin/framework/plugin_lister.go +++ b/pkg/plugin/framework/plugin_lister.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // PluginIdentifier uniquely identifies a plugin by command, kind, and name. diff --git a/pkg/plugin/framework/restore_item_action.go b/pkg/plugin/framework/restore_item_action.go index a0cfa0b0f..26cef3728 100644 --- a/pkg/plugin/framework/restore_item_action.go +++ b/pkg/plugin/framework/restore_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // RestoreItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/restore_item_action_client.go b/pkg/plugin/framework/restore_item_action_client.go index a902417a1..3a5a633f3 100644 --- a/pkg/plugin/framework/restore_item_action_client.go +++ b/pkg/plugin/framework/restore_item_action_client.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" - riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" ) var _ riav1.RestoreItemAction = &RestoreItemActionGRPCClient{} diff --git a/pkg/plugin/framework/restore_item_action_server.go b/pkg/plugin/framework/restore_item_action_server.go index 14a90f02e..175a941bd 100644 --- a/pkg/plugin/framework/restore_item_action_server.go +++ b/pkg/plugin/framework/restore_item_action_server.go @@ -24,11 +24,11 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - "github.com/velero-io/velero/pkg/plugin/velero" - riav1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" ) // RestoreItemActionGRPCServer implements the proto-generated RestoreItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go index 606f04cdf..00bb825b8 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" ) // RestoreItemActionPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go index 40668d4c3..5e2f01c37 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_client.go @@ -26,11 +26,11 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" ) var _ riav2.RestoreItemAction = &RestoreItemActionGRPCClient{} diff --git a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go index 6a9302080..115961656 100644 --- a/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go +++ b/pkg/plugin/framework/restoreitemaction/v2/restore_item_action_server.go @@ -28,12 +28,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime/schema" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - protoriav2 "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + protoriav2 "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" ) // RestoreItemActionGRPCServer implements the proto-generated RestoreItemActionServer interface, and accepts diff --git a/pkg/plugin/framework/server.go b/pkg/plugin/framework/server.go index 58d184709..923210d55 100644 --- a/pkg/plugin/framework/server.go +++ b/pkg/plugin/framework/server.go @@ -24,11 +24,11 @@ import ( "github.com/sirupsen/logrus" "github.com/spf13/pflag" - "github.com/velero-io/velero/pkg/cmd/server/config" - biav2 "github.com/velero-io/velero/pkg/plugin/framework/backupitemaction/v2" - "github.com/velero-io/velero/pkg/plugin/framework/common" - ibav1 "github.com/velero-io/velero/pkg/plugin/framework/itemblockaction/v1" - riav2 "github.com/velero-io/velero/pkg/plugin/framework/restoreitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/cmd/server/config" + biav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/backupitemaction/v2" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + ibav1 "github.com/vmware-tanzu/velero/pkg/plugin/framework/itemblockaction/v1" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/framework/restoreitemaction/v2" ) // Server serves registered plugin implementations. diff --git a/pkg/plugin/framework/volume_snapshotter.go b/pkg/plugin/framework/volume_snapshotter.go index b54955c11..8cbb48fa4 100644 --- a/pkg/plugin/framework/volume_snapshotter.go +++ b/pkg/plugin/framework/volume_snapshotter.go @@ -22,8 +22,8 @@ import ( plugin "github.com/hashicorp/go-plugin" "google.golang.org/grpc" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // VolumeSnapshotterPlugin is an implementation of go-plugin's Plugin diff --git a/pkg/plugin/framework/volume_snapshotter_client.go b/pkg/plugin/framework/volume_snapshotter_client.go index 6af01e37d..f7af07ce4 100644 --- a/pkg/plugin/framework/volume_snapshotter_client.go +++ b/pkg/plugin/framework/volume_snapshotter_client.go @@ -26,8 +26,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" ) // NewVolumeSnapshotterPlugin constructs a VolumeSnapshotterPlugin. diff --git a/pkg/plugin/framework/volume_snapshotter_server.go b/pkg/plugin/framework/volume_snapshotter_server.go index 95050afb8..de30c823f 100644 --- a/pkg/plugin/framework/volume_snapshotter_server.go +++ b/pkg/plugin/framework/volume_snapshotter_server.go @@ -24,9 +24,9 @@ import ( "github.com/pkg/errors" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/pkg/plugin/framework/common" - proto "github.com/velero-io/velero/pkg/plugin/generated" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + proto "github.com/vmware-tanzu/velero/pkg/plugin/generated" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // VolumeSnapshotterGRPCServer implements the proto-generated VolumeSnapshotterServer interface, and accepts diff --git a/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go b/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go index 3c8f740d1..5eb2c852b 100644 --- a/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go +++ b/pkg/plugin/generated/backupitemaction/v2/BackupItemAction.pb.go @@ -7,7 +7,7 @@ package v2 import ( - generated "github.com/velero-io/velero/pkg/plugin/generated" + generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" emptypb "google.golang.org/protobuf/types/known/emptypb" diff --git a/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go b/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go index ffa395a39..cec604477 100644 --- a/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go +++ b/pkg/plugin/generated/itemblockaction/v1/ItemBlockAction.pb.go @@ -7,7 +7,7 @@ package v1 import ( - generated "github.com/velero-io/velero/pkg/plugin/generated" + generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" reflect "reflect" diff --git a/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go b/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go index 0063e6158..a7bbc421e 100644 --- a/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go +++ b/pkg/plugin/generated/restoreitemaction/v2/RestoreItemAction.pb.go @@ -7,7 +7,7 @@ package v2 import ( - generated "github.com/velero-io/velero/pkg/plugin/generated" + generated "github.com/vmware-tanzu/velero/pkg/plugin/generated" protoreflect "google.golang.org/protobuf/reflect/protoreflect" protoimpl "google.golang.org/protobuf/runtime/protoimpl" durationpb "google.golang.org/protobuf/types/known/durationpb" diff --git a/pkg/plugin/mocks/manager.go b/pkg/plugin/mocks/manager.go index 0c2219dc0..c12510fdd 100644 --- a/pkg/plugin/mocks/manager.go +++ b/pkg/plugin/mocks/manager.go @@ -4,19 +4,19 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - itemblockactionv1 "github.com/velero-io/velero/pkg/plugin/velero/itemblockaction/v1" + itemblockactionv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/itemblockaction/v1" - restoreitemactionv1 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v1" + restoreitemactionv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v1" - restoreitemactionv2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" + restoreitemactionv2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" - v1 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v1" + v1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v1" - v2 "github.com/velero-io/velero/pkg/plugin/velero/backupitemaction/v2" + v2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/backupitemaction/v2" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" - volumesnapshotterv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" + volumesnapshotterv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" ) // Manager is an autogenerated mock type for the Manager type diff --git a/pkg/plugin/mocks/process_factory.go b/pkg/plugin/mocks/process_factory.go index 5325a6a9f..586e31121 100644 --- a/pkg/plugin/mocks/process_factory.go +++ b/pkg/plugin/mocks/process_factory.go @@ -21,7 +21,7 @@ import ( logrus "github.com/sirupsen/logrus" mock "github.com/stretchr/testify/mock" - process "github.com/velero-io/velero/pkg/plugin/clientmgmt/process" + process "github.com/vmware-tanzu/velero/pkg/plugin/clientmgmt/process" ) // ProcessFactory is an autogenerated mock type for the ProcessFactory type diff --git a/pkg/plugin/proto/BackupItemAction.proto b/pkg/plugin/proto/BackupItemAction.proto index 5d89e2a87..66111300a 100644 --- a/pkg/plugin/proto/BackupItemAction.proto +++ b/pkg/plugin/proto/BackupItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/DeleteItemAction.proto b/pkg/plugin/proto/DeleteItemAction.proto index 34c1924c9..f2838fe0c 100644 --- a/pkg/plugin/proto/DeleteItemAction.proto +++ b/pkg/plugin/proto/DeleteItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/ObjectStore.proto b/pkg/plugin/proto/ObjectStore.proto index 49e493789..4487a0cef 100644 --- a/pkg/plugin/proto/ObjectStore.proto +++ b/pkg/plugin/proto/ObjectStore.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/PluginLister.proto b/pkg/plugin/proto/PluginLister.proto index d2300924d..55cfe62de 100644 --- a/pkg/plugin/proto/PluginLister.proto +++ b/pkg/plugin/proto/PluginLister.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/RestoreItemAction.proto b/pkg/plugin/proto/RestoreItemAction.proto index 57ca235a4..ae9c3ddd9 100644 --- a/pkg/plugin/proto/RestoreItemAction.proto +++ b/pkg/plugin/proto/RestoreItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/Shared.proto b/pkg/plugin/proto/Shared.proto index d59f548af..dd12a7ee7 100644 --- a/pkg/plugin/proto/Shared.proto +++ b/pkg/plugin/proto/Shared.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "google/protobuf/timestamp.proto"; diff --git a/pkg/plugin/proto/VolumeSnapshotter.proto b/pkg/plugin/proto/VolumeSnapshotter.proto index 36da5b704..affb762bc 100644 --- a/pkg/plugin/proto/VolumeSnapshotter.proto +++ b/pkg/plugin/proto/VolumeSnapshotter.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package generated; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated"; import "Shared.proto"; diff --git a/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto b/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto index 8479d7f42..36f067fe2 100644 --- a/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto +++ b/pkg/plugin/proto/backupitemaction/v2/BackupItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v2; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated/backupitemaction/v2"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/backupitemaction/v2"; import "Shared.proto"; import "google/protobuf/empty.proto"; diff --git a/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto b/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto index 71b350044..5c0f86a3d 100644 --- a/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto +++ b/pkg/plugin/proto/itemblockaction/v1/ItemBlockAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v1; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated/itemblockaction/v1"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/itemblockaction/v1"; import "Shared.proto"; diff --git a/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto b/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto index 614544025..a3e969114 100644 --- a/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto +++ b/pkg/plugin/proto/restoreitemaction/v2/RestoreItemAction.proto @@ -1,6 +1,6 @@ syntax = "proto3"; package v2; -option go_package = "github.com/velero-io/velero/pkg/plugin/generated/restoreitemaction/v2"; +option go_package = "github.com/vmware-tanzu/velero/pkg/plugin/generated/restoreitemaction/v2"; import "Shared.proto"; import "google/protobuf/empty.proto"; diff --git a/pkg/plugin/utils/volumehelper/volume_policy_helper.go b/pkg/plugin/utils/volumehelper/volume_policy_helper.go index 84675cafb..843c23b06 100644 --- a/pkg/plugin/utils/volumehelper/volume_policy_helper.go +++ b/pkg/plugin/utils/volumehelper/volume_policy_helper.go @@ -22,12 +22,12 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/resourcepolicies" - "github.com/velero-io/velero/internal/volumehelper" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/boolptr" - podvolumeutil "github.com/velero-io/velero/pkg/util/podvolume" - vhutil "github.com/velero-io/velero/pkg/util/volumehelper" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/volumehelper" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + podvolumeutil "github.com/vmware-tanzu/velero/pkg/util/podvolume" + vhutil "github.com/vmware-tanzu/velero/pkg/util/volumehelper" ) // ShouldPerformSnapshotWithBackup is used for third-party plugins. diff --git a/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go b/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go index cebc4641e..08b23ae04 100644 --- a/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go +++ b/pkg/plugin/utils/volumehelper/volume_policy_helper_test.go @@ -26,10 +26,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/internal/volumehelper" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/volumehelper" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestShouldPerformSnapshotWithBackup(t *testing.T) { diff --git a/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go b/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go index 0a823e3ca..35566d98a 100644 --- a/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go +++ b/pkg/plugin/velero/backupitemaction/v1/backup_item_action.go @@ -19,8 +19,8 @@ package v1 import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // BackupItemAction is an actor that performs an operation on an individual item being backed up. diff --git a/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go b/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go index 4566eafd6..3c23802f2 100644 --- a/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go +++ b/pkg/plugin/velero/backupitemaction/v2/backup_item_action.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // BackupItemAction is an actor that performs an operation on an individual item being backed up. diff --git a/pkg/plugin/velero/delete_item_action.go b/pkg/plugin/velero/delete_item_action.go index afd8ebbb2..e3e7d9259 100644 --- a/pkg/plugin/velero/delete_item_action.go +++ b/pkg/plugin/velero/delete_item_action.go @@ -19,7 +19,7 @@ package velero import ( "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // DeleteItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/plugin/velero/itemblockaction/v1/item_block_action.go b/pkg/plugin/velero/itemblockaction/v1/item_block_action.go index c8d6e020c..6d0133700 100644 --- a/pkg/plugin/velero/itemblockaction/v1/item_block_action.go +++ b/pkg/plugin/velero/itemblockaction/v1/item_block_action.go @@ -19,8 +19,8 @@ package v1 import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // ItemBlockAction is an action that returns a list of related items that must be backed up diff --git a/pkg/plugin/velero/mocks/DeleteItemAction.go b/pkg/plugin/velero/mocks/DeleteItemAction.go index c75eb32e9..101e04fde 100644 --- a/pkg/plugin/velero/mocks/DeleteItemAction.go +++ b/pkg/plugin/velero/mocks/DeleteItemAction.go @@ -4,7 +4,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // DeleteItemAction is an autogenerated mock type for the DeleteItemAction type diff --git a/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go b/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go index d6fba5904..cfca2ef6d 100644 --- a/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go +++ b/pkg/plugin/velero/mocks/backupitemaction/v1/BackupItemAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // BackupItemAction is an autogenerated mock type for the BackupItemAction type diff --git a/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go b/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go index e30ffeb67..426442477 100644 --- a/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go +++ b/pkg/plugin/velero/mocks/backupitemaction/v2/BackupItemAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // BackupItemAction is an autogenerated mock type for the BackupItemAction type diff --git a/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go b/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go index b07bb63f4..95a8d960a 100644 --- a/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go +++ b/pkg/plugin/velero/mocks/itemblockaction/v1/ItemBlockAction.go @@ -21,9 +21,9 @@ import ( mock "github.com/stretchr/testify/mock" runtime "k8s.io/apimachinery/pkg/runtime" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // ItemBlockAction is an autogenerated mock type for the ItemBlockAction type diff --git a/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go b/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go index bd4b7d56d..1bacf7b16 100644 --- a/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go +++ b/pkg/plugin/velero/mocks/restoreitemaction/v1/RestoreItemAction.go @@ -19,7 +19,7 @@ package v1 import ( mock "github.com/stretchr/testify/mock" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RestoreItemAction is an autogenerated mock type for the RestoreItemAction type diff --git a/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go b/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go index 18b4af19d..647e8b6dc 100644 --- a/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go +++ b/pkg/plugin/velero/mocks/restoreitemaction/v2/RestoreItemAction.go @@ -19,9 +19,9 @@ package v2 import ( mock "github.com/stretchr/testify/mock" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velero "github.com/velero-io/velero/pkg/plugin/velero" + velero "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RestoreItemAction is an autogenerated mock type for the RestoreItemAction type diff --git a/pkg/plugin/velero/restore_item_action_shared.go b/pkg/plugin/velero/restore_item_action_shared.go index 27f3d0622..a8e285b0c 100644 --- a/pkg/plugin/velero/restore_item_action_shared.go +++ b/pkg/plugin/velero/restore_item_action_shared.go @@ -21,7 +21,7 @@ import ( "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // RestoreItemActionExecuteInput contains the input parameters for the ItemAction's Execute function. diff --git a/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go b/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go index ec316e789..3398af9e1 100644 --- a/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go +++ b/pkg/plugin/velero/restoreitemaction/v1/restore_item_action.go @@ -17,7 +17,7 @@ limitations under the License. package v1 import ( - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RestoreItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go b/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go index 8d66b6ef4..dfc35428f 100644 --- a/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go +++ b/pkg/plugin/velero/restoreitemaction/v2/restore_item_action.go @@ -21,8 +21,8 @@ import ( "github.com/pkg/errors" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RestoreItemAction is an actor that performs an operation on an individual item being restored. diff --git a/pkg/podexec/pod_command_executor.go b/pkg/podexec/pod_command_executor.go index 94cda5ac3..0dbc28e95 100644 --- a/pkg/podexec/pod_command_executor.go +++ b/pkg/podexec/pod_command_executor.go @@ -31,7 +31,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/remotecommand" - api "github.com/velero-io/velero/pkg/apis/velero/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) const defaultTimeout = 30 * time.Second diff --git a/pkg/podexec/pod_command_executor_test.go b/pkg/podexec/pod_command_executor_test.go index 34878df70..3286ba42d 100644 --- a/pkg/podexec/pod_command_executor_test.go +++ b/pkg/podexec/pod_command_executor_test.go @@ -37,8 +37,8 @@ import ( "k8s.io/client-go/tools/remotecommand" "k8s.io/utils/ptr" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewPodCommandExecutor(t *testing.T) { diff --git a/pkg/podvolume/backup_micro_service.go b/pkg/podvolume/backup_micro_service.go index e4c80c6e2..d393b2bcb 100644 --- a/pkg/podvolume/backup_micro_service.go +++ b/pkg/podvolume/backup_micro_service.go @@ -31,12 +31,12 @@ import ( cachetool "k8s.io/client-go/tools/cache" "sigs.k8s.io/controller-runtime/pkg/cache" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/podvolume/backup_micro_service_test.go b/pkg/podvolume/backup_micro_service_test.go index 2461b055d..bec46f353 100644 --- a/pkg/podvolume/backup_micro_service_test.go +++ b/pkg/podvolume/backup_micro_service_test.go @@ -30,19 +30,19 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/uploader" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" ) type backupMsTestHelper struct { diff --git a/pkg/podvolume/backupper.go b/pkg/podvolume/backupper.go index b680b79fc..6b534d5ed 100644 --- a/pkg/podvolume/backupper.go +++ b/pkg/podvolume/backupper.go @@ -30,17 +30,17 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/resourcepolicies" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - veleroclient "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/podvolume/configs" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - uploaderutil "github.com/velero-io/velero/pkg/uploader/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/podvolume/configs" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( @@ -371,7 +371,7 @@ func (b *backupper) BackupPodVolumes(backup *velerov1api.Backup, pod *corev1api. continue } // similar with above: the PVB may be handled very quickly by the controller and the informer handler will call "b.wg.Done()" before "b.wg.Add(1)" runs which causes panic - // see https://github.com/velero-io/velero/issues/8657 + // see https://github.com/vmware-tanzu/velero/issues/8657 b.wg.Add(1) if err := veleroclient.CreateRetryGenerateName(b.crClient, b.ctx, volumeBackup); err != nil { b.wg.Done() @@ -397,7 +397,7 @@ func (b *backupper) WaitAllPodVolumesProcessed(log logrus.FieldLogger) []*velero var podVolumeBackups []*velerov1api.PodVolumeBackup // if no pod volume backups are tracked, return directly to avoid issue mentioned in - // https://github.com/velero-io/velero/issues/8723 + // https://github.com/vmware-tanzu/velero/issues/8723 if len(b.pvbIndexer.List()) == 0 { return podVolumeBackups } diff --git a/pkg/podvolume/backupper_factory.go b/pkg/podvolume/backupper_factory.go index 64bdbeb60..f75f1d30b 100644 --- a/pkg/podvolume/backupper_factory.go +++ b/pkg/podvolume/backupper_factory.go @@ -25,8 +25,8 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" ) // BackupperFactory can construct pod volumes backuppers. diff --git a/pkg/podvolume/backupper_test.go b/pkg/podvolume/backupper_test.go index 45a32225a..e6042ede1 100644 --- a/pkg/podvolume/backupper_test.go +++ b/pkg/podvolume/backupper_test.go @@ -36,11 +36,11 @@ import ( clientTesting "k8s.io/client-go/testing" "k8s.io/client-go/tools/cache" - "github.com/velero-io/velero/internal/resourcepolicies" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/repository" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/repository" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) type fakeInformerRegistration struct{} diff --git a/pkg/podvolume/mocks/restorer.go b/pkg/podvolume/mocks/restorer.go index eb0fd9f2e..56de97f44 100644 --- a/pkg/podvolume/mocks/restorer.go +++ b/pkg/podvolume/mocks/restorer.go @@ -4,9 +4,9 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - podvolume "github.com/velero-io/velero/pkg/podvolume" + podvolume "github.com/vmware-tanzu/velero/pkg/podvolume" - volume "github.com/velero-io/velero/internal/volume" + volume "github.com/vmware-tanzu/velero/internal/volume" ) // Restorer is an autogenerated mock type for the Restorer type diff --git a/pkg/podvolume/restore_micro_service.go b/pkg/podvolume/restore_micro_service.go index 49fcc81c4..77e84eb04 100644 --- a/pkg/podvolume/restore_micro_service.go +++ b/pkg/podvolume/restore_micro_service.go @@ -32,12 +32,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/cache" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/kube" cachetool "k8s.io/client-go/tools/cache" ) diff --git a/pkg/podvolume/restore_micro_service_test.go b/pkg/podvolume/restore_micro_service_test.go index 72a1001df..1d25e342f 100644 --- a/pkg/podvolume/restore_micro_service_test.go +++ b/pkg/podvolume/restore_micro_service_test.go @@ -31,19 +31,19 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/datapath" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/datapath" + "github.com/vmware-tanzu/velero/pkg/uploader" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - datapathmockes "github.com/velero-io/velero/pkg/datapath/mocks" + datapathmockes "github.com/vmware-tanzu/velero/pkg/datapath/mocks" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" ) diff --git a/pkg/podvolume/restorer.go b/pkg/podvolume/restorer.go index 89b054dc8..ce662d5de 100644 --- a/pkg/podvolume/restorer.go +++ b/pkg/podvolume/restorer.go @@ -21,7 +21,7 @@ import ( "sync" "time" - "github.com/velero-io/velero/internal/volume" + "github.com/vmware-tanzu/velero/internal/volume" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -33,14 +33,14 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - veleroclient "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/nodeagent" - "github.com/velero-io/velero/pkg/repository" - uploaderutil "github.com/velero-io/velero/pkg/uploader/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/nodeagent" + "github.com/vmware-tanzu/velero/pkg/repository" + uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type RestoreData struct { diff --git a/pkg/podvolume/restorer_factory.go b/pkg/podvolume/restorer_factory.go index 963230900..178d720c8 100644 --- a/pkg/podvolume/restorer_factory.go +++ b/pkg/podvolume/restorer_factory.go @@ -26,8 +26,8 @@ import ( ctrlcache "sigs.k8s.io/controller-runtime/pkg/cache" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" ) // RestorerFactory can construct pod volumes restorers. diff --git a/pkg/podvolume/restorer_test.go b/pkg/podvolume/restorer_test.go index 687152ae7..bd67e8480 100644 --- a/pkg/podvolume/restorer_test.go +++ b/pkg/podvolume/restorer_test.go @@ -33,11 +33,11 @@ import ( kubefake "k8s.io/client-go/kubernetes/fake" "k8s.io/client-go/tools/cache" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/repository" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/repository" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestGetVolumesRepositoryType(t *testing.T) { diff --git a/pkg/podvolume/snaphost_tracker_test.go b/pkg/podvolume/snaphost_tracker_test.go index 973d1503b..0f89eb903 100644 --- a/pkg/podvolume/snaphost_tracker_test.go +++ b/pkg/podvolume/snaphost_tracker_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/builder" ) func TestOptoutVolume(t *testing.T) { diff --git a/pkg/podvolume/util.go b/pkg/podvolume/util.go index 0f1fd5ad7..bb827c732 100644 --- a/pkg/podvolume/util.go +++ b/pkg/podvolume/util.go @@ -23,10 +23,10 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/podvolume/configs" - repotypes "github.com/velero-io/velero/pkg/repository/types" - "github.com/velero-io/velero/pkg/uploader" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/podvolume/configs" + repotypes "github.com/vmware-tanzu/velero/pkg/repository/types" + "github.com/vmware-tanzu/velero/pkg/uploader" ) const ( @@ -87,8 +87,8 @@ func getVolumeBackupInfoForPod(podVolumeBackups []*velerov1api.PodVolumeBackup, } // If the volume came from a projected or DownwardAPI source, skip its restore. - // This allows backups affected by https://github.com/velero-io/velero/issues/3863 - // or https://github.com/velero-io/velero/issues/4053 to be restored successfully. + // This allows backups affected by https://github.com/vmware-tanzu/velero/issues/3863 + // or https://github.com/vmware-tanzu/velero/issues/4053 to be restored successfully. if volumeHasNonRestorableSource(pvb.Spec.Volume, pod.Spec.Volumes) { continue } diff --git a/pkg/podvolume/util_test.go b/pkg/podvolume/util_test.go index 6fd86bee6..bfd33e55e 100644 --- a/pkg/podvolume/util_test.go +++ b/pkg/podvolume/util_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" corev1api "k8s.io/api/core/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" ) func TestGetVolumeBackupsForPod(t *testing.T) { diff --git a/pkg/repository/backup_repo_op.go b/pkg/repository/backup_repo_op.go index 011abffd0..36356e7af 100644 --- a/pkg/repository/backup_repo_op.go +++ b/pkg/repository/backup_repo_op.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/labels" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/label" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/label" ) // A BackupRepositoryKey uniquely identify a backup repository diff --git a/pkg/repository/backup_repo_op_test.go b/pkg/repository/backup_repo_op_test.go index b50e26e4e..de53cfbe7 100644 --- a/pkg/repository/backup_repo_op_test.go +++ b/pkg/repository/backup_repo_op_test.go @@ -29,9 +29,9 @@ import ( "github.com/stretchr/testify/require" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func buildBackupRepo(key BackupRepositoryKey, phase velerov1api.BackupRepositoryPhase, seqNum string) velerov1api.BackupRepository { diff --git a/pkg/repository/config/azure.go b/pkg/repository/config/azure.go index 044700f31..6662d13c6 100644 --- a/pkg/repository/config/azure.go +++ b/pkg/repository/config/azure.go @@ -19,7 +19,7 @@ package config import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/util/azure" + "github.com/vmware-tanzu/velero/pkg/util/azure" ) // GetAzureResticEnvVars gets the environment variables that restic diff --git a/pkg/repository/config/azure_test.go b/pkg/repository/config/azure_test.go index b76b22edb..605987d37 100644 --- a/pkg/repository/config/azure_test.go +++ b/pkg/repository/config/azure_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/util/azure" + "github.com/vmware-tanzu/velero/pkg/util/azure" ) func TestGetAzureResticEnvVars(t *testing.T) { diff --git a/pkg/repository/ensurer.go b/pkg/repository/ensurer.go index f399b2437..91cdb0d9e 100644 --- a/pkg/repository/ensurer.go +++ b/pkg/repository/ensurer.go @@ -27,7 +27,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" apierrors "k8s.io/apimachinery/pkg/api/errors" ) diff --git a/pkg/repository/ensurer_test.go b/pkg/repository/ensurer_test.go index 8b8b4b81d..b2d60eb21 100644 --- a/pkg/repository/ensurer_test.go +++ b/pkg/repository/ensurer_test.go @@ -26,8 +26,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestEnsureRepo(t *testing.T) { diff --git a/pkg/repository/keys/keys.go b/pkg/repository/keys/keys.go index eebd10613..21423afe0 100644 --- a/pkg/repository/keys/keys.go +++ b/pkg/repository/keys/keys.go @@ -26,7 +26,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/velero-io/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/builder" ) const ( diff --git a/pkg/repository/maintenance/maintenance.go b/pkg/repository/maintenance/maintenance.go index 9a6b118db..747d89f52 100644 --- a/pkg/repository/maintenance/maintenance.go +++ b/pkg/repository/maintenance/maintenance.go @@ -37,14 +37,14 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/constant" - velerolabel "github.com/velero-io/velero/pkg/label" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/constant" + velerolabel "github.com/vmware-tanzu/velero/pkg/label" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ) const ( diff --git a/pkg/repository/maintenance/maintenance_test.go b/pkg/repository/maintenance/maintenance_test.go index d501e241d..97eee1148 100644 --- a/pkg/repository/maintenance/maintenance_test.go +++ b/pkg/repository/maintenance/maintenance_test.go @@ -38,15 +38,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerolabel "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/repository/provider" - velerotest "github.com/velero-io/velero/pkg/test" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/logging" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerolabel "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/repository/provider" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/logging" ) func TestGenerateJobName(t *testing.T) { diff --git a/pkg/repository/manager/manager.go b/pkg/repository/manager/manager.go index d22288e85..4d03931c0 100644 --- a/pkg/repository/manager/manager.go +++ b/pkg/repository/manager/manager.go @@ -25,11 +25,11 @@ import ( "github.com/sirupsen/logrus" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/repository/provider" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/repository/provider" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // Manager manages backup repositories. diff --git a/pkg/repository/manager/manager_test.go b/pkg/repository/manager/manager_test.go index b3312a636..88d8db481 100644 --- a/pkg/repository/manager/manager_test.go +++ b/pkg/repository/manager/manager_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/require" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestGetRepositoryProvider(t *testing.T) { diff --git a/pkg/repository/mocks/Manager.go b/pkg/repository/mocks/Manager.go index 9ef8ea889..954967adc 100644 --- a/pkg/repository/mocks/Manager.go +++ b/pkg/repository/mocks/Manager.go @@ -9,7 +9,7 @@ import ( time "time" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // Manager is an autogenerated mock type for the Manager type diff --git a/pkg/repository/provider/provider.go b/pkg/repository/provider/provider.go index 301c45834..7681d830b 100644 --- a/pkg/repository/provider/provider.go +++ b/pkg/repository/provider/provider.go @@ -20,7 +20,7 @@ import ( "context" "time" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // RepoParam includes the parameters to manipulate a backup repository diff --git a/pkg/repository/provider/unified_repo.go b/pkg/repository/provider/unified_repo.go index 27e20cae7..2af59f190 100644 --- a/pkg/repository/provider/unified_repo.go +++ b/pkg/repository/provider/unified_repo.go @@ -30,12 +30,12 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - repoconfig "github.com/velero-io/velero/pkg/repository/config" - repokey "github.com/velero-io/velero/pkg/repository/keys" - "github.com/velero-io/velero/pkg/repository/udmrepo" - reposervice "github.com/velero-io/velero/pkg/repository/udmrepo/service" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + repoconfig "github.com/vmware-tanzu/velero/pkg/repository/config" + repokey "github.com/vmware-tanzu/velero/pkg/repository/keys" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + reposervice "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/service" ) type unifiedRepoProvider struct { diff --git a/pkg/repository/provider/unified_repo_test.go b/pkg/repository/provider/unified_repo_test.go index d8f5b1975..e0e0a8b8f 100644 --- a/pkg/repository/provider/unified_repo_test.go +++ b/pkg/repository/provider/unified_repo_test.go @@ -30,12 +30,12 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerocredentials "github.com/velero-io/velero/internal/credentials" - credmock "github.com/velero-io/velero/internal/credentials/mocks" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository/udmrepo" - reposervicenmocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + velerocredentials "github.com/vmware-tanzu/velero/internal/credentials" + credmock "github.com/vmware-tanzu/velero/internal/credentials/mocks" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + reposervicenmocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestGetStorageCredentials(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/azure.go b/pkg/repository/udmrepo/kopialib/backend/azure.go index 55bb79e43..79bf1bbc2 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure.go @@ -23,9 +23,9 @@ import ( "github.com/kopia/kopia/repo/blob" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/azure" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/azure" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type AzureBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go b/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go index 541b7c82d..5e2443a42 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure/azure_storage_wrapper.go @@ -23,9 +23,9 @@ import ( "github.com/kopia/kopia/repo/blob/azure" "github.com/kopia/kopia/repo/blob/throttling" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" - azureutil "github.com/velero-io/velero/pkg/util/azure" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" + azureutil "github.com/vmware-tanzu/velero/pkg/util/azure" ) const ( diff --git a/pkg/repository/udmrepo/kopialib/backend/azure_test.go b/pkg/repository/udmrepo/kopialib/backend/azure_test.go index e10517997..b4504986e 100644 --- a/pkg/repository/udmrepo/kopialib/backend/azure_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/azure_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" "github.com/kopia/kopia/repo/blob/throttling" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) func TestAzureSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/common.go b/pkg/repository/udmrepo/kopialib/backend/common.go index 900857946..7af061204 100644 --- a/pkg/repository/udmrepo/kopialib/backend/common.go +++ b/pkg/repository/udmrepo/kopialib/backend/common.go @@ -29,7 +29,7 @@ import ( "github.com/kopia/kopia/repo/hashing" "github.com/kopia/kopia/repo/splitter" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) const ( diff --git a/pkg/repository/udmrepo/kopialib/backend/common_test.go b/pkg/repository/udmrepo/kopialib/backend/common_test.go index 2f9773e73..1083bca9a 100644 --- a/pkg/repository/udmrepo/kopialib/backend/common_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/common_test.go @@ -28,7 +28,7 @@ import ( "github.com/kopia/kopia/repo/splitter" "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) func TestSetupNewRepositoryOptions(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/file_system.go b/pkg/repository/udmrepo/kopialib/backend/file_system.go index 9680fa8bd..f0999e832 100644 --- a/pkg/repository/udmrepo/kopialib/backend/file_system.go +++ b/pkg/repository/udmrepo/kopialib/backend/file_system.go @@ -27,8 +27,8 @@ import ( "github.com/kopia/kopia/repo/blob/filesystem" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type FsBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/file_system_test.go b/pkg/repository/udmrepo/kopialib/backend/file_system_test.go index 92fca43ae..33e608efd 100644 --- a/pkg/repository/udmrepo/kopialib/backend/file_system_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/file_system_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" "github.com/kopia/kopia/repo/blob/filesystem" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) func TestFSSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/gcs.go b/pkg/repository/udmrepo/kopialib/backend/gcs.go index 6a10b6010..2c46609a4 100644 --- a/pkg/repository/udmrepo/kopialib/backend/gcs.go +++ b/pkg/repository/udmrepo/kopialib/backend/gcs.go @@ -24,8 +24,8 @@ import ( "github.com/kopia/kopia/repo/blob" "github.com/kopia/kopia/repo/blob/gcs" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type GCSBackend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/gcs_test.go b/pkg/repository/udmrepo/kopialib/backend/gcs_test.go index a782e0375..3398c35c2 100644 --- a/pkg/repository/udmrepo/kopialib/backend/gcs_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/gcs_test.go @@ -19,13 +19,13 @@ package backend import ( "testing" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" "github.com/kopia/kopia/repo/blob/gcs" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) func TestGcsSetup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/s3.go b/pkg/repository/udmrepo/kopialib/backend/s3.go index 25e27dddc..202c3c449 100644 --- a/pkg/repository/udmrepo/kopialib/backend/s3.go +++ b/pkg/repository/udmrepo/kopialib/backend/s3.go @@ -24,8 +24,8 @@ import ( "github.com/kopia/kopia/repo/blob" "github.com/kopia/kopia/repo/blob/s3" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/logging" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/logging" ) type S3Backend struct { diff --git a/pkg/repository/udmrepo/kopialib/backend/s3_test.go b/pkg/repository/udmrepo/kopialib/backend/s3_test.go index 58a2d4d6d..3e1b045c4 100644 --- a/pkg/repository/udmrepo/kopialib/backend/s3_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/s3_test.go @@ -19,12 +19,12 @@ package backend import ( "testing" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" "github.com/kopia/kopia/repo/blob/s3" "github.com/stretchr/testify/assert" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) func TestS3Setup(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/backend/utils_test.go b/pkg/repository/udmrepo/kopialib/backend/utils_test.go index 4e57bafd0..24923e447 100644 --- a/pkg/repository/udmrepo/kopialib/backend/utils_test.go +++ b/pkg/repository/udmrepo/kopialib/backend/utils_test.go @@ -25,7 +25,7 @@ import ( "go.uber.org/zap" "go.uber.org/zap/zapcore" - storagemocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + storagemocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" ) func TestOptionalHaveBool(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/lib_repo.go b/pkg/repository/udmrepo/kopialib/lib_repo.go index fc1e50d63..2131baa5c 100644 --- a/pkg/repository/udmrepo/kopialib/lib_repo.go +++ b/pkg/repository/udmrepo/kopialib/lib_repo.go @@ -38,9 +38,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/kopia" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" + "github.com/vmware-tanzu/velero/pkg/kopia" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" ) type kopiaRepoService struct { diff --git a/pkg/repository/udmrepo/kopialib/lib_repo_test.go b/pkg/repository/udmrepo/kopialib/lib_repo_test.go index c3c778f66..1776f9be0 100644 --- a/pkg/repository/udmrepo/kopialib/lib_repo_test.go +++ b/pkg/repository/udmrepo/kopialib/lib_repo_test.go @@ -36,10 +36,10 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" - repomocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + repomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestOpen(t *testing.T) { diff --git a/pkg/repository/udmrepo/kopialib/repo_init.go b/pkg/repository/udmrepo/kopialib/repo_init.go index da6fe022d..ade9039d7 100644 --- a/pkg/repository/udmrepo/kopialib/repo_init.go +++ b/pkg/repository/udmrepo/kopialib/repo_init.go @@ -32,9 +32,9 @@ import ( "github.com/kopia/kopia/repo/maintenance" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/kopia" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" + "github.com/vmware-tanzu/velero/pkg/kopia" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" ) type kopiaBackendStore struct { diff --git a/pkg/repository/udmrepo/kopialib/repo_init_test.go b/pkg/repository/udmrepo/kopialib/repo_init_test.go index a71089d75..3b8a52be2 100644 --- a/pkg/repository/udmrepo/kopialib/repo_init_test.go +++ b/pkg/repository/udmrepo/kopialib/repo_init_test.go @@ -27,16 +27,16 @@ import ( "github.com/kopia/kopia/repo/maintenance" "github.com/kopia/kopia/repo/manifest" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend" - repomocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" - storagemocks "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend" + repomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" + storagemocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib/backend/mocks" "github.com/pkg/errors" ) diff --git a/pkg/repository/udmrepo/mocks/BackupRepo.go b/pkg/repository/udmrepo/mocks/BackupRepo.go index 6ca2648bc..623c4d70d 100644 --- a/pkg/repository/udmrepo/mocks/BackupRepo.go +++ b/pkg/repository/udmrepo/mocks/BackupRepo.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) // NewBackupRepo creates a new instance of BackupRepo. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/mocks/BackupRepoService.go b/pkg/repository/udmrepo/mocks/BackupRepoService.go index b5be1d866..34a24ef97 100644 --- a/pkg/repository/udmrepo/mocks/BackupRepoService.go +++ b/pkg/repository/udmrepo/mocks/BackupRepoService.go @@ -9,7 +9,7 @@ import ( "time" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) // NewBackupRepoService creates a new instance of BackupRepoService. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/mocks/ObjectWriter.go b/pkg/repository/udmrepo/mocks/ObjectWriter.go index 26d38eba0..d50a3ce76 100644 --- a/pkg/repository/udmrepo/mocks/ObjectWriter.go +++ b/pkg/repository/udmrepo/mocks/ObjectWriter.go @@ -6,7 +6,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" ) // NewObjectWriter creates a new instance of ObjectWriter. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/repository/udmrepo/service/service.go b/pkg/repository/udmrepo/service/service.go index 1f76c7c38..195b67b11 100644 --- a/pkg/repository/udmrepo/service/service.go +++ b/pkg/repository/udmrepo/service/service.go @@ -19,8 +19,8 @@ package service import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/kopialib" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/kopialib" ) // Create creates an instance of BackupRepoService diff --git a/pkg/restic/common.go b/pkg/restic/common.go index 572c0f7ad..a5bf05c44 100644 --- a/pkg/restic/common.go +++ b/pkg/restic/common.go @@ -26,10 +26,10 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - repoconfig "github.com/velero-io/velero/pkg/repository/config" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + repoconfig "github.com/vmware-tanzu/velero/pkg/repository/config" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) const ( diff --git a/pkg/restic/common_test.go b/pkg/restic/common_test.go index 590152fa9..97363340c 100644 --- a/pkg/restic/common_test.go +++ b/pkg/restic/common_test.go @@ -24,8 +24,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestTempCACertFile(t *testing.T) { diff --git a/pkg/restic/exec_commands.go b/pkg/restic/exec_commands.go index ed5e2274d..94c17c04a 100644 --- a/pkg/restic/exec_commands.go +++ b/pkg/restic/exec_commands.go @@ -26,9 +26,9 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/exec" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) const restoreProgressCheckInterval = 10 * time.Second diff --git a/pkg/restic/exec_commands_test.go b/pkg/restic/exec_commands_test.go index 5994c948c..370f6653c 100644 --- a/pkg/restic/exec_commands_test.go +++ b/pkg/restic/exec_commands_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) func Test_getSummaryLine(t *testing.T) { diff --git a/pkg/restore/actions/add_pvc_from_pod_action.go b/pkg/restore/actions/add_pvc_from_pod_action.go index 3ae6ee804..3e88f796a 100644 --- a/pkg/restore/actions/add_pvc_from_pod_action.go +++ b/pkg/restore/actions/add_pvc_from_pod_action.go @@ -22,8 +22,8 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) type AddPVCFromPodAction struct { diff --git a/pkg/restore/actions/add_pvc_from_pod_action_test.go b/pkg/restore/actions/add_pvc_from_pod_action_test.go index b94c82e70..5d27e1582 100644 --- a/pkg/restore/actions/add_pvc_from_pod_action_test.go +++ b/pkg/restore/actions/add_pvc_from_pod_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestAddPVCFromPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/admissionwebhook_config_action.go b/pkg/restore/actions/admissionwebhook_config_action.go index e2bd07257..82599dc62 100644 --- a/pkg/restore/actions/admissionwebhook_config_action.go +++ b/pkg/restore/actions/admissionwebhook_config_action.go @@ -22,12 +22,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // AdmissionWebhookConfigurationAction is a RestoreItemAction plugin applicable to mutatingwebhookconfiguration and // validatingwebhookconfiguration to reset the invalid value for "sideEffects" of the webhooks. -// More background please refer to https://github.com/velero-io/velero/issues/3516 +// More background please refer to https://github.com/vmware-tanzu/velero/issues/3516 type AdmissionWebhookConfigurationAction struct { logger logrus.FieldLogger } diff --git a/pkg/restore/actions/admissionwebhook_config_action_test.go b/pkg/restore/actions/admissionwebhook_config_action_test.go index f83e9b8b6..f1257cb9f 100644 --- a/pkg/restore/actions/admissionwebhook_config_action_test.go +++ b/pkg/restore/actions/admissionwebhook_config_action_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestNewAdmissionWebhookConfigurationActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/apiservice_action.go b/pkg/restore/actions/apiservice_action.go index 69b94e8e1..f2433352b 100644 --- a/pkg/restore/actions/apiservice_action.go +++ b/pkg/restore/actions/apiservice_action.go @@ -20,7 +20,7 @@ import ( "github.com/sirupsen/logrus" "k8s.io/kube-aggregator/pkg/controllers/autoregister" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) type APIServiceAction struct { diff --git a/pkg/restore/actions/apiservice_action_test.go b/pkg/restore/actions/apiservice_action_test.go index ef52733b0..9058259c1 100644 --- a/pkg/restore/actions/apiservice_action_test.go +++ b/pkg/restore/actions/apiservice_action_test.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" apiregistrationv1 "k8s.io/kube-aggregator/pkg/apis/apiregistration/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestAPIServiceActionExecuteSkipsRestore(t *testing.T) { diff --git a/pkg/restore/actions/change_image_name_action.go b/pkg/restore/actions/change_image_name_action.go index 356675c04..828da40d6 100644 --- a/pkg/restore/actions/change_image_name_action.go +++ b/pkg/restore/actions/change_image_name_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) const ( diff --git a/pkg/restore/actions/change_image_name_action_test.go b/pkg/restore/actions/change_image_name_action_test.go index d29c1d9c9..530c8453d 100644 --- a/pkg/restore/actions/change_image_name_action_test.go +++ b/pkg/restore/actions/change_image_name_action_test.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // TestChangeImageRepositoryActionExecute runs the ChangeImageNameAction's Execute diff --git a/pkg/restore/actions/change_storageclass_action.go b/pkg/restore/actions/change_storageclass_action.go index bebb236b9..f9f031fe3 100644 --- a/pkg/restore/actions/change_storageclass_action.go +++ b/pkg/restore/actions/change_storageclass_action.go @@ -29,8 +29,8 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" storagev1client "k8s.io/client-go/kubernetes/typed/storage/v1" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // ChangeStorageClassAction updates a PV or PVC's storage class name diff --git a/pkg/restore/actions/change_storageclass_action_test.go b/pkg/restore/actions/change_storageclass_action_test.go index 6e89f8baf..13bbcdcc4 100644 --- a/pkg/restore/actions/change_storageclass_action_test.go +++ b/pkg/restore/actions/change_storageclass_action_test.go @@ -30,8 +30,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // TestChangeStorageClassActionExecute runs the ChangeStorageClassAction's Execute diff --git a/pkg/restore/actions/clusterrolebinding_action.go b/pkg/restore/actions/clusterrolebinding_action.go index 28534ed6f..a11665c1a 100644 --- a/pkg/restore/actions/clusterrolebinding_action.go +++ b/pkg/restore/actions/clusterrolebinding_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // ClusterRoleBindingAction handle namespace remappings for role bindings diff --git a/pkg/restore/actions/clusterrolebinding_action_test.go b/pkg/restore/actions/clusterrolebinding_action_test.go index 8ada6dc93..0829221db 100644 --- a/pkg/restore/actions/clusterrolebinding_action_test.go +++ b/pkg/restore/actions/clusterrolebinding_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestClusterRoleBindingActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go index 8a77af5c5..9e4cf7e2f 100644 --- a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go +++ b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action.go @@ -25,7 +25,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // CRDV1PreserveUnknownFieldsAction will take a CRD and inspect it for the API version and the PreserveUnknownFields value. diff --git a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go index 2c136059d..329cfb433 100644 --- a/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go +++ b/pkg/restore/actions/crd_v1_preserve_unknown_fields_action_test.go @@ -23,13 +23,13 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestExecuteForACRDWithAnIntOnAFloat64FieldShouldWork(t *testing.T) { - // ref. reopen of https://github.com/velero-io/velero/issues/2319 + // ref. reopen of https://github.com/vmware-tanzu/velero/issues/2319 b := builder.ForV1CustomResourceDefinition("test.velero.io") // 5 here is just an int value, it could be any other whole number. diff --git a/pkg/restore/actions/csi/pvc_action.go b/pkg/restore/actions/csi/pvc_action.go index e89a2b0c3..dee23cf70 100644 --- a/pkg/restore/actions/csi/pvc_action.go +++ b/pkg/restore/actions/csi/pvc_action.go @@ -33,17 +33,17 @@ import ( utilrand "k8s.io/apimachinery/pkg/util/rand" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/client" - kuberesource "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/label" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - uploaderUtil "github.com/velero-io/velero/pkg/uploader/util" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/client" + kuberesource "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/label" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + uploaderUtil "github.com/vmware-tanzu/velero/pkg/uploader/util" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) const ( diff --git a/pkg/restore/actions/csi/pvc_action_test.go b/pkg/restore/actions/csi/pvc_action_test.go index ae858b6ff..4da3bec50 100644 --- a/pkg/restore/actions/csi/pvc_action_test.go +++ b/pkg/restore/actions/csi/pvc_action_test.go @@ -36,16 +36,16 @@ import ( "k8s.io/apimachinery/pkg/util/validation" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/apis/velero/shared" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/apis/velero/shared" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) func TestResetPVCSpec(t *testing.T) { diff --git a/pkg/restore/actions/csi/volumesnapshot_action.go b/pkg/restore/actions/csi/volumesnapshot_action.go index 38bed87a2..dec33d4ef 100644 --- a/pkg/restore/actions/csi/volumesnapshot_action.go +++ b/pkg/restore/actions/csi/volumesnapshot_action.go @@ -31,13 +31,13 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/kuberesource" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) // volumeSnapshotRestoreItemAction is a Velero restore item diff --git a/pkg/restore/actions/csi/volumesnapshot_action_test.go b/pkg/restore/actions/csi/volumesnapshot_action_test.go index b7f128255..de3e592c0 100644 --- a/pkg/restore/actions/csi/volumesnapshot_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshot_action_test.go @@ -31,12 +31,12 @@ import ( "k8s.io/apimachinery/pkg/runtime" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util" ) var ( diff --git a/pkg/restore/actions/csi/volumesnapshotclass_action.go b/pkg/restore/actions/csi/volumesnapshotclass_action.go index 911e97430..c906a04b2 100644 --- a/pkg/restore/actions/csi/volumesnapshotclass_action.go +++ b/pkg/restore/actions/csi/volumesnapshotclass_action.go @@ -23,10 +23,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/schema" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" ) // volumeSnapshotClassRestoreItemAction is a Velero restore diff --git a/pkg/restore/actions/csi/volumesnapshotclass_action_test.go b/pkg/restore/actions/csi/volumesnapshotclass_action_test.go index 5ad757452..73d86a109 100644 --- a/pkg/restore/actions/csi/volumesnapshotclass_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshotclass_action_test.go @@ -25,12 +25,12 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" - //"github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + //"github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func TestVSClassExecute(t *testing.T) { diff --git a/pkg/restore/actions/csi/volumesnapshotcontent_action.go b/pkg/restore/actions/csi/volumesnapshotcontent_action.go index d13adc994..00a25c86f 100644 --- a/pkg/restore/actions/csi/volumesnapshotcontent_action.go +++ b/pkg/restore/actions/csi/volumesnapshotcontent_action.go @@ -27,13 +27,13 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/client" - plugincommon "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/csi" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/client" + plugincommon "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/csi" ) // volumeSnapshotContentRestoreItemAction is a restore item action diff --git a/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go b/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go index 5b9b75b57..83b79bd5b 100644 --- a/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go +++ b/pkg/restore/actions/csi/volumesnapshotcontent_action_test.go @@ -26,13 +26,13 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - factorymocks "github.com/velero-io/velero/pkg/client/mocks" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + factorymocks "github.com/vmware-tanzu/velero/pkg/client/mocks" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util" ) func TestVSCExecute(t *testing.T) { diff --git a/pkg/restore/actions/dataupload_retrieve_action.go b/pkg/restore/actions/dataupload_retrieve_action.go index e72fda8ba..a7efdc5f7 100644 --- a/pkg/restore/actions/dataupload_retrieve_action.go +++ b/pkg/restore/actions/dataupload_retrieve_action.go @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/types" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - veleroclient "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + veleroclient "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) type DataUploadRetrieveAction struct { diff --git a/pkg/restore/actions/dataupload_retrieve_action_test.go b/pkg/restore/actions/dataupload_retrieve_action_test.go index 572d3ff1c..64be241bf 100644 --- a/pkg/restore/actions/dataupload_retrieve_action_test.go +++ b/pkg/restore/actions/dataupload_retrieve_action_test.go @@ -27,12 +27,12 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1 "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestDataUploadRetrieveActionExectue(t *testing.T) { diff --git a/pkg/restore/actions/init_restorehook_pod_action.go b/pkg/restore/actions/init_restorehook_pod_action.go index c147860ee..7614ef085 100644 --- a/pkg/restore/actions/init_restorehook_pod_action.go +++ b/pkg/restore/actions/init_restorehook_pod_action.go @@ -21,9 +21,9 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // InitRestoreHookPodAction is a RestoreItemAction plugin applicable to pods that runs diff --git a/pkg/restore/actions/init_restorehook_pod_action_test.go b/pkg/restore/actions/init_restorehook_pod_action_test.go index 66d307d3c..52da2011b 100644 --- a/pkg/restore/actions/init_restorehook_pod_action_test.go +++ b/pkg/restore/actions/init_restorehook_pod_action_test.go @@ -26,11 +26,11 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestInitContainerRestoreHookPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/job_action.go b/pkg/restore/actions/job_action.go index d0a8cdde9..1eabc208c 100644 --- a/pkg/restore/actions/job_action.go +++ b/pkg/restore/actions/job_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) const ( diff --git a/pkg/restore/actions/job_action_test.go b/pkg/restore/actions/job_action_test.go index a78ecd8a6..e3578bb60 100644 --- a/pkg/restore/actions/job_action_test.go +++ b/pkg/restore/actions/job_action_test.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestJobActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/pod_action.go b/pkg/restore/actions/pod_action.go index 3dfa33857..a9db3ed7e 100644 --- a/pkg/restore/actions/pod_action.go +++ b/pkg/restore/actions/pod_action.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) type PodAction struct { diff --git a/pkg/restore/actions/pod_action_test.go b/pkg/restore/actions/pod_action_test.go index 418346ff7..dae455a5b 100644 --- a/pkg/restore/actions/pod_action_test.go +++ b/pkg/restore/actions/pod_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestPodActionExecute(t *testing.T) { diff --git a/pkg/restore/actions/pod_volume_restore_action.go b/pkg/restore/actions/pod_volume_restore_action.go index 831ca390a..e26a53034 100644 --- a/pkg/restore/actions/pod_volume_restore_action.go +++ b/pkg/restore/actions/pod_volume_restore_action.go @@ -21,7 +21,7 @@ import ( "fmt" "strings" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -33,16 +33,16 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" ctrlclient "sigs.k8s.io/controller-runtime/pkg/client" - veleroimage "github.com/velero-io/velero/internal/velero" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/framework/common" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/restorehelper" - "github.com/velero-io/velero/pkg/util/kube" - veleroutil "github.com/velero-io/velero/pkg/util/velero" + veleroimage "github.com/vmware-tanzu/velero/internal/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/framework/common" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/restorehelper" + "github.com/vmware-tanzu/velero/pkg/util/kube" + veleroutil "github.com/vmware-tanzu/velero/pkg/util/velero" ) const ( diff --git a/pkg/restore/actions/pod_volume_restore_action_test.go b/pkg/restore/actions/pod_volume_restore_action_test.go index 8faa80f43..bc9662ab7 100644 --- a/pkg/restore/actions/pod_volume_restore_action_test.go +++ b/pkg/restore/actions/pod_volume_restore_action_test.go @@ -20,7 +20,7 @@ import ( "sort" "testing" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" "github.com/sirupsen/logrus" "github.com/stretchr/testify/assert" @@ -33,16 +33,16 @@ import ( "k8s.io/client-go/kubernetes/fake" crfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/buildinfo" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/kube" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/kube" "k8s.io/client-go/kubernetes/scheme" - "github.com/velero-io/velero/pkg/restorehelper" + "github.com/vmware-tanzu/velero/pkg/restorehelper" ) func TestGetImage(t *testing.T) { diff --git a/pkg/restore/actions/pvc_action.go b/pkg/restore/actions/pvc_action.go index 4ecfa9ead..a4a63374d 100644 --- a/pkg/restore/actions/pvc_action.go +++ b/pkg/restore/actions/pvc_action.go @@ -24,10 +24,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util" ) const ( diff --git a/pkg/restore/actions/pvc_action_test.go b/pkg/restore/actions/pvc_action_test.go index d143342c3..aa2ddeeef 100644 --- a/pkg/restore/actions/pvc_action_test.go +++ b/pkg/restore/actions/pvc_action_test.go @@ -28,10 +28,10 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/client-go/kubernetes/fake" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) // TestPVCActionExecute runs the PVCAction's Execute diff --git a/pkg/restore/actions/rolebinding_action.go b/pkg/restore/actions/rolebinding_action.go index 92f712a48..05e463587 100644 --- a/pkg/restore/actions/rolebinding_action.go +++ b/pkg/restore/actions/rolebinding_action.go @@ -23,7 +23,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) // RoleBindingAction handle namespace remappings for role bindings diff --git a/pkg/restore/actions/rolebinding_action_test.go b/pkg/restore/actions/rolebinding_action_test.go index bf29cf0cd..f2867e8a5 100644 --- a/pkg/restore/actions/rolebinding_action_test.go +++ b/pkg/restore/actions/rolebinding_action_test.go @@ -26,9 +26,9 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestRoleBindingActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/secret_action.go b/pkg/restore/actions/secret_action.go index e339018a9..2ec9fb4ff 100644 --- a/pkg/restore/actions/secret_action.go +++ b/pkg/restore/actions/secret_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) // SecretAction is a restore item action for secrets diff --git a/pkg/restore/actions/secret_action_test.go b/pkg/restore/actions/secret_action_test.go index 92c4349a2..575b7634e 100644 --- a/pkg/restore/actions/secret_action_test.go +++ b/pkg/restore/actions/secret_action_test.go @@ -28,8 +28,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestSecretActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/service_account_action.go b/pkg/restore/actions/service_account_action.go index 52e3c3095..429c21949 100644 --- a/pkg/restore/actions/service_account_action.go +++ b/pkg/restore/actions/service_account_action.go @@ -25,8 +25,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type ServiceAccountAction struct { diff --git a/pkg/restore/actions/service_account_action_test.go b/pkg/restore/actions/service_account_action_test.go index a6cc389f7..6a2f74ead 100644 --- a/pkg/restore/actions/service_account_action_test.go +++ b/pkg/restore/actions/service_account_action_test.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestServiceAccountActionAppliesTo(t *testing.T) { diff --git a/pkg/restore/actions/service_action.go b/pkg/restore/actions/service_action.go index 9db2ae600..47147a31f 100644 --- a/pkg/restore/actions/service_action.go +++ b/pkg/restore/actions/service_action.go @@ -28,8 +28,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/util/sets" - "github.com/velero-io/velero/pkg/plugin/velero" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) const annotationLastAppliedConfig = "kubectl.kubernetes.io/last-applied-configuration" diff --git a/pkg/restore/actions/service_action_test.go b/pkg/restore/actions/service_action_test.go index a94675c3b..f9a01d5d4 100644 --- a/pkg/restore/actions/service_action_test.go +++ b/pkg/restore/actions/service_action_test.go @@ -27,10 +27,10 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" "k8s.io/apimachinery/pkg/runtime" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/plugin/velero" - velerotest "github.com/velero-io/velero/pkg/test" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func svcJSON(ports ...corev1api.ServicePort) string { diff --git a/pkg/restore/merge_service_account_test.go b/pkg/restore/merge_service_account_test.go index 13e77bddd..4322ae003 100644 --- a/pkg/restore/merge_service_account_test.go +++ b/pkg/restore/merge_service_account_test.go @@ -25,7 +25,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) var mergedServiceAccountsBenchmarkResult *unstructured.Unstructured diff --git a/pkg/restore/prioritize_group_version.go b/pkg/restore/prioritize_group_version.go index cd52d1cfc..5d7ab15d5 100644 --- a/pkg/restore/prioritize_group_version.go +++ b/pkg/restore/prioritize_group_version.go @@ -27,9 +27,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/version" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" - "github.com/velero-io/velero/pkg/client" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" + "github.com/vmware-tanzu/velero/pkg/client" ) // ChosenGroupVersion is the API Group version that was selected to restore diff --git a/pkg/restore/prioritize_group_version_test.go b/pkg/restore/prioritize_group_version_test.go index fa6300162..e87fb13ba 100644 --- a/pkg/restore/prioritize_group_version_test.go +++ b/pkg/restore/prioritize_group_version_test.go @@ -23,8 +23,8 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestK8sPrioritySort(t *testing.T) { diff --git a/pkg/restore/pv_restorer.go b/pkg/restore/pv_restorer.go index 6f4a7bcb7..53fbd0126 100644 --- a/pkg/restore/pv_restorer.go +++ b/pkg/restore/pv_restorer.go @@ -25,10 +25,10 @@ import ( "k8s.io/apimachinery/pkg/types" "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/volume" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/volume" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) type PVRestorer interface { diff --git a/pkg/restore/pv_restorer_test.go b/pkg/restore/pv_restorer_test.go index b7a956fbb..09c6dd0ad 100644 --- a/pkg/restore/pv_restorer_test.go +++ b/pkg/restore/pv_restorer_test.go @@ -27,12 +27,12 @@ import ( "github.com/stretchr/testify/require" "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - "github.com/velero-io/velero/internal/volume" - api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - providermocks "github.com/velero-io/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/internal/volume" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + providermocks "github.com/vmware-tanzu/velero/pkg/plugin/velero/mocks/volumesnapshotter/v1" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func defaultBackup() *builder.BackupBuilder { diff --git a/pkg/restore/request.go b/pkg/restore/request.go index e451f61c0..239d65df9 100644 --- a/pkg/restore/request.go +++ b/pkg/restore/request.go @@ -25,11 +25,11 @@ import ( "github.com/sirupsen/logrus" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/internal/resourcemodifiers" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/internal/resourcemodifiers" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) const ( diff --git a/pkg/restore/restore.go b/pkg/restore/restore.go index 378633f20..5287eec21 100644 --- a/pkg/restore/restore.go +++ b/pkg/restore/restore.go @@ -52,33 +52,33 @@ import ( "k8s.io/client-go/util/retry" crclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/hook" - "github.com/velero-io/velero/internal/resourcemodifiers" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/plugin/framework" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podexec" - "github.com/velero-io/velero/pkg/podvolume" - "github.com/velero-io/velero/pkg/podvolume/configs" - "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" - csiutil "github.com/velero-io/velero/pkg/util/csi" - "github.com/velero-io/velero/pkg/util/filesystem" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/pkg/util/results" - "github.com/velero-io/velero/pkg/util/wildcard" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/hook" + "github.com/vmware-tanzu/velero/internal/resourcemodifiers" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/plugin/framework" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podexec" + "github.com/vmware-tanzu/velero/pkg/podvolume" + "github.com/vmware-tanzu/velero/pkg/podvolume/configs" + "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" + csiutil "github.com/vmware-tanzu/velero/pkg/util/csi" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/pkg/util/wildcard" ) const ObjectStatusRestoreAnnotationKey = "velero.io/restore-status" @@ -1789,7 +1789,7 @@ func isAlreadyExistsError(ctx *restoreContext, obj *unstructured.Unstructured, e // 1. For NodePort service, the service has nodePort preservation while the same nodePort service already exists. - Get invalid value error // 2. For LoadBalancer service, the "healthCheckNodePort" already exists. - Get internal error // If this is the case, the function returns true to avoid reporting error. - // Refer to https://github.com/velero-io/velero/issues/2308 for more details + // Refer to https://github.com/vmware-tanzu/velero/issues/2308 for more details if obj.GetKind() != "Service" { return false, nil } diff --git a/pkg/restore/restore_test.go b/pkg/restore/restore_test.go index 9efd2eef1..95b283cbe 100644 --- a/pkg/restore/restore_test.go +++ b/pkg/restore/restore_test.go @@ -25,8 +25,8 @@ import ( "testing" "time" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/collections" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/collections" snapshotv1api "github.com/kubernetes-csi/external-snapshotter/client/v8/apis/volumesnapshot/v1" "github.com/pkg/errors" @@ -45,25 +45,25 @@ import ( "k8s.io/client-go/dynamic" kubetesting "k8s.io/client-go/testing" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/client" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/features" - "github.com/velero-io/velero/pkg/itemoperation" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" - riav2 "github.com/velero-io/velero/pkg/plugin/velero/restoreitemaction/v2" - vsv1 "github.com/velero-io/velero/pkg/plugin/velero/volumesnapshotter/v1" - "github.com/velero-io/velero/pkg/podvolume" - uploadermocks "github.com/velero-io/velero/pkg/podvolume/mocks" - "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/kube" - kubeutil "github.com/velero-io/velero/pkg/util/kube" - . "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/itemoperation" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" + riav2 "github.com/vmware-tanzu/velero/pkg/plugin/velero/restoreitemaction/v2" + vsv1 "github.com/vmware-tanzu/velero/pkg/plugin/velero/volumesnapshotter/v1" + "github.com/vmware-tanzu/velero/pkg/podvolume" + uploadermocks "github.com/vmware-tanzu/velero/pkg/podvolume/mocks" + "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/kube" + kubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + . "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestRestorePVWithVolumeInfo(t *testing.T) { diff --git a/pkg/restore/restore_wildcard_test.go b/pkg/restore/restore_wildcard_test.go index 257eec785..c38ad7dd9 100644 --- a/pkg/restore/restore_wildcard_test.go +++ b/pkg/restore/restore_wildcard_test.go @@ -23,8 +23,8 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/archive" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/archive" ) func TestExpandNamespaceWildcards(t *testing.T) { diff --git a/pkg/test/fake_controller_runtime_client.go b/pkg/test/fake_controller_runtime_client.go index 383c7d0b8..90ee95d11 100644 --- a/pkg/test/fake_controller_runtime_client.go +++ b/pkg/test/fake_controller_runtime_client.go @@ -31,8 +31,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" k8sfake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) func NewFakeControllerRuntimeClientBuilder(t *testing.T) *k8sfake.ClientBuilder { diff --git a/pkg/test/fake_dynamic.go b/pkg/test/fake_dynamic.go index ee5021801..996e8cfd1 100644 --- a/pkg/test/fake_dynamic.go +++ b/pkg/test/fake_dynamic.go @@ -24,7 +24,7 @@ import ( "k8s.io/apimachinery/pkg/watch" "k8s.io/client-go/dynamic/dynamicinformer" - "github.com/velero-io/velero/pkg/client" + "github.com/vmware-tanzu/velero/pkg/client" ) type FakeDynamicFactory struct { diff --git a/pkg/test/fake_file_system.go b/pkg/test/fake_file_system.go index 2beae0644..7a744647b 100644 --- a/pkg/test/fake_file_system.go +++ b/pkg/test/fake_file_system.go @@ -23,7 +23,7 @@ import ( "github.com/spf13/afero" - "github.com/velero-io/velero/pkg/util/filesystem" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) type FakeFileSystem struct { diff --git a/pkg/test/mock_pod_command_executor.go b/pkg/test/mock_pod_command_executor.go index ff4019a77..b8ace0c6e 100644 --- a/pkg/test/mock_pod_command_executor.go +++ b/pkg/test/mock_pod_command_executor.go @@ -22,7 +22,7 @@ import ( "github.com/sirupsen/logrus" "github.com/stretchr/testify/mock" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) type MockPodCommandExecutor struct { diff --git a/pkg/test/tar_writer.go b/pkg/test/tar_writer.go index a51079655..20706766c 100644 --- a/pkg/test/tar_writer.go +++ b/pkg/test/tar_writer.go @@ -29,7 +29,7 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/util/encode" + "github.com/vmware-tanzu/velero/pkg/util/encode" ) type TarWriter struct { diff --git a/pkg/types/node_agent.go b/pkg/types/node_agent.go index b7743bac2..f456bbf55 100644 --- a/pkg/types/node_agent.go +++ b/pkg/types/node_agent.go @@ -19,7 +19,7 @@ package types import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/pkg/util/kube" ) type LoadConcurrency struct { diff --git a/pkg/types/repo_maintenance.go b/pkg/types/repo_maintenance.go index ae3b1d484..a5115ff92 100644 --- a/pkg/types/repo_maintenance.go +++ b/pkg/types/repo_maintenance.go @@ -16,7 +16,7 @@ limitations under the License. package types -import "github.com/velero-io/velero/pkg/util/kube" +import "github.com/vmware-tanzu/velero/pkg/util/kube" type JobConfigs struct { // LoadAffinities is the config for repository maintenance job load affinity. diff --git a/pkg/uploader/cbt/bitmap.go b/pkg/uploader/cbt/bitmap.go index 731096cfd..f26cb22b7 100644 --- a/pkg/uploader/cbt/bitmap.go +++ b/pkg/uploader/cbt/bitmap.go @@ -21,7 +21,7 @@ import ( "github.com/RoaringBitmap/roaring" - "github.com/velero-io/velero/pkg/uploader/cbt/types" + "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" ) const ( diff --git a/pkg/uploader/cbt/set.go b/pkg/uploader/cbt/set.go index 3c82eff74..5919419e6 100644 --- a/pkg/uploader/cbt/set.go +++ b/pkg/uploader/cbt/set.go @@ -21,8 +21,8 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/cbtservice" - "github.com/velero-io/velero/pkg/uploader/cbt/types" + "github.com/vmware-tanzu/velero/pkg/cbtservice" + "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" ) // SetBitmapOrFull translates the allocated/changed blocks from CBT service to the given bitmap or set the bitmap to full when error happens diff --git a/pkg/uploader/cbt/set_test.go b/pkg/uploader/cbt/set_test.go index 93bd93171..55701dedd 100644 --- a/pkg/uploader/cbt/set_test.go +++ b/pkg/uploader/cbt/set_test.go @@ -24,9 +24,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/cbtservice" - cbtservicemocks "github.com/velero-io/velero/pkg/cbtservice/mocks" - cbtmocks "github.com/velero-io/velero/pkg/uploader/cbt/types/mocks" + "github.com/vmware-tanzu/velero/pkg/cbtservice" + cbtservicemocks "github.com/vmware-tanzu/velero/pkg/cbtservice/mocks" + cbtmocks "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types/mocks" ) func TestSetBitmapOrFull(t *testing.T) { diff --git a/pkg/uploader/cbt/types/mocks/Bitmap.go b/pkg/uploader/cbt/types/mocks/Bitmap.go index b382e995e..faa4ee242 100644 --- a/pkg/uploader/cbt/types/mocks/Bitmap.go +++ b/pkg/uploader/cbt/types/mocks/Bitmap.go @@ -6,7 +6,7 @@ package mocks import ( mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/uploader/cbt/types" + "github.com/vmware-tanzu/velero/pkg/uploader/cbt/types" ) // NewBitmap creates a new instance of Bitmap. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/uploader/kopia/progress.go b/pkg/uploader/kopia/progress.go index 62a98efce..5071398d0 100644 --- a/pkg/uploader/kopia/progress.go +++ b/pkg/uploader/kopia/progress.go @@ -22,7 +22,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader" "github.com/kopia/kopia/snapshot/upload" ) diff --git a/pkg/uploader/kopia/progress_test.go b/pkg/uploader/kopia/progress_test.go index 8b811f854..8c18bb85b 100644 --- a/pkg/uploader/kopia/progress_test.go +++ b/pkg/uploader/kopia/progress_test.go @@ -23,7 +23,7 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader" ) type fakeProgressUpdater struct{} diff --git a/pkg/uploader/kopia/shim.go b/pkg/uploader/kopia/shim.go index d6c888e11..f146348fa 100644 --- a/pkg/uploader/kopia/shim.go +++ b/pkg/uploader/kopia/shim.go @@ -23,7 +23,7 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" "github.com/kopia/kopia/repo" "github.com/kopia/kopia/repo/content" diff --git a/pkg/uploader/kopia/shim_test.go b/pkg/uploader/kopia/shim_test.go index cbeada746..7933ec6b8 100644 --- a/pkg/uploader/kopia/shim_test.go +++ b/pkg/uploader/kopia/shim_test.go @@ -30,8 +30,8 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" ) func TestShimRepo(t *testing.T) { diff --git a/pkg/uploader/kopia/snapshot.go b/pkg/uploader/kopia/snapshot.go index 3549fe45d..1924ed35b 100644 --- a/pkg/uploader/kopia/snapshot.go +++ b/pkg/uploader/kopia/snapshot.go @@ -38,10 +38,10 @@ import ( "github.com/kopia/kopia/snapshot/snapshotfs" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/kopia" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/uploader" - uploaderutil "github.com/velero-io/velero/pkg/uploader/util" + "github.com/vmware-tanzu/velero/pkg/kopia" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/uploader" + uploaderutil "github.com/vmware-tanzu/velero/pkg/uploader/util" ) // All function mainly used to make testing more convenient diff --git a/pkg/uploader/kopia/snapshot_test.go b/pkg/uploader/kopia/snapshot_test.go index 9944ec06c..984b92af5 100644 --- a/pkg/uploader/kopia/snapshot_test.go +++ b/pkg/uploader/kopia/snapshot_test.go @@ -36,9 +36,9 @@ import ( "github.com/stretchr/testify/mock" "github.com/stretchr/testify/require" - repomocks "github.com/velero-io/velero/pkg/repository/mocks" - "github.com/velero-io/velero/pkg/uploader" - uploadermocks "github.com/velero-io/velero/pkg/uploader/mocks" + repomocks "github.com/vmware-tanzu/velero/pkg/repository/mocks" + "github.com/vmware-tanzu/velero/pkg/uploader" + uploadermocks "github.com/vmware-tanzu/velero/pkg/uploader/mocks" ) type snapshotMockes struct { diff --git a/pkg/uploader/provider/block.go b/pkg/uploader/provider/block.go index 1b42e5391..b1eed428a 100644 --- a/pkg/uploader/provider/block.go +++ b/pkg/uploader/provider/block.go @@ -23,11 +23,11 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - repokeys "github.com/velero-io/velero/pkg/repository/keys" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + repokeys "github.com/vmware-tanzu/velero/pkg/repository/keys" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/uploader" ) type blockProvider struct { diff --git a/pkg/uploader/provider/block_test.go b/pkg/uploader/provider/block_test.go index f6834c82c..a48b0a862 100644 --- a/pkg/uploader/provider/block_test.go +++ b/pkg/uploader/provider/block_test.go @@ -26,12 +26,12 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/credentials/mocks" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" - "github.com/velero-io/velero/pkg/repository/udmrepo" - udmrepomocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/credentials/mocks" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + udmrepomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" ) func TestNewBlockUploaderProvider(t *testing.T) { diff --git a/pkg/uploader/provider/kopia.go b/pkg/uploader/provider/kopia.go index 684a6d12f..620b0776d 100644 --- a/pkg/uploader/provider/kopia.go +++ b/pkg/uploader/provider/kopia.go @@ -26,14 +26,14 @@ import ( "github.com/pkg/errors" "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/uploader/kopia" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader/kopia" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - repokeys "github.com/velero-io/velero/pkg/repository/keys" - "github.com/velero-io/velero/pkg/repository/udmrepo" - "github.com/velero-io/velero/pkg/repository/udmrepo/service" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + repokeys "github.com/vmware-tanzu/velero/pkg/repository/keys" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/service" ) var kopiaBackupFunc = kopia.Backup diff --git a/pkg/uploader/provider/kopia_test.go b/pkg/uploader/provider/kopia_test.go index eb1e0ab21..092333a24 100644 --- a/pkg/uploader/provider/kopia_test.go +++ b/pkg/uploader/provider/kopia_test.go @@ -33,15 +33,15 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/credentials/mocks" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/repository" - udmrepo "github.com/velero-io/velero/pkg/repository/udmrepo" - udmrepomocks "github.com/velero-io/velero/pkg/repository/udmrepo/mocks" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/uploader/kopia" - "github.com/velero-io/velero/pkg/util" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/credentials/mocks" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/repository" + udmrepo "github.com/vmware-tanzu/velero/pkg/repository/udmrepo" + udmrepomocks "github.com/vmware-tanzu/velero/pkg/repository/udmrepo/mocks" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader/kopia" + "github.com/vmware-tanzu/velero/pkg/util" ) type FakeBackupProgressUpdater struct { diff --git a/pkg/uploader/provider/mocks/Provider.go b/pkg/uploader/provider/mocks/Provider.go index d84850129..71e60b84e 100644 --- a/pkg/uploader/provider/mocks/Provider.go +++ b/pkg/uploader/provider/mocks/Provider.go @@ -8,8 +8,8 @@ import ( "context" mock "github.com/stretchr/testify/mock" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/uploader/provider" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/uploader/provider" ) // NewProvider creates a new instance of Provider. It also registers a testing interface on the mock and a cleanup function to assert the mocks expectations. diff --git a/pkg/uploader/provider/provider.go b/pkg/uploader/provider/provider.go index 146f89e91..0c1caaffe 100644 --- a/pkg/uploader/provider/provider.go +++ b/pkg/uploader/provider/provider.go @@ -27,10 +27,10 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/credentials" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cbtservice" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/internal/credentials" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cbtservice" + "github.com/vmware-tanzu/velero/pkg/uploader" ) const restoreProgressCheckInterval = 10 * time.Second diff --git a/pkg/uploader/provider/provider_test.go b/pkg/uploader/provider/provider_test.go index 91a35c274..8f447725b 100644 --- a/pkg/uploader/provider/provider_test.go +++ b/pkg/uploader/provider/provider_test.go @@ -25,10 +25,10 @@ import ( corev1api "k8s.io/api/core/v1" "sigs.k8s.io/controller-runtime/pkg/client/fake" - "github.com/velero-io/velero/internal/credentials" - "github.com/velero-io/velero/internal/credentials/mocks" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util" + "github.com/vmware-tanzu/velero/internal/credentials" + "github.com/vmware-tanzu/velero/internal/credentials/mocks" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util" ) type NewUploaderProviderTestCase struct { diff --git a/pkg/uploader/util/uploader_config.go b/pkg/uploader/util/uploader_config.go index 51499129e..5584ffbce 100644 --- a/pkg/uploader/util/uploader_config.go +++ b/pkg/uploader/util/uploader_config.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) const ( diff --git a/pkg/uploader/util/uploader_config_test.go b/pkg/uploader/util/uploader_config_test.go index f03538116..593bce4f0 100644 --- a/pkg/uploader/util/uploader_config_test.go +++ b/pkg/uploader/util/uploader_config_test.go @@ -22,7 +22,7 @@ import ( "github.com/pkg/errors" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestStoreBackupConfig(t *testing.T) { diff --git a/pkg/util/actionhelpers/pod_helper.go b/pkg/util/actionhelpers/pod_helper.go index 6d9514bdc..72c42936c 100644 --- a/pkg/util/actionhelpers/pod_helper.go +++ b/pkg/util/actionhelpers/pod_helper.go @@ -20,8 +20,8 @@ import ( "github.com/sirupsen/logrus" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func RelatedItemsForPod(pod *corev1api.Pod, log logrus.FieldLogger) []velero.ResourceIdentifier { diff --git a/pkg/util/actionhelpers/pvc_helper.go b/pkg/util/actionhelpers/pvc_helper.go index e496d5a1e..f6a72eeaa 100644 --- a/pkg/util/actionhelpers/pvc_helper.go +++ b/pkg/util/actionhelpers/pvc_helper.go @@ -20,8 +20,8 @@ import ( "github.com/sirupsen/logrus" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func RelatedItemsForPVC(pvc *corev1api.PersistentVolumeClaim, log logrus.FieldLogger) []velero.ResourceIdentifier { diff --git a/pkg/util/actionhelpers/service_account_helper.go b/pkg/util/actionhelpers/service_account_helper.go index 7f529f121..0474e1a9b 100644 --- a/pkg/util/actionhelpers/service_account_helper.go +++ b/pkg/util/actionhelpers/service_account_helper.go @@ -22,9 +22,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/util/sets" - velerodiscovery "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/plugin/velero" + velerodiscovery "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/plugin/velero" ) func ClusterRoleBindingsForAction(clusterRoleBindingListers map[string]ClusterRoleBindingLister, discoveryHelper velerodiscovery.Helper) ([]ClusterRoleBinding, error) { diff --git a/pkg/util/azure/storage.go b/pkg/util/azure/storage.go index c5ba18c3a..49943a3f9 100644 --- a/pkg/util/azure/storage.go +++ b/pkg/util/azure/storage.go @@ -33,7 +33,7 @@ import ( const ( // the keys of Azure BSL config: - // https://github.com/velero-io/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md + // https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/backupstoragelocation.md BSLConfigResourceGroup = "resourceGroup" BSLConfigStorageAccount = "storageAccount" BSLConfigStorageAccountAccessKeyName = "storageAccountKeyEnvVar" @@ -162,7 +162,7 @@ func GetStorageAccountCredentials(bslCfg map[string]string, creds map[string]str // getStorageAccountURI returns the storage account URI by the following order: // 1. Return the storage account URI directly if it is specified in BSL config -// 2. Try to call Azure API to get the storage account URI if possible(Background: https://github.com/velero-io/velero/issues/6163) +// 2. Try to call Azure API to get the storage account URI if possible(Background: https://github.com/vmware-tanzu/velero/issues/6163) // 3. Fall back to return the default URI func getStorageAccountURI(log logrus.FieldLogger, bslCfg map[string]string, creds map[string]string) (string, error) { // if the URI is specified in the BSL, return it directly diff --git a/pkg/util/collections/includes_excludes.go b/pkg/util/collections/includes_excludes.go index d5efd6c15..f326a4124 100644 --- a/pkg/util/collections/includes_excludes.go +++ b/pkg/util/collections/includes_excludes.go @@ -19,7 +19,7 @@ package collections import ( "strings" - "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" "github.com/gobwas/glob" "github.com/pkg/errors" @@ -28,11 +28,11 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/discovery" - "github.com/velero-io/velero/pkg/kuberesource" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/wildcard" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/discovery" + "github.com/vmware-tanzu/velero/pkg/kuberesource" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/wildcard" ) type globStringSet struct { @@ -274,7 +274,7 @@ func GetResourceIncludesExcludes(helper discovery.Helper, includes, excludes []s if err != nil { // If we can't resolve it, return it as-is. This prevents the generated // includes-excludes list from including *everything*, if none of the includes - // can be resolved. ref. https://github.com/velero-io/velero/issues/2461 + // can be resolved. ref. https://github.com/vmware-tanzu/velero/issues/2461 return item } diff --git a/pkg/util/collections/includes_excludes_test.go b/pkg/util/collections/includes_excludes_test.go index 7b260e4b5..1d700a729 100644 --- a/pkg/util/collections/includes_excludes_test.go +++ b/pkg/util/collections/includes_excludes_test.go @@ -19,7 +19,7 @@ package collections import ( "testing" - "github.com/velero-io/velero/internal/resourcepolicies" + "github.com/vmware-tanzu/velero/internal/resourcepolicies" "github.com/pkg/errors" "github.com/sirupsen/logrus" @@ -29,9 +29,9 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/apimachinery/pkg/util/sets" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/test" ) func TestShouldInclude(t *testing.T) { diff --git a/pkg/util/csi/util.go b/pkg/util/csi/util.go index d1b151a1e..bcc424d1b 100644 --- a/pkg/util/csi/util.go +++ b/pkg/util/csi/util.go @@ -19,8 +19,8 @@ package csi import ( "strings" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/features" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/features" ) const ( diff --git a/pkg/util/csi/util_test.go b/pkg/util/csi/util_test.go index e2f548189..8a3ea3cc1 100644 --- a/pkg/util/csi/util_test.go +++ b/pkg/util/csi/util_test.go @@ -21,7 +21,7 @@ import ( "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/features" + "github.com/vmware-tanzu/velero/pkg/features" ) func TestCSIFeatureNotEnabledAndPluginIsFromCSI(t *testing.T) { diff --git a/pkg/util/csi/volume_snapshot.go b/pkg/util/csi/volume_snapshot.go index 5fbc1e7fb..ed6371f7b 100644 --- a/pkg/util/csi/volume_snapshot.go +++ b/pkg/util/csi/volume_snapshot.go @@ -36,10 +36,10 @@ import ( "k8s.io/apimachinery/pkg/util/wait" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/stringptr" - "github.com/velero-io/velero/pkg/util/stringslice" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/stringptr" + "github.com/vmware-tanzu/velero/pkg/util/stringslice" ) const ( diff --git a/pkg/util/csi/volume_snapshot_test.go b/pkg/util/csi/volume_snapshot_test.go index f00a09480..67a07d135 100644 --- a/pkg/util/csi/volume_snapshot_test.go +++ b/pkg/util/csi/volume_snapshot_test.go @@ -36,13 +36,13 @@ import ( clientTesting "k8s.io/client-go/testing" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/test" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/util/boolptr" - "github.com/velero-io/velero/pkg/util/logging" - "github.com/velero-io/velero/pkg/util/stringptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/logging" + "github.com/vmware-tanzu/velero/pkg/util/stringptr" ) type reactor struct { diff --git a/pkg/util/encode/encode.go b/pkg/util/encode/encode.go index 1f783f823..b7cbdc1c7 100644 --- a/pkg/util/encode/encode.go +++ b/pkg/util/encode/encode.go @@ -27,8 +27,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" "k8s.io/apimachinery/pkg/runtime/serializer" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util" ) // Encode converts the provided object to the specified format diff --git a/pkg/util/kube/client.go b/pkg/util/kube/client.go index fc2f1eff1..801f7ab33 100644 --- a/pkg/util/kube/client.go +++ b/pkg/util/kube/client.go @@ -22,7 +22,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" - veleroPkgClient "github.com/velero-io/velero/pkg/client" + veleroPkgClient "github.com/vmware-tanzu/velero/pkg/client" ) func PatchResource(original, updated client.Object, kbClient client.Client) error { diff --git a/pkg/util/kube/event_test.go b/pkg/util/kube/event_test.go index 76969a12f..645d1da2d 100644 --- a/pkg/util/kube/event_test.go +++ b/pkg/util/kube/event_test.go @@ -30,7 +30,7 @@ import ( corev1api "k8s.io/api/core/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestEvent(t *testing.T) { diff --git a/pkg/util/kube/list_watch_test.go b/pkg/util/kube/list_watch_test.go index 64521b6df..a0ed9760e 100644 --- a/pkg/util/kube/list_watch_test.go +++ b/pkg/util/kube/list_watch_test.go @@ -24,8 +24,8 @@ import ( "k8s.io/client-go/tools/cache" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestInternalLW(t *testing.T) { diff --git a/pkg/util/kube/node_test.go b/pkg/util/kube/node_test.go index c9a929891..9f14c380b 100644 --- a/pkg/util/kube/node_test.go +++ b/pkg/util/kube/node_test.go @@ -24,13 +24,13 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/runtime" - "github.com/velero-io/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/builder" kubeClientFake "k8s.io/client-go/kubernetes/fake" clientTesting "k8s.io/client-go/testing" clientFake "sigs.k8s.io/controller-runtime/pkg/client/fake" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestIsLinuxNode(t *testing.T) { diff --git a/pkg/util/kube/periodical_enqueue_source_test.go b/pkg/util/kube/periodical_enqueue_source_test.go index b4a2e4f9d..b5e97321a 100644 --- a/pkg/util/kube/periodical_enqueue_source_test.go +++ b/pkg/util/kube/periodical_enqueue_source_test.go @@ -33,8 +33,8 @@ import ( "sigs.k8s.io/controller-runtime/pkg/predicate" "sigs.k8s.io/controller-runtime/pkg/reconcile" - "github.com/velero-io/velero/internal/storage" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/internal/storage" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestStart(t *testing.T) { diff --git a/pkg/util/kube/pod_test.go b/pkg/util/kube/pod_test.go index 90301c62c..aa8d4db99 100644 --- a/pkg/util/kube/pod_test.go +++ b/pkg/util/kube/pod_test.go @@ -39,7 +39,7 @@ import ( clientTesting "k8s.io/client-go/testing" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" corev1client "k8s.io/client-go/kubernetes/typed/core/v1" ) diff --git a/pkg/util/kube/predicate_test.go b/pkg/util/kube/predicate_test.go index 2cc956a75..eb00e2fed 100644 --- a/pkg/util/kube/predicate_test.go +++ b/pkg/util/kube/predicate_test.go @@ -26,7 +26,7 @@ import ( "sigs.k8s.io/controller-runtime/pkg/client" "sigs.k8s.io/controller-runtime/pkg/event" - velerov1 "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestSpecChangePredicate(t *testing.T) { diff --git a/pkg/util/kube/priority_class_test.go b/pkg/util/kube/priority_class_test.go index d552f76d1..9d6a52599 100644 --- a/pkg/util/kube/priority_class_test.go +++ b/pkg/util/kube/priority_class_test.go @@ -27,7 +27,7 @@ import ( "k8s.io/client-go/kubernetes/fake" k8stesting "k8s.io/client-go/testing" - velerotesting "github.com/velero-io/velero/pkg/test" + velerotesting "github.com/vmware-tanzu/velero/pkg/test" ) func TestValidatePriorityClass(t *testing.T) { diff --git a/pkg/util/kube/pvc_pv_test.go b/pkg/util/kube/pvc_pv_test.go index 8ba298c52..63b8e1edd 100644 --- a/pkg/util/kube/pvc_pv_test.go +++ b/pkg/util/kube/pvc_pv_test.go @@ -33,8 +33,8 @@ import ( clientTesting "k8s.io/client-go/testing" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) type reactor struct { diff --git a/pkg/util/kube/resource_requirements.go b/pkg/util/kube/resource_requirements.go index 5e385254c..12cf7a79c 100644 --- a/pkg/util/kube/resource_requirements.go +++ b/pkg/util/kube/resource_requirements.go @@ -21,7 +21,7 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/api/resource" - "github.com/velero-io/velero/pkg/constant" + "github.com/vmware-tanzu/velero/pkg/constant" ) // ParseCPUAndMemoryResources is a helper function that parses CPU and memory requests and limits, diff --git a/pkg/util/kube/secrets_test.go b/pkg/util/kube/secrets_test.go index 120a9c457..8707c9be3 100644 --- a/pkg/util/kube/secrets_test.go +++ b/pkg/util/kube/secrets_test.go @@ -22,8 +22,8 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestGetSecretKey(t *testing.T) { diff --git a/pkg/util/kube/security_context_test.go b/pkg/util/kube/security_context_test.go index 4153b37ee..6ba857bc7 100644 --- a/pkg/util/kube/security_context_test.go +++ b/pkg/util/kube/security_context_test.go @@ -23,7 +23,7 @@ import ( "github.com/stretchr/testify/require" corev1api "k8s.io/api/core/v1" - "github.com/velero-io/velero/pkg/util/boolptr" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) func TestParseSecurityContext(t *testing.T) { diff --git a/pkg/util/kube/utils.go b/pkg/util/kube/utils.go index 89c838615..5e5e97603 100644 --- a/pkg/util/kube/utils.go +++ b/pkg/util/kube/utils.go @@ -37,10 +37,10 @@ import ( corev1client "k8s.io/client-go/kubernetes/typed/core/v1" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/label" - "github.com/velero-io/velero/pkg/uploader" - "github.com/velero-io/velero/pkg/util/filesystem" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/label" + "github.com/vmware-tanzu/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/util/filesystem" ) // These annotations are taken from the Kubernetes persistent volume/persistent volume claim controller. @@ -244,7 +244,7 @@ func isProvisionedByCSI(log logrus.FieldLogger, pv *corev1api.PersistentVolume, return true, nil } // Although the pv.Spec.CSI is nil, the volume could be provisioned by a CSI driver when enabling the CSI migration - // Refer to https://github.com/velero-io/velero/issues/4496 for more details + // Refer to https://github.com/vmware-tanzu/velero/issues/4496 for more details if pv.Annotations != nil { driverName := pv.Annotations[KubeAnnDynamicallyProvisioned] migratedDriver := pv.Annotations[KubeAnnMigratedTo] diff --git a/pkg/util/kube/utils_test.go b/pkg/util/kube/utils_test.go index 04de4e0a2..df23903a0 100644 --- a/pkg/util/kube/utils_test.go +++ b/pkg/util/kube/utils_test.go @@ -35,9 +35,9 @@ import ( "k8s.io/apimachinery/pkg/runtime/schema" "k8s.io/client-go/kubernetes/fake" - "github.com/velero-io/velero/pkg/builder" - velerotest "github.com/velero-io/velero/pkg/test" - "github.com/velero-io/velero/pkg/uploader" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotest "github.com/vmware-tanzu/velero/pkg/test" + "github.com/vmware-tanzu/velero/pkg/uploader" ) func TestNamespaceAndName(t *testing.T) { diff --git a/pkg/util/logging/dual_mode_logger_test.go b/pkg/util/logging/dual_mode_logger_test.go index c96ed5a8c..c22d19dca 100644 --- a/pkg/util/logging/dual_mode_logger_test.go +++ b/pkg/util/logging/dual_mode_logger_test.go @@ -26,7 +26,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - velerotest "github.com/velero-io/velero/pkg/test" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestDualModeLogger(t *testing.T) { diff --git a/pkg/util/logging/error_location_hook_test.go b/pkg/util/logging/error_location_hook_test.go index 664b275a0..f6f230c02 100644 --- a/pkg/util/logging/error_location_hook_test.go +++ b/pkg/util/logging/error_location_hook_test.go @@ -55,7 +55,7 @@ func TestFire(t *testing.T) { expectedEntryFields: map[string]any{ logrus.ErrorKey: pkgerrs.New("a pkg/errors error"), errorFileField: "", - errorFunctionField: "github.com/velero-io/velero/pkg/util/logging.TestFire", + errorFunctionField: "github.com/vmware-tanzu/velero/pkg/util/logging.TestFire", }, }, { diff --git a/pkg/util/logging/format_flag.go b/pkg/util/logging/format_flag.go index d49af16a3..c757a17dd 100644 --- a/pkg/util/logging/format_flag.go +++ b/pkg/util/logging/format_flag.go @@ -15,7 +15,7 @@ limitations under the License. */ package logging -import "github.com/velero-io/velero/pkg/cmd/util/flag" +import "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" // Format is a string representation of the desired output format for logs type Format string diff --git a/pkg/util/logging/log_counter_hook.go b/pkg/util/logging/log_counter_hook.go index 52e453fc3..63c9342df 100644 --- a/pkg/util/logging/log_counter_hook.go +++ b/pkg/util/logging/log_counter_hook.go @@ -23,7 +23,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/pkg/util/results" ) // LogHook is a logrus hook that counts the number of log diff --git a/pkg/util/logging/log_counter_hook_test.go b/pkg/util/logging/log_counter_hook_test.go index 989e155fc..1afd2bc29 100644 --- a/pkg/util/logging/log_counter_hook_test.go +++ b/pkg/util/logging/log_counter_hook_test.go @@ -9,7 +9,7 @@ import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" - "github.com/velero-io/velero/pkg/util/results" + "github.com/vmware-tanzu/velero/pkg/util/results" ) func TestLogHook_Fire(t *testing.T) { diff --git a/pkg/util/logging/log_level_flag.go b/pkg/util/logging/log_level_flag.go index 1dd7fd111..ff0f0efb2 100644 --- a/pkg/util/logging/log_level_flag.go +++ b/pkg/util/logging/log_level_flag.go @@ -21,7 +21,7 @@ import ( "github.com/sirupsen/logrus" - "github.com/velero-io/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" ) var sortedLogLevels = sortLogLevels() diff --git a/pkg/util/logging/log_location_hook.go b/pkg/util/logging/log_location_hook.go index c2abf512f..a0e88813a 100644 --- a/pkg/util/logging/log_location_hook.go +++ b/pkg/util/logging/log_location_hook.go @@ -28,7 +28,7 @@ const ( logSourceField = "logSource" logSourceSetMarkerField = "@logSourceSetBy" logrusPackage = "github.com/sirupsen/logrus" - veleroPackage = "github.com/velero-io/velero/" + veleroPackage = "github.com/vmware-tanzu/velero/" veleroPackageLen = len(veleroPackage) ) @@ -60,7 +60,7 @@ func (h *LogLocationHook) Fire(entry *logrus.Entry) error { // skip 2 frames: // runtime.Callers - // github.com/velero-io/velero/pkg/util/logging/(*LogLocationHook).Fire + // github.com/vmware-tanzu/velero/pkg/util/logging/(*LogLocationHook).Fire n := runtime.Callers(2, pcs) // re-slice pcs based on the number of entries written @@ -122,7 +122,7 @@ func getLogSourceSetMarker(entry *logrus.Entry) string { func removeVeleroPackagePrefix(file string) string { if index := strings.Index(file, veleroPackage); index != -1 { - // strip off .../github.com/velero-io/velero/ so we just have pkg/... + // strip off .../github.com/vmware-tanzu/velero/ so we just have pkg/... return file[index+veleroPackageLen:] } diff --git a/pkg/util/logging/log_location_hook_test.go b/pkg/util/logging/log_location_hook_test.go index 8fc23daad..74f007a0b 100644 --- a/pkg/util/logging/log_location_hook_test.go +++ b/pkg/util/logging/log_location_hook_test.go @@ -23,6 +23,6 @@ import ( ) func TestRemoveVeleroPackagePrefix(t *testing.T) { - assert.Equal(t, "pkg/foo.go", removeVeleroPackagePrefix("github.com/velero-io/velero/pkg/foo.go")) - assert.Equal(t, "github.com/velero-io/velero-plugin-example/foo.go", removeVeleroPackagePrefix("github.com/velero-io/velero-plugin-example/foo.go")) + assert.Equal(t, "pkg/foo.go", removeVeleroPackagePrefix("github.com/vmware-tanzu/velero/pkg/foo.go")) + assert.Equal(t, "github.com/vmware-tanzu/velero-plugin-example/foo.go", removeVeleroPackagePrefix("github.com/vmware-tanzu/velero-plugin-example/foo.go")) } diff --git a/pkg/util/podvolume/pod_volume.go b/pkg/util/podvolume/pod_volume.go index 42a36fcbb..7c7e0f9c4 100644 --- a/pkg/util/podvolume/pod_volume.go +++ b/pkg/util/podvolume/pod_volume.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" crclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/util" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/util" ) // PVCPodCache provides a cached mapping from PVC to the pods that use it. diff --git a/pkg/util/podvolume/pod_volume_test.go b/pkg/util/podvolume/pod_volume_test.go index 894a88034..87a6f3a0f 100644 --- a/pkg/util/podvolume/pod_volume_test.go +++ b/pkg/util/podvolume/pod_volume_test.go @@ -26,8 +26,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/runtime" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerotest "github.com/velero-io/velero/pkg/test" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerotest "github.com/vmware-tanzu/velero/pkg/test" ) func TestGetVolumesToBackup(t *testing.T) { diff --git a/pkg/util/scheme.go b/pkg/util/scheme.go index 893594e12..c398e4196 100644 --- a/pkg/util/scheme.go +++ b/pkg/util/scheme.go @@ -20,8 +20,8 @@ import ( "k8s.io/apimachinery/pkg/runtime" utilruntime "k8s.io/apimachinery/pkg/util/runtime" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) var VeleroScheme = runtime.NewScheme() diff --git a/pkg/util/velero/restore/util.go b/pkg/util/velero/restore/util.go index b054ae606..e0812884b 100644 --- a/pkg/util/velero/restore/util.go +++ b/pkg/util/velero/restore/util.go @@ -1,7 +1,7 @@ package restore import ( - api "github.com/velero-io/velero/pkg/apis/velero/v1" + api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func IsResourcePolicyValid(resourcePolicy string) bool { diff --git a/pkg/util/velero/restore/util_test.go b/pkg/util/velero/restore/util_test.go index dc1f82d22..be72ff8ba 100644 --- a/pkg/util/velero/restore/util_test.go +++ b/pkg/util/velero/restore/util_test.go @@ -5,7 +5,7 @@ import ( "github.com/stretchr/testify/require" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) func TestIsResourcePolicyValid(t *testing.T) { diff --git a/pkg/util/velero/velero.go b/pkg/util/velero/velero.go index a47312775..a58d6e76b 100644 --- a/pkg/util/velero/velero.go +++ b/pkg/util/velero/velero.go @@ -20,7 +20,7 @@ import ( appsv1api "k8s.io/api/apps/v1" corev1api "k8s.io/api/core/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" ) // GetNodeSelectorFromVeleroServer get the node selector from the Velero server deployment diff --git a/pkg/util/velero/velero_test.go b/pkg/util/velero/velero_test.go index 9d2060341..c4e201780 100644 --- a/pkg/util/velero/velero_test.go +++ b/pkg/util/velero/velero_test.go @@ -26,9 +26,9 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/pkg/util/boolptr" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" ) func TestGetNodeSelectorFromVeleroServer(t *testing.T) { diff --git a/restore-hooks_product-requirements.md b/restore-hooks_product-requirements.md index cb62c6818..1b943fe82 100644 --- a/restore-hooks_product-requirements.md +++ b/restore-hooks_product-requirements.md @@ -2,7 +2,7 @@ Velero Restore Hooks - PRD (Product Requirements Document) MVP Feature Set -Relates to: [https://github.com/velero-io/velero/issues/2116](https://github.com/velero-io/velero/issues/2116) +Relates to: [https://github.com/vmware-tanzu/velero/issues/2116](https://github.com/vmware-tanzu/velero/issues/2116) # **Change tracking** @@ -23,9 +23,9 @@ _This is a live document, you can reach me on the following channels for more in -* [https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/velero-io/velero/2465](https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/velero-io/velero/2465) - * [https://github.com/velero-io/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a](https://github.com/velero-io/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a) -* [https://github.com/velero-io/velero/issues/1150](https://github.com/velero-io/velero/issues/1150) +* [https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/vmware-tanzu/velero/2465](https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/issues/vmware-tanzu/velero/2465) + * [https://github.com/vmware-tanzu/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a](https://github.com/vmware-tanzu/velero/pull/2465/files?short_path=140e0c6#diff-140e0c6b370f250ee97f6ecafc8dbb7a) +* [https://github.com/vmware-tanzu/velero/issues/1150](https://github.com/vmware-tanzu/velero/issues/1150) Background @@ -79,7 +79,7 @@ MVP Use Cases The following use cases must be included as part of the Velero restore hooks MVP (minimum viable product). -**Note: **Processing of concurrent vs sequential workloads is slated later in the Velero roadmap (see [https://github.com/velero-io/velero/pull/2548/files](https://github.com/velero-io/velero/pull/2548/files)). The MVP for this feature set will align with restore of single workloads vs concurrent workload restores. A second epic will be created to address the concurrent restore operations and will be added to the backlog for priority visibility. +**Note: **Processing of concurrent vs sequential workloads is slated later in the Velero roadmap (see [https://github.com/vmware-tanzu/velero/pull/2548/files](https://github.com/vmware-tanzu/velero/pull/2548/files)). The MVP for this feature set will align with restore of single workloads vs concurrent workload restores. A second epic will be created to address the concurrent restore operations and will be added to the backlog for priority visibility. **Note: **Please refer to the Requirements section of this document for more details on what items are P0 (must have in the MVP), P1 (should not ship without for the MVP), P2 (nice to haves). diff --git a/test/e2e/README.md b/test/e2e/README.md index 583606971..f4e7714af 100644 --- a/test/e2e/README.md +++ b/test/e2e/README.md @@ -180,8 +180,8 @@ make test-e2e ``` Please refer to `velero-plugin-for-microsoft-azure` documentation for instruction: -* [set up permissions for Velero](https://github.com/velero-io/velero-plugin-for-microsoft-azure#set-permissions-for-velero) -* [set up azure storage account and blob container](https://github.com/velero-io/velero-plugin-for-microsoft-azure#setup-azure-storage-account-and-blob-container) +* [set up permissions for Velero](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#set-permissions-for-velero) +* [set up azure storage account and blob container](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure#setup-azure-storage-account-and-blob-container) 1. Run Multi-API group and version tests using MinIO as the backup storage location: ``` bash diff --git a/test/e2e/backup/backup.go b/test/e2e/backup/backup.go index 91b0fcae0..43a6f4f23 100644 --- a/test/e2e/backup/backup.go +++ b/test/e2e/backup/backup.go @@ -25,11 +25,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type BackupRestoreTestConfig struct { @@ -208,7 +208,7 @@ func BackupRestoreTest(backupRestoreTestConfig BackupRestoreTestConfig) { )).To(Succeed()) // We limit the length of backup name here to avoid the issue of vsphere plugin - // https://github.com/velero-io/velero-plugin-for-vsphere/issues/370 + // https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/370 // We can remove the logic once the issue is fixed backupName = "backup-" + common.AdditionalBSLName restoreName = "restore-" + common.AdditionalBSLName diff --git a/test/e2e/backups/deletion.go b/test/e2e/backups/deletion.go index ccffcec55..54388b70a 100644 --- a/test/e2e/backups/deletion.go +++ b/test/e2e/backups/deletion.go @@ -27,11 +27,11 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) // Test backup and restore of Kibishii using restic diff --git a/test/e2e/backups/sync_backups.go b/test/e2e/backups/sync_backups.go index cbbba10c1..447fc735b 100644 --- a/test/e2e/backups/sync_backups.go +++ b/test/e2e/backups/sync_backups.go @@ -16,7 +16,7 @@ * / */ -// Refer to https://github.com/velero-io/velero/issues/4253 +// Refer to https://github.com/vmware-tanzu/velero/issues/4253 package backups import ( @@ -30,10 +30,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type SyncBackups struct { diff --git a/test/e2e/backups/ttl.go b/test/e2e/backups/ttl.go index 998e55f19..f781c32d4 100644 --- a/test/e2e/backups/ttl.go +++ b/test/e2e/backups/ttl.go @@ -30,11 +30,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type TTL struct { diff --git a/test/e2e/basic/api-group/enable_api_group_extentions.go b/test/e2e/basic/api-group/enable_api_group_extentions.go index 11a057f3e..546d2f721 100644 --- a/test/e2e/basic/api-group/enable_api_group_extentions.go +++ b/test/e2e/basic/api-group/enable_api_group_extentions.go @@ -24,9 +24,9 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) func APIExtensionsVersionsTest() { diff --git a/test/e2e/basic/api-group/enable_api_group_versions.go b/test/e2e/basic/api-group/enable_api_group_versions.go index 5155b8497..13ee3a39e 100644 --- a/test/e2e/basic/api-group/enable_api_group_versions.go +++ b/test/e2e/basic/api-group/enable_api_group_versions.go @@ -34,11 +34,11 @@ import ( corev1api "k8s.io/api/core/v1" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - "github.com/velero-io/velero/pkg/builder" - veleroexec "github.com/velero-io/velero/pkg/util/exec" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + "github.com/vmware-tanzu/velero/pkg/builder" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var veleroCfg VeleroConfig diff --git a/test/e2e/basic/backup-volume-info/base.go b/test/e2e/basic/backup-volume-info/base.go index 8f2da8772..2cd574b5c 100644 --- a/test/e2e/basic/backup-volume-info/base.go +++ b/test/e2e/basic/backup-volume-info/base.go @@ -27,11 +27,11 @@ import ( "github.com/pkg/errors" corev1api "k8s.io/api/core/v1" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type BackupVolumeInfo struct { @@ -144,7 +144,7 @@ func (v *BackupVolumeInfo) CreateResources() error { for _, pod := range podList.Items { for i := 0; i <= pvcCount-1; i++ { - // Hitting issue https://github.com/velero-io/velero/issues/7388 + // Hitting issue https://github.com/vmware-tanzu/velero/issues/7388 // So populate data only to some of pods, leave other pods empty to verify empty PV datamover if i%2 == 0 { Expect(CreateFileToPod( diff --git a/test/e2e/basic/backup-volume-info/csi_data_mover.go b/test/e2e/basic/backup-volume-info/csi_data_mover.go index 9731c7d4b..43edb0ddb 100644 --- a/test/e2e/basic/backup-volume-info/csi_data_mover.go +++ b/test/e2e/basic/backup-volume-info/csi_data_mover.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var CSIDataMoverVolumeInfoTest func() = TestFunc(&CSIDataMoverVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/csi_snapshot.go b/test/e2e/basic/backup-volume-info/csi_snapshot.go index fe008baaa..5eddb4ea2 100644 --- a/test/e2e/basic/backup-volume-info/csi_snapshot.go +++ b/test/e2e/basic/backup-volume-info/csi_snapshot.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var CSISnapshotVolumeInfoTest func() = TestFunc(&CSISnapshotVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/filesystem_upload.go b/test/e2e/basic/backup-volume-info/filesystem_upload.go index 7c176fc50..e6266c0c6 100644 --- a/test/e2e/basic/backup-volume-info/filesystem_upload.go +++ b/test/e2e/basic/backup-volume-info/filesystem_upload.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var FilesystemUploadVolumeInfoTest func() = TestFunc(&FilesystemUploadVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/native_snapshot.go b/test/e2e/basic/backup-volume-info/native_snapshot.go index 725755f5b..13a75d2e6 100644 --- a/test/e2e/basic/backup-volume-info/native_snapshot.go +++ b/test/e2e/basic/backup-volume-info/native_snapshot.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var NativeSnapshotVolumeInfoTest func() = TestFunc(&NativeSnapshotVolumeInfo{ diff --git a/test/e2e/basic/backup-volume-info/skipped_volumes.go b/test/e2e/basic/backup-volume-info/skipped_volumes.go index 755c527b9..2fc801a5f 100644 --- a/test/e2e/basic/backup-volume-info/skipped_volumes.go +++ b/test/e2e/basic/backup-volume-info/skipped_volumes.go @@ -21,9 +21,9 @@ import ( . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var SkippedVolumeInfoTest func() = TestFunc(&SkippedVolumeInfo{ diff --git a/test/e2e/basic/namespace-mapping.go b/test/e2e/basic/namespace-mapping.go index 54314e5dc..6816b2df0 100644 --- a/test/e2e/basic/namespace-mapping.go +++ b/test/e2e/basic/namespace-mapping.go @@ -8,9 +8,9 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" ) type NamespaceMapping struct { diff --git a/test/e2e/basic/nodeport.go b/test/e2e/basic/nodeport.go index 18f11fa1e..b561295a1 100644 --- a/test/e2e/basic/nodeport.go +++ b/test/e2e/basic/nodeport.go @@ -10,10 +10,10 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/util/intstr" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type NodePort struct { diff --git a/test/e2e/basic/resources-check/namespaces.go b/test/e2e/basic/resources-check/namespaces.go index c2f8e7d33..922e4ed07 100644 --- a/test/e2e/basic/resources-check/namespaces.go +++ b/test/e2e/basic/resources-check/namespaces.go @@ -25,8 +25,8 @@ import ( "github.com/pkg/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type MultiNSBackup struct { diff --git a/test/e2e/basic/resources-check/namespaces_annotation.go b/test/e2e/basic/resources-check/namespaces_annotation.go index e835b99f7..e698d4818 100644 --- a/test/e2e/basic/resources-check/namespaces_annotation.go +++ b/test/e2e/basic/resources-check/namespaces_annotation.go @@ -22,8 +22,8 @@ import ( "github.com/pkg/errors" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type NSAnnotationCase struct { diff --git a/test/e2e/basic/resources-check/rbac.go b/test/e2e/basic/resources-check/rbac.go index 9ab4a4e90..b79c3615f 100644 --- a/test/e2e/basic/resources-check/rbac.go +++ b/test/e2e/basic/resources-check/rbac.go @@ -39,8 +39,8 @@ import ( . "github.com/onsi/ginkgo/v2" "github.com/pkg/errors" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type RBACCase struct { diff --git a/test/e2e/basic/resources-check/resources_check.go b/test/e2e/basic/resources-check/resources_check.go index b656300c4..880063657 100644 --- a/test/e2e/basic/resources-check/resources_check.go +++ b/test/e2e/basic/resources-check/resources_check.go @@ -33,7 +33,7 @@ limitations under the License. package basic import ( - . "github.com/velero-io/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" ) func GetResourcesCheckTestCases() []VeleroBackupRestoreTest { diff --git a/test/e2e/basic/restore_exec_hooks.go b/test/e2e/basic/restore_exec_hooks.go index 10757feff..fc1b8ceb8 100644 --- a/test/e2e/basic/restore_exec_hooks.go +++ b/test/e2e/basic/restore_exec_hooks.go @@ -24,10 +24,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) // RestoreExecHooks tests that a pod with multiple restore exec hooks does not hang diff --git a/test/e2e/basic/storage-class-changing.go b/test/e2e/basic/storage-class-changing.go index 9a0aa17cb..08481d4ad 100644 --- a/test/e2e/basic/storage-class-changing.go +++ b/test/e2e/basic/storage-class-changing.go @@ -7,12 +7,12 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type StorageClasssChanging struct { diff --git a/test/e2e/bsl-mgmt/deletion.go b/test/e2e/bsl-mgmt/deletion.go index 9088dee01..838aa67b5 100644 --- a/test/e2e/bsl-mgmt/deletion.go +++ b/test/e2e/bsl-mgmt/deletion.go @@ -27,11 +27,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) const ( @@ -143,7 +143,7 @@ func BslDeletionTest(useVolumeSnapshots bool) { podName2 := "kibishii-deployment-1" label1 := "for=1" - // TODO remove when issue https://github.com/velero-io/velero/issues/4724 is fixed + // TODO remove when issue https://github.com/vmware-tanzu/velero/issues/4724 is fixed //label2 := "for!=1" label2 := "for=2" By("Create namespace for sample workload", func() { diff --git a/test/e2e/e2e_suite_test.go b/test/e2e/e2e_suite_test.go index dadd3a2b9..909cc8074 100644 --- a/test/e2e/e2e_suite_test.go +++ b/test/e2e/e2e_suite_test.go @@ -29,30 +29,30 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/velero-io/velero/pkg/cmd/cli/install" - "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/backup" - . "github.com/velero-io/velero/test/e2e/backups" - . "github.com/velero-io/velero/test/e2e/basic" - . "github.com/velero-io/velero/test/e2e/basic/api-group" - . "github.com/velero-io/velero/test/e2e/basic/backup-volume-info" - . "github.com/velero-io/velero/test/e2e/basic/resources-check" - . "github.com/velero-io/velero/test/e2e/bsl-mgmt" - . "github.com/velero-io/velero/test/e2e/migration" - . "github.com/velero-io/velero/test/e2e/nodeagentconfig" - . "github.com/velero-io/velero/test/e2e/parallelfilesdownload" - . "github.com/velero-io/velero/test/e2e/parallelfilesupload" - . "github.com/velero-io/velero/test/e2e/privilegesmgmt" - . "github.com/velero-io/velero/test/e2e/pv-backup" - . "github.com/velero-io/velero/test/e2e/repomaintenance" - . "github.com/velero-io/velero/test/e2e/resource-filtering" - . "github.com/velero-io/velero/test/e2e/resourcemodifiers" - . "github.com/velero-io/velero/test/e2e/resourcepolicies" - . "github.com/velero-io/velero/test/e2e/scale" - . "github.com/velero-io/velero/test/e2e/schedule" - . "github.com/velero-io/velero/test/e2e/upgrade" - "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/backup" + . "github.com/vmware-tanzu/velero/test/e2e/backups" + . "github.com/vmware-tanzu/velero/test/e2e/basic" + . "github.com/vmware-tanzu/velero/test/e2e/basic/api-group" + . "github.com/vmware-tanzu/velero/test/e2e/basic/backup-volume-info" + . "github.com/vmware-tanzu/velero/test/e2e/basic/resources-check" + . "github.com/vmware-tanzu/velero/test/e2e/bsl-mgmt" + . "github.com/vmware-tanzu/velero/test/e2e/migration" + . "github.com/vmware-tanzu/velero/test/e2e/nodeagentconfig" + . "github.com/vmware-tanzu/velero/test/e2e/parallelfilesdownload" + . "github.com/vmware-tanzu/velero/test/e2e/parallelfilesupload" + . "github.com/vmware-tanzu/velero/test/e2e/privilegesmgmt" + . "github.com/vmware-tanzu/velero/test/e2e/pv-backup" + . "github.com/vmware-tanzu/velero/test/e2e/repomaintenance" + . "github.com/vmware-tanzu/velero/test/e2e/resource-filtering" + . "github.com/vmware-tanzu/velero/test/e2e/resourcemodifiers" + . "github.com/vmware-tanzu/velero/test/e2e/resourcepolicies" + . "github.com/vmware-tanzu/velero/test/e2e/scale" + . "github.com/vmware-tanzu/velero/test/e2e/schedule" + . "github.com/vmware-tanzu/velero/test/e2e/upgrade" + "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) func init() { diff --git a/test/e2e/migration/migration.go b/test/e2e/migration/migration.go index faeafc2c8..e890189c3 100644 --- a/test/e2e/migration/migration.go +++ b/test/e2e/migration/migration.go @@ -24,14 +24,14 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - "github.com/velero-io/velero/test" - framework "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - util "github.com/velero-io/velero/test/util/csi" - k8sutil "github.com/velero-io/velero/test/util/k8s" - "github.com/velero-io/velero/test/util/kibishii" - "github.com/velero-io/velero/test/util/providers" - veleroutil "github.com/velero-io/velero/test/util/velero" + "github.com/vmware-tanzu/velero/test" + framework "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + util "github.com/vmware-tanzu/velero/test/util/csi" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/test/util/kibishii" + "github.com/vmware-tanzu/velero/test/util/providers" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) const BackupObjectsPrefix = "backups" @@ -283,7 +283,7 @@ func (m *migrationE2E) Backup() error { }) } else { // the snapshots of AWS may be still in pending status when do the restore. - // wait for a while to avoid this https://github.com/velero-io/velero/issues/1799 + // wait for a while to avoid this https://github.com/vmware-tanzu/velero/issues/1799 if OriginVeleroCfg.CloudProvider == test.Azure && strings.EqualFold(OriginVeleroCfg.Features, test.FeatureCSI) || OriginVeleroCfg.CloudProvider == test.AWS { diff --git a/test/e2e/nodeagentconfig/cache_pvc.go b/test/e2e/nodeagentconfig/cache_pvc.go index 2f5029215..9104946c7 100644 --- a/test/e2e/nodeagentconfig/cache_pvc.go +++ b/test/e2e/nodeagentconfig/cache_pvc.go @@ -29,13 +29,13 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) type CachePVCTestCase struct { diff --git a/test/e2e/nodeagentconfig/node-agent-config.go b/test/e2e/nodeagentconfig/node-agent-config.go index 115594197..5266bffc5 100644 --- a/test/e2e/nodeagentconfig/node-agent-config.go +++ b/test/e2e/nodeagentconfig/node-agent-config.go @@ -31,15 +31,15 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" - "github.com/velero-io/velero/pkg/builder" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) type NodeAgentConfigTestCase struct { diff --git a/test/e2e/parallelfilesdownload/parallel_files_download.go b/test/e2e/parallelfilesdownload/parallel_files_download.go index b67af2324..bc4d61323 100644 --- a/test/e2e/parallelfilesdownload/parallel_files_download.go +++ b/test/e2e/parallelfilesdownload/parallel_files_download.go @@ -22,10 +22,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type ParallelFilesDownload struct { diff --git a/test/e2e/parallelfilesupload/parallel_files_upload.go b/test/e2e/parallelfilesupload/parallel_files_upload.go index bc9b6e4c0..b11e3382b 100644 --- a/test/e2e/parallelfilesupload/parallel_files_upload.go +++ b/test/e2e/parallelfilesupload/parallel_files_upload.go @@ -22,10 +22,10 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type ParallelFilesUpload struct { diff --git a/test/e2e/privilegesmgmt/ssr.go b/test/e2e/privilegesmgmt/ssr.go index e6c7fea7b..9b0e99a0f 100644 --- a/test/e2e/privilegesmgmt/ssr.go +++ b/test/e2e/privilegesmgmt/ssr.go @@ -29,10 +29,10 @@ import ( waitutil "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - v1 "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + v1 "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) func SSRTest() { diff --git a/test/e2e/pv-backup/pv-backup-filter.go b/test/e2e/pv-backup/pv-backup-filter.go index df3ae2333..5a6730551 100644 --- a/test/e2e/pv-backup/pv-backup-filter.go +++ b/test/e2e/pv-backup/pv-backup-filter.go @@ -10,11 +10,11 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type PVBackupFiltering struct { diff --git a/test/e2e/repomaintenance/repo_maintenance_config.go b/test/e2e/repomaintenance/repo_maintenance_config.go index f874896ec..c0092c4bf 100644 --- a/test/e2e/repomaintenance/repo_maintenance_config.go +++ b/test/e2e/repomaintenance/repo_maintenance_config.go @@ -29,15 +29,15 @@ import ( "k8s.io/apimachinery/pkg/labels" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - velerotypes "github.com/velero-io/velero/pkg/types" - "github.com/velero-io/velero/pkg/util/kube" - velerokubeutil "github.com/velero-io/velero/pkg/util/kube" - "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + velerotypes "github.com/vmware-tanzu/velero/pkg/types" + "github.com/vmware-tanzu/velero/pkg/util/kube" + velerokubeutil "github.com/vmware-tanzu/velero/pkg/util/kube" + "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) type RepoMaintenanceTestCase struct { diff --git a/test/e2e/resource-filtering/base.go b/test/e2e/resource-filtering/base.go index 021dac7cc..f4070d9e7 100644 --- a/test/e2e/resource-filtering/base.go +++ b/test/e2e/resource-filtering/base.go @@ -23,9 +23,9 @@ import ( "github.com/pkg/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) type FilteringCase struct { diff --git a/test/e2e/resource-filtering/exclude_label.go b/test/e2e/resource-filtering/exclude_label.go index bd1c297bf..695d7d8ed 100644 --- a/test/e2e/resource-filtering/exclude_label.go +++ b/test/e2e/resource-filtering/exclude_label.go @@ -24,10 +24,10 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/exclude_namespaces.go b/test/e2e/resource-filtering/exclude_namespaces.go index e4be6302f..1b8e5da55 100644 --- a/test/e2e/resource-filtering/exclude_namespaces.go +++ b/test/e2e/resource-filtering/exclude_namespaces.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/exclude_resources.go b/test/e2e/resource-filtering/exclude_resources.go index dcee6c7aa..b8a7d2e73 100644 --- a/test/e2e/resource-filtering/exclude_resources.go +++ b/test/e2e/resource-filtering/exclude_resources.go @@ -24,9 +24,9 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/include_namespaces.go b/test/e2e/resource-filtering/include_namespaces.go index 363e4b9a9..d511de212 100644 --- a/test/e2e/resource-filtering/include_namespaces.go +++ b/test/e2e/resource-filtering/include_namespaces.go @@ -23,8 +23,8 @@ import ( "github.com/pkg/errors" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/include_resources.go b/test/e2e/resource-filtering/include_resources.go index 2b86dc59e..22d7e968b 100644 --- a/test/e2e/resource-filtering/include_resources.go +++ b/test/e2e/resource-filtering/include_resources.go @@ -24,8 +24,8 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/label_selector.go b/test/e2e/resource-filtering/label_selector.go index 6f310f863..9ecc66a0c 100644 --- a/test/e2e/resource-filtering/label_selector.go +++ b/test/e2e/resource-filtering/label_selector.go @@ -24,9 +24,9 @@ import ( apierrors "k8s.io/apimachinery/pkg/api/errors" metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) /* diff --git a/test/e2e/resource-filtering/wildcard_namespaces.go b/test/e2e/resource-filtering/wildcard_namespaces.go index aab0bc3b2..c3cd50071 100644 --- a/test/e2e/resource-filtering/wildcard_namespaces.go +++ b/test/e2e/resource-filtering/wildcard_namespaces.go @@ -23,8 +23,8 @@ import ( . "github.com/onsi/gomega" apierrors "k8s.io/apimachinery/pkg/api/errors" - . "github.com/velero-io/velero/test/e2e/test" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) // WildcardNamespaces tests the inclusion and exclusion of namespaces using wildcards diff --git a/test/e2e/resourcemodifiers/resource_modifiers.go b/test/e2e/resourcemodifiers/resource_modifiers.go index 4e20cd613..06cbd91f1 100644 --- a/test/e2e/resourcemodifiers/resource_modifiers.go +++ b/test/e2e/resourcemodifiers/resource_modifiers.go @@ -24,9 +24,9 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) var yamlData = ` diff --git a/test/e2e/resourcepolicies/resource_policies.go b/test/e2e/resourcepolicies/resource_policies.go index da68e44f7..f3254eb04 100644 --- a/test/e2e/resourcepolicies/resource_policies.go +++ b/test/e2e/resourcepolicies/resource_policies.go @@ -27,10 +27,10 @@ import ( corev1api "k8s.io/api/core/v1" "k8s.io/apimachinery/pkg/api/resource" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) const FileName = "test-data.txt" diff --git a/test/e2e/scale/multiple_namespaces.go b/test/e2e/scale/multiple_namespaces.go index 4a55539b3..6bc4e4f9a 100644 --- a/test/e2e/scale/multiple_namespaces.go +++ b/test/e2e/scale/multiple_namespaces.go @@ -17,8 +17,8 @@ limitations under the License. package scale import ( - basic "github.com/velero-io/velero/test/e2e/basic/resources-check" - . "github.com/velero-io/velero/test/e2e/test" + basic "github.com/vmware-tanzu/velero/test/e2e/basic/resources-check" + . "github.com/vmware-tanzu/velero/test/e2e/test" ) var MultiNSBackupRestore func() = TestFunc(&basic.MultiNSBackup{IsScaleTest: true}) diff --git a/test/e2e/schedule/in_progress.go b/test/e2e/schedule/in_progress.go index 651905449..060740c3f 100644 --- a/test/e2e/schedule/in_progress.go +++ b/test/e2e/schedule/in_progress.go @@ -11,12 +11,12 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/test" - framework "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/test" + framework "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) var ScheduleInProgressTest func() = framework.TestFunc(&InProgressCase{}) diff --git a/test/e2e/schedule/ordered_resources.go b/test/e2e/schedule/ordered_resources.go index d0464bd3a..df0d8b972 100644 --- a/test/e2e/schedule/ordered_resources.go +++ b/test/e2e/schedule/ordered_resources.go @@ -16,7 +16,7 @@ See the License for the specific language governing permissions and limitations under the License. */ -//the ordered resources test related to https://github.com/velero-io/velero/issues/4561 +//the ordered resources test related to https://github.com/vmware-tanzu/velero/issues/4561 import ( "context" "fmt" @@ -30,11 +30,11 @@ import ( waitutil "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - framework "github.com/velero-io/velero/test/e2e/test" - "github.com/velero-io/velero/test/util/common" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + framework "github.com/vmware-tanzu/velero/test/e2e/test" + "github.com/vmware-tanzu/velero/test/util/common" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) var ScheduleOrderedResources func() = framework.TestFunc(&OrderedResources{}) diff --git a/test/e2e/schedule/periodical.go b/test/e2e/schedule/periodical.go index cb904d00e..330356e99 100644 --- a/test/e2e/schedule/periodical.go +++ b/test/e2e/schedule/periodical.go @@ -10,10 +10,10 @@ import ( . "github.com/onsi/gomega" "k8s.io/apimachinery/pkg/util/wait" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - framework "github.com/velero-io/velero/test/e2e/test" - k8sutil "github.com/velero-io/velero/test/util/k8s" - veleroutil "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + framework "github.com/vmware-tanzu/velero/test/e2e/test" + k8sutil "github.com/vmware-tanzu/velero/test/util/k8s" + veleroutil "github.com/vmware-tanzu/velero/test/util/velero" ) type PeriodicalCase struct { diff --git a/test/e2e/test/test.go b/test/e2e/test/test.go index dda3f3870..1a91c115f 100644 --- a/test/e2e/test/test.go +++ b/test/e2e/test/test.go @@ -27,10 +27,10 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) /* @@ -146,8 +146,8 @@ func (t *TestCase) Restore() error { veleroCfg := t.GetTestCase().VeleroCfg // the snapshots of AWS may be still in pending status when do the restore, wait for a while - // to avoid this https://github.com/velero-io/velero/issues/1799 - // TODO remove this after https://github.com/velero-io/velero/issues/3533 is fixed + // to avoid this https://github.com/vmware-tanzu/velero/issues/1799 + // TODO remove this after https://github.com/vmware-tanzu/velero/issues/3533 is fixed By("Waiting 5 minutes to make sure the snapshots are ready...", func() { if t.UseVolumeSnapshots && veleroCfg.CloudProvider != Vsphere { time.Sleep(5 * time.Minute) diff --git a/test/e2e/upgrade/upgrade.go b/test/e2e/upgrade/upgrade.go index 91ade0cfa..6d081f1c1 100644 --- a/test/e2e/upgrade/upgrade.go +++ b/test/e2e/upgrade/upgrade.go @@ -26,11 +26,11 @@ import ( . "github.com/onsi/ginkgo/v2" . "github.com/onsi/gomega" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/kibishii" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/kibishii" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) var upgradeNamespace string @@ -236,8 +236,8 @@ func BackupUpgradeRestoreTest(useVolumeSnapshots bool, veleroCLI2Version VeleroC }) } // the snapshots of AWS may be still in pending status when do the restore, wait for a while - // to avoid this https://github.com/velero-io/velero/issues/1799 - // TODO remove this after https://github.com/velero-io/velero/issues/3533 is fixed + // to avoid this https://github.com/vmware-tanzu/velero/issues/1799 + // TODO remove this after https://github.com/vmware-tanzu/velero/issues/3533 is fixed if tmpCfg.CloudProvider == AWS && useVolumeSnapshots { fmt.Println("Waiting 5 minutes to make sure the snapshots are ready...") time.Sleep(5 * time.Minute) diff --git a/test/perf/README.md b/test/perf/README.md index 79e99d95d..a3dd295ba 100644 --- a/test/perf/README.md +++ b/test/perf/README.md @@ -2,4 +2,4 @@ Document for running Velero end-to-end performance test suite. -And the data generate tool for performance test could be found in [here](https://github.com/velero-io/velero-performance-test) \ No newline at end of file +And the data generate tool for performance test could be found in [here](https://github.com/vmware-tanzu/velero-performance-test) \ No newline at end of file diff --git a/test/perf/backup/backup.go b/test/perf/backup/backup.go index 91c5ff9b0..c8c39a6e1 100644 --- a/test/perf/backup/backup.go +++ b/test/perf/backup/backup.go @@ -21,8 +21,8 @@ import ( "strings" "time" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/perf/test" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/perf/test" ) type BackupTest struct { diff --git a/test/perf/basic/basic.go b/test/perf/basic/basic.go index 5ebbf70c1..76bf605a6 100644 --- a/test/perf/basic/basic.go +++ b/test/perf/basic/basic.go @@ -23,9 +23,9 @@ import ( "github.com/pkg/errors" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/perf/test" - "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/perf/test" + "github.com/vmware-tanzu/velero/test/util/k8s" ) type BasicTest struct { diff --git a/test/perf/e2e_suite_test.go b/test/perf/e2e_suite_test.go index a54215dc5..48a5ceec9 100644 --- a/test/perf/e2e_suite_test.go +++ b/test/perf/e2e_suite_test.go @@ -27,15 +27,15 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/cmd/cli/install" - . "github.com/velero-io/velero/test" - "github.com/velero-io/velero/test/perf/backup" - "github.com/velero-io/velero/test/perf/basic" - "github.com/velero-io/velero/test/perf/restore" - "github.com/velero-io/velero/test/perf/test" - . "github.com/velero-io/velero/test/util/k8s" - "github.com/velero-io/velero/test/util/report" - . "github.com/velero-io/velero/test/util/velero" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + . "github.com/vmware-tanzu/velero/test" + "github.com/vmware-tanzu/velero/test/perf/backup" + "github.com/vmware-tanzu/velero/test/perf/basic" + "github.com/vmware-tanzu/velero/test/perf/restore" + "github.com/vmware-tanzu/velero/test/perf/test" + . "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/test/util/report" + . "github.com/vmware-tanzu/velero/test/util/velero" ) func init() { diff --git a/test/perf/metrics/minio.go b/test/perf/metrics/minio.go index ecb20a3d3..8ea7ae4c3 100644 --- a/test/perf/metrics/minio.go +++ b/test/perf/metrics/minio.go @@ -19,7 +19,7 @@ package metrics import ( "github.com/pkg/errors" - "github.com/velero-io/velero/test/util/metrics" + "github.com/vmware-tanzu/velero/test/util/metrics" ) const MinioDesc = "Minio disk usage" diff --git a/test/perf/metrics/nfs.go b/test/perf/metrics/nfs.go index 6b0946342..043a4f976 100644 --- a/test/perf/metrics/nfs.go +++ b/test/perf/metrics/nfs.go @@ -21,7 +21,7 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/test/util/metrics" + "github.com/vmware-tanzu/velero/test/util/metrics" ) const NFSDesc = "NFS disk usage" diff --git a/test/perf/metrics/pod.go b/test/perf/metrics/pod.go index cedb89cdc..56572f672 100644 --- a/test/perf/metrics/pod.go +++ b/test/perf/metrics/pod.go @@ -26,7 +26,7 @@ import ( metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" - "github.com/velero-io/velero/test/util/metrics" + "github.com/vmware-tanzu/velero/test/util/metrics" ) const PodResourceDesc = "Resource consumption" diff --git a/test/perf/restore/restore.go b/test/perf/restore/restore.go index 2aedc4d48..6adbff5f4 100644 --- a/test/perf/restore/restore.go +++ b/test/perf/restore/restore.go @@ -22,10 +22,10 @@ import ( "github.com/pkg/errors" - . "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test/perf/test" - "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test/perf/test" + "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/velero" ) type RestoreTest struct { diff --git a/test/perf/test/test.go b/test/perf/test/test.go index f40165cd9..1bc8a3fc0 100644 --- a/test/perf/test/test.go +++ b/test/perf/test/test.go @@ -26,13 +26,13 @@ import ( . "github.com/onsi/gomega" "github.com/pkg/errors" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - . "github.com/velero-io/velero/test" - "github.com/velero-io/velero/test/perf/metrics" - . "github.com/velero-io/velero/test/util/k8s" - "github.com/velero-io/velero/test/util/report" - "github.com/velero-io/velero/test/util/velero" - . "github.com/velero-io/velero/test/util/velero" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + . "github.com/vmware-tanzu/velero/test" + "github.com/vmware-tanzu/velero/test/perf/metrics" + . "github.com/vmware-tanzu/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/test/util/report" + "github.com/vmware-tanzu/velero/test/util/velero" + . "github.com/vmware-tanzu/velero/test/util/velero" ) /* diff --git a/test/pkg/client/client.go b/test/pkg/client/client.go index 9ac1f1d55..331b786f2 100644 --- a/test/pkg/client/client.go +++ b/test/pkg/client/client.go @@ -24,7 +24,7 @@ import ( "k8s.io/client-go/rest" "k8s.io/client-go/tools/clientcmd" - "github.com/velero-io/velero/pkg/buildinfo" + "github.com/vmware-tanzu/velero/pkg/buildinfo" ) func buildConfigFromFlags(context, kubeconfigPath string, precedence []string) (*rest.Config, error) { diff --git a/test/pkg/client/factory.go b/test/pkg/client/factory.go index c5d089ea5..340cba587 100644 --- a/test/pkg/client/factory.go +++ b/test/pkg/client/factory.go @@ -32,8 +32,8 @@ import ( "k8s.io/client-go/rest" metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - velerov2alpha1api "github.com/velero-io/velero/pkg/apis/velero/v2alpha1" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + velerov2alpha1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v2alpha1" ) // Factory knows how to create a VeleroClient and Kubernetes client. diff --git a/test/types.go b/test/types.go index f2aa135c3..ef9582ce3 100644 --- a/test/types.go +++ b/test/types.go @@ -21,8 +21,8 @@ import ( "github.com/google/uuid" - "github.com/velero-io/velero/pkg/cmd/cli/install" - "github.com/velero-io/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + "github.com/vmware-tanzu/velero/test/util/k8s" ) // e2e-storage-class is the default StorageClass for E2E. diff --git a/test/util/csi/common.go b/test/util/csi/common.go index 0d36cb530..373bc1502 100644 --- a/test/util/csi/common.go +++ b/test/util/csi/common.go @@ -28,7 +28,7 @@ import ( "k8s.io/client-go/kubernetes" "k8s.io/client-go/tools/clientcmd" - . "github.com/velero-io/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) func GetClients() (*kubernetes.Clientset, *snapshotterClientSet.Clientset, error) { diff --git a/test/util/eks/eks.go b/test/util/eks/eks.go index 56a1d0736..f2e491c1f 100644 --- a/test/util/eks/eks.go +++ b/test/util/eks/eks.go @@ -26,7 +26,7 @@ import ( "k8s.io/apimachinery/pkg/util/wait" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func KubectlDeleteIAMServiceAcount(ctx context.Context, name, namespace, cluster string) error { diff --git a/test/util/k8s/client.go b/test/util/k8s/client.go index 5c1779f61..1018e3bdf 100644 --- a/test/util/k8s/client.go +++ b/test/util/k8s/client.go @@ -21,7 +21,7 @@ import ( metricsclientset "k8s.io/metrics/pkg/client/clientset/versioned" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/test/pkg/client" + "github.com/vmware-tanzu/velero/test/pkg/client" ) // TestClient contains different API clients that are in use throughout diff --git a/test/util/k8s/clusterrolebinding.go b/test/util/k8s/clusterrolebinding.go index 95b804304..e682c0bdc 100644 --- a/test/util/k8s/clusterrolebinding.go +++ b/test/util/k8s/clusterrolebinding.go @@ -23,7 +23,7 @@ import ( "context" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func KubectlDeleteClusterRoleBinding(ctx context.Context, name string) error { diff --git a/test/util/k8s/common.go b/test/util/k8s/common.go index 368da15b6..8869caab3 100644 --- a/test/util/k8s/common.go +++ b/test/util/k8s/common.go @@ -30,9 +30,9 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/util/wait" - "github.com/velero-io/velero/pkg/builder" - veleroexec "github.com/velero-io/velero/pkg/util/exec" - common "github.com/velero-io/velero/test/util/common" + "github.com/vmware-tanzu/velero/pkg/builder" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + common "github.com/vmware-tanzu/velero/test/util/common" ) // ensureClusterExists returns whether or not a Kubernetes cluster exists for tests to be run on. diff --git a/test/util/k8s/crd.go b/test/util/k8s/crd.go index 5d1379b64..fe17fb0ae 100644 --- a/test/util/k8s/crd.go +++ b/test/util/k8s/crd.go @@ -26,7 +26,7 @@ import ( "github.com/pkg/errors" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func InstallCRD(ctx context.Context, yaml string) error { diff --git a/test/util/k8s/deployment.go b/test/util/k8s/deployment.go index c172604ff..42e2d6ac7 100644 --- a/test/util/k8s/deployment.go +++ b/test/util/k8s/deployment.go @@ -29,8 +29,8 @@ import ( "k8s.io/apimachinery/pkg/util/wait" clientset "k8s.io/client-go/kubernetes" - "github.com/velero-io/velero/pkg/util/boolptr" - common "github.com/velero-io/velero/test/util/common" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + common "github.com/vmware-tanzu/velero/test/util/common" ) const ( diff --git a/test/util/k8s/namespace.go b/test/util/k8s/namespace.go index 59454c1a7..b46075fee 100644 --- a/test/util/k8s/namespace.go +++ b/test/util/k8s/namespace.go @@ -31,8 +31,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" waitutil "k8s.io/apimachinery/pkg/util/wait" - "github.com/velero-io/velero/pkg/builder" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/pkg/builder" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func CreateNamespace(ctx context.Context, client TestClient, namespace string) error { diff --git a/test/util/k8s/node.go b/test/util/k8s/node.go index 949c75aaf..5fd1dafc6 100644 --- a/test/util/k8s/node.go +++ b/test/util/k8s/node.go @@ -8,7 +8,7 @@ import ( "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" - common "github.com/velero-io/velero/test/util/common" + common "github.com/vmware-tanzu/velero/test/util/common" ) func GetWorkerNodes(ctx context.Context, workerOS string) ([]string, error) { diff --git a/test/util/k8s/pod.go b/test/util/k8s/pod.go index 7b8e04a83..9906e08b5 100644 --- a/test/util/k8s/pod.go +++ b/test/util/k8s/pod.go @@ -27,8 +27,8 @@ import ( metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/apimachinery/pkg/types" - "github.com/velero-io/velero/pkg/util/boolptr" - common "github.com/velero-io/velero/test/util/common" + "github.com/vmware-tanzu/velero/pkg/util/boolptr" + common "github.com/vmware-tanzu/velero/test/util/common" ) func CreatePod( diff --git a/test/util/k8s/serviceaccount.go b/test/util/k8s/serviceaccount.go index 7f6b0fa8e..31773d846 100644 --- a/test/util/k8s/serviceaccount.go +++ b/test/util/k8s/serviceaccount.go @@ -29,7 +29,7 @@ import ( "k8s.io/apimachinery/pkg/types" "k8s.io/apimachinery/pkg/util/wait" - "github.com/velero-io/velero/pkg/builder" + "github.com/vmware-tanzu/velero/pkg/builder" ) func WaitUntilServiceAccountCreated(ctx context.Context, client TestClient, namespace, serviceAccount string, timeout time.Duration) error { diff --git a/test/util/k8s/statefulset.go b/test/util/k8s/statefulset.go index 6699a731b..f0ac3a651 100644 --- a/test/util/k8s/statefulset.go +++ b/test/util/k8s/statefulset.go @@ -24,7 +24,7 @@ import ( "github.com/pkg/errors" - veleroexec "github.com/velero-io/velero/pkg/util/exec" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" ) func ScaleStatefulSet(ctx context.Context, namespace, name string, replicas int) error { diff --git a/test/util/kibishii/kibishii_utils.go b/test/util/kibishii/kibishii_utils.go index 175938438..5948a2c7b 100644 --- a/test/util/kibishii/kibishii_utils.go +++ b/test/util/kibishii/kibishii_utils.go @@ -35,12 +35,12 @@ import ( "k8s.io/apimachinery/pkg/util/wait" "sigs.k8s.io/yaml" - veleroexec "github.com/velero-io/velero/pkg/util/exec" - . "github.com/velero-io/velero/test" - "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" - . "github.com/velero-io/velero/test/util/providers" - . "github.com/velero-io/velero/test/util/velero" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + . "github.com/vmware-tanzu/velero/test" + "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" + . "github.com/vmware-tanzu/velero/test/util/providers" + . "github.com/vmware-tanzu/velero/test/util/velero" ) const ( diff --git a/test/util/metrics/minio.go b/test/util/metrics/minio.go index 1f0dc44cd..163212713 100644 --- a/test/util/metrics/minio.go +++ b/test/util/metrics/minio.go @@ -19,7 +19,7 @@ package metrics import ( "github.com/pkg/errors" - "github.com/velero-io/velero/test/util/providers" + "github.com/vmware-tanzu/velero/test/util/providers" ) func GetMinioDiskUsage(cloudCredentialsFile string, bslBucket string, bslPrefix string, bslConfig string) (int64, error) { diff --git a/test/util/providers/aws_utils.go b/test/util/providers/aws_utils.go index 7750749f8..7b8916cef 100644 --- a/test/util/providers/aws_utils.go +++ b/test/util/providers/aws_utils.go @@ -38,8 +38,8 @@ import ( s3types "github.com/aws/aws-sdk-go-v2/service/s3/types" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/cmd/util/flag" - "github.com/velero-io/velero/test" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + "github.com/vmware-tanzu/velero/test" ) type AWSStorage string diff --git a/test/util/providers/azure_utils.go b/test/util/providers/azure_utils.go index 79375ec8e..468dbfe40 100644 --- a/test/util/providers/azure_utils.go +++ b/test/util/providers/azure_utils.go @@ -39,8 +39,8 @@ import ( "github.com/joho/godotenv" "github.com/pkg/errors" - "github.com/velero-io/velero/pkg/cmd/util/flag" - . "github.com/velero-io/velero/test" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + . "github.com/vmware-tanzu/velero/test" ) type AzureStorage string diff --git a/test/util/providers/common.go b/test/util/providers/common.go index 2e915c460..a7c68dc37 100644 --- a/test/util/providers/common.go +++ b/test/util/providers/common.go @@ -27,9 +27,9 @@ import ( "github.com/pkg/errors" - "github.com/velero-io/velero/internal/volume" - velerotest "github.com/velero-io/velero/test" - velero "github.com/velero-io/velero/test/util/velero" + "github.com/vmware-tanzu/velero/internal/volume" + velerotest "github.com/vmware-tanzu/velero/test" + velero "github.com/vmware-tanzu/velero/test/util/velero" ) type ObjectsInStorage interface { diff --git a/test/util/providers/gcloud_utils.go b/test/util/providers/gcloud_utils.go index 571a6f3d9..022d92ff2 100644 --- a/test/util/providers/gcloud_utils.go +++ b/test/util/providers/gcloud_utils.go @@ -32,7 +32,7 @@ import ( "google.golang.org/api/iterator" "google.golang.org/api/option" - "github.com/velero-io/velero/test" + "github.com/vmware-tanzu/velero/test" ) type GCSStorage string diff --git a/test/util/report/report.go b/test/util/report/report.go index 04bc6a209..6d5955392 100644 --- a/test/util/report/report.go +++ b/test/util/report/report.go @@ -22,7 +22,7 @@ import ( "github.com/pkg/errors" "gopkg.in/yaml.v3" - "github.com/velero-io/velero/test" + "github.com/vmware-tanzu/velero/test" ) func GenerateYamlReport() error { diff --git a/test/util/velero/install.go b/test/util/velero/install.go index 02eacf28c..e2c57392e 100644 --- a/test/util/velero/install.go +++ b/test/util/velero/install.go @@ -39,13 +39,13 @@ import ( clientset "k8s.io/client-go/kubernetes" "sigs.k8s.io/controller-runtime/pkg/client" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/cmd/cli/install" - velerexec "github.com/velero-io/velero/pkg/util/exec" - "github.com/velero-io/velero/test" - common "github.com/velero-io/velero/test/util/common" - eksutil "github.com/velero-io/velero/test/util/eks" - "github.com/velero-io/velero/test/util/k8s" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + velerexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/test" + common "github.com/vmware-tanzu/velero/test/util/common" + eksutil "github.com/vmware-tanzu/velero/test/util/eks" + "github.com/vmware-tanzu/velero/test/util/k8s" ) // we provide more install options other than the standard install.InstallOptions in E2E test @@ -222,7 +222,7 @@ func VeleroInstall(ctx context.Context, veleroCfg *test.VeleroConfig, isStandbyC } // generateVSpherePlugin refers to -// https://github.com/velero-io/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md +// https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md func generateVSpherePlugin(veleroCfg *test.VeleroConfig) error { cli := veleroCfg.ClientToInstallVelero @@ -927,7 +927,7 @@ func VeleroUninstall(ctx context.Context, veleroCfg test.VeleroConfig) error { } // createVCCredentialSecret refer to -// https://github.com/velero-io/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md +// https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/v1.3.0/docs/vanilla.md func createVCCredentialSecret(c clientset.Interface, veleroNamespace string) error { secret, err := getVCCredentialSecret(c) if err != nil { @@ -970,7 +970,7 @@ func createVCCredentialSecret(c clientset.Interface, veleroNamespace string) err return nil } -// Reference https://github.com/velero-io/velero-plugin-for-vsphere/blob/main/docs/vanilla.md#create-vc-credential-secret +// Reference https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/main/docs/vanilla.md#create-vc-credential-secret // Read secret from kube-system namespace first, if not found, try with vmware-system-csi. func getVCCredentialSecret(c clientset.Interface) (secret *corev1api.Secret, err error) { secret, err = k8s.GetSecret(c, test.KubeSystemNamespace, "vsphere-config-secret") diff --git a/test/util/velero/velero_utils.go b/test/util/velero/velero_utils.go index dc1ddc4a8..5c9b39a84 100644 --- a/test/util/velero/velero_utils.go +++ b/test/util/velero/velero_utils.go @@ -45,16 +45,16 @@ import ( "k8s.io/apimachinery/pkg/util/wait" kbclient "sigs.k8s.io/controller-runtime/pkg/client" - "github.com/velero-io/velero/internal/volume" - velerov1api "github.com/velero-io/velero/pkg/apis/velero/v1" - "github.com/velero-io/velero/pkg/builder" - cliinstall "github.com/velero-io/velero/pkg/cmd/cli/install" - "github.com/velero-io/velero/pkg/cmd/util/flag" - veleroexec "github.com/velero-io/velero/pkg/util/exec" - "github.com/velero-io/velero/test" - . "github.com/velero-io/velero/test" - common "github.com/velero-io/velero/test/util/common" - . "github.com/velero-io/velero/test/util/k8s" + "github.com/vmware-tanzu/velero/internal/volume" + velerov1api "github.com/vmware-tanzu/velero/pkg/apis/velero/v1" + "github.com/vmware-tanzu/velero/pkg/builder" + cliinstall "github.com/vmware-tanzu/velero/pkg/cmd/cli/install" + "github.com/vmware-tanzu/velero/pkg/cmd/util/flag" + veleroexec "github.com/vmware-tanzu/velero/pkg/util/exec" + "github.com/vmware-tanzu/velero/test" + . "github.com/vmware-tanzu/velero/test" + common "github.com/vmware-tanzu/velero/test/util/common" + . "github.com/vmware-tanzu/velero/test/util/k8s" ) const BackupObjectsPrefix = "backups" @@ -477,7 +477,7 @@ func VeleroBackupNamespace(ctx context.Context, veleroCLI, veleroNamespace strin args = append(args, "--default-volumes-to-fs-backup") } - // To workaround https://github.com/velero-io/velero-plugin-for-vsphere/issues/347 for vsphere plugin v1.1.1 + // To workaround https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/347 for vsphere plugin v1.1.1 // if the "--snapshot-volumes=false" isn't specified explicitly, the vSphere plugin will always take snapshots // for the volumes even though the "--default-volumes-to-fs-backup" is specified // TODO This can be removed if the logic of vSphere plugin bump up to 1.3 @@ -946,7 +946,7 @@ func InstallVeleroCLI(ctx context.Context, version string) (string, error) { postfix := ".tar.gz" tarball := name + postfix err := wait.PollUntilContextTimeout(ctx, time.Second*5, time.Minute*5, true, func(ctx context.Context) (bool, error) { - tempFile, err := getVeleroCliTarball("https://github.com/velero-io/velero/releases/download/" + version + "/" + tarball) + tempFile, err := getVeleroCliTarball("https://github.com/vmware-tanzu/velero/releases/download/" + version + "/" + tarball) if err != nil { return false, errors.WithMessagef(err, "failed to get Velero CLI tarball") } From 9552f9f656457ca99f195a245c43c88a81aca930 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 25 May 2026 05:50:35 +0000 Subject: [PATCH 6/6] docs: keep velero-plugin-for-csi on vmware-tanzu links Agent-Logs-Url: https://github.com/velero-io/velero/sessions/bb5e2fbb-ec32-48df-b2f8-fa893972fadb Co-authored-by: blackpiglet <59276555+blackpiglet@users.noreply.github.com> --- site/content/docs/main/csi-snapshot-data-movement.md | 2 +- site/content/docs/main/csi.md | 2 +- site/content/docs/v1.10/csi.md | 4 ++-- site/content/docs/v1.10/supported-providers.md | 2 +- site/content/docs/v1.11/csi.md | 4 ++-- site/content/docs/v1.11/supported-providers.md | 2 +- site/content/docs/v1.12/csi.md | 4 ++-- site/content/docs/v1.12/supported-providers.md | 2 +- site/content/docs/v1.13/csi.md | 4 ++-- site/content/docs/v1.13/supported-providers.md | 2 +- site/content/docs/v1.14/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.14/csi.md | 2 +- site/content/docs/v1.15/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.15/csi.md | 2 +- site/content/docs/v1.16/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.16/csi.md | 2 +- site/content/docs/v1.17/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.17/csi.md | 2 +- site/content/docs/v1.18/csi-snapshot-data-movement.md | 2 +- site/content/docs/v1.18/csi.md | 2 +- site/content/docs/v1.3.0/csi.md | 2 +- site/content/docs/v1.3.1/csi.md | 2 +- site/content/docs/v1.3.2/csi.md | 6 +++--- site/content/docs/v1.4/csi.md | 4 ++-- site/content/docs/v1.4/supported-providers.md | 2 +- site/content/docs/v1.5/csi.md | 2 +- site/content/docs/v1.5/supported-providers.md | 2 +- site/content/docs/v1.6/csi.md | 2 +- site/content/docs/v1.6/supported-providers.md | 2 +- site/content/docs/v1.7/csi.md | 2 +- site/content/docs/v1.7/supported-providers.md | 2 +- site/content/docs/v1.8/csi.md | 2 +- site/content/docs/v1.8/supported-providers.md | 2 +- site/content/docs/v1.9/csi.md | 4 ++-- site/content/docs/v1.9/supported-providers.md | 2 +- site/content/plugins/list/10-container-storage-interface.md | 2 +- site/content/posts/2020-05-26-Velero-1.4-Community-Wave.md | 6 +++--- site/content/posts/2020-05-27-CSI-integration.md | 4 ++-- .../posts/2020-09-16-Velero-1.5-For-And-By-Community.md | 2 +- 39 files changed, 50 insertions(+), 50 deletions(-) diff --git a/site/content/docs/main/csi-snapshot-data-movement.md b/site/content/docs/main/csi-snapshot-data-movement.md index 378f99055..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/main/csi.md b/site/content/docs/main/csi.md index 11973f50a..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.10/csi.md b/site/content/docs/v1.10/csi.md index 67518359a..d8c3c5eff 100644 --- a/site/content/docs/v1.10/csi.md +++ b/site/content/docs/v1.10/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). ## Prerequisites @@ -71,5 +71,5 @@ For more details on how each plugin works, see the [CSI plugin repo][2]'s docume **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/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.10/supported-providers.md b/site/content/docs/v1.10/supported-providers.md index e1837fb7d..164544d59 100644 --- a/site/content/docs/v1.10/supported-providers.md +++ b/site/content/docs/v1.10/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.11/csi.md b/site/content/docs/v1.11/csi.md index d10d52570..bfeb68d4e 100644 --- a/site/content/docs/v1.11/csi.md +++ b/site/content/docs/v1.11/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). ## Prerequisites @@ -73,5 +73,5 @@ For more details on how each plugin works, see the [CSI plugin repo][2]'s docume **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/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.11/supported-providers.md b/site/content/docs/v1.11/supported-providers.md index e1837fb7d..164544d59 100644 --- a/site/content/docs/v1.11/supported-providers.md +++ b/site/content/docs/v1.11/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.12/csi.md b/site/content/docs/v1.12/csi.md index 1654626f4..57ecffc7a 100644 --- a/site/content/docs/v1.12/csi.md +++ b/site/content/docs/v1.12/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). ## Prerequisites @@ -115,5 +115,5 @@ For more details on how each plugin works, see the [CSI plugin repo][2]'s docume **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/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.12/supported-providers.md b/site/content/docs/v1.12/supported-providers.md index e1837fb7d..164544d59 100644 --- a/site/content/docs/v1.12/supported-providers.md +++ b/site/content/docs/v1.12/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.13/csi.md b/site/content/docs/v1.13/csi.md index 23ccb29fc..d09eacb59 100644 --- a/site/content/docs/v1.13/csi.md +++ b/site/content/docs/v1.13/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). ## Prerequisites @@ -115,5 +115,5 @@ For more details on how each plugin works, see the [CSI plugin repo][2]'s docume **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/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.13/supported-providers.md b/site/content/docs/v1.13/supported-providers.md index e1837fb7d..164544d59 100644 --- a/site/content/docs/v1.13/supported-providers.md +++ b/site/content/docs/v1.13/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | +| [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/velero-io/velero/issues) 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 a9efe4fb7..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.14/csi.md b/site/content/docs/v1.14/csi.md index 4ec75a9c1..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. 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 f336caba7..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.15/csi.md b/site/content/docs/v1.15/csi.md index 4ec75a9c1..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. 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 68bf56b2a..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.16/csi.md b/site/content/docs/v1.16/csi.md index 33fe1ef70..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. 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 6c916e0e1..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.17/csi.md b/site/content/docs/v1.17/csi.md index 11973f50a..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. 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 378f99055..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.18/csi.md b/site/content/docs/v1.18/csi.md index 11973f50a..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/velero-io/velero-plugin-for-csi` repository, which is the Velero CSI plugin, is merged into the `github.com/velero-io/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. diff --git a/site/content/docs/v1.3.0/csi.md b/site/content/docs/v1.3.0/csi.md index 99d11daf5..a8f272a32 100644 --- a/site/content/docs/v1.3.0/csi.md +++ b/site/content/docs/v1.3.0/csi.md @@ -10,7 +10,7 @@ Velero supports taking Container Storage Interface (CSI) snapshots as a beta fea 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster should be the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Roadmap diff --git a/site/content/docs/v1.3.1/csi.md b/site/content/docs/v1.3.1/csi.md index 99d11daf5..a8f272a32 100644 --- a/site/content/docs/v1.3.1/csi.md +++ b/site/content/docs/v1.3.1/csi.md @@ -10,7 +10,7 @@ Velero supports taking Container Storage Interface (CSI) snapshots as a beta fea 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster should be the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Roadmap diff --git a/site/content/docs/v1.3.2/csi.md b/site/content/docs/v1.3.2/csi.md index 535c36008..388fbc368 100644 --- a/site/content/docs/v1.3.2/csi.md +++ b/site/content/docs/v1.3.2/csi.md @@ -12,19 +12,19 @@ The following are the prerequisites for using Velero to take Container Storage I 1. The cluster is Kubernetes version 1.17 or greater. 1. The cluster is running a CSI driver capable of support volume snapshots at the [v1beta1 API level](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/). 1. The Velero server is running with the `--features EnableCSI` feature flag to enable CSI logic in Velero's core. - 1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. + 1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) is installed to integrate with the CSI volume snapshot APIs. 1. When restoring CSI volumesnapshots across clusters, the name of the CSI driver in the destination cluster is the same as that on the source cluster to ensure cross cluster portability of CSI volumesnapshots # Implementation Choices -This section documents some of the choices made during implementation of the Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/): +This section documents some of the choices made during implementation of the Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/): 1. Volumesnapshots created by the plugin will be retained only for the lifetime of the backup even if the `DeletionPolicy` on the volumesnapshotclass is set to `Retain`. To accomplish this, during deletion of the backup the prior to deleting the volumesnapshot, volumesnapshotcontent object will be patched to set its `DeletionPolicy` to `Delete`. Thus deleting volumesnapshot object will result in cascade delete of the volumesnapshotcontent and the snapshot in the storage provider. 1. Volumesnapshotcontent objects created during a velero backup that are dangling, unbound to a volumesnapshot object, will also be discovered, through labels, and deleted on backup deletion. # Known Limitations -1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/velero-io/velero-plugin-for-csi/issues/17)_ +1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/vmware-tanzu/velero-plugin-for-csi/issues/17)_ # Roadmap diff --git a/site/content/docs/v1.4/csi.md b/site/content/docs/v1.4/csi.md index 52a8c8dc3..147f4b581 100644 --- a/site/content/docs/v1.4/csi.md +++ b/site/content/docs/v1.4/csi.md @@ -43,7 +43,7 @@ This section documents some of the choices made during implementation of the Vel ## Known Limitations -1. The Velero [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/velero-io/velero-plugin-for-csi/issues/17)_ +1. The Velero [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/), to backup CSI backed PVCs, will choose the first VolumeSnapshotClass in the cluster that has the same driver name. _[Issue #17](https://github.com/vmware-tanzu/velero-plugin-for-csi/issues/17)_ ## Roadmap @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.4/supported-providers.md b/site/content/docs/v1.4/supported-providers.md index 862a034f3..9904b4bf5 100644 --- a/site/content/docs/v1.4/supported-providers.md +++ b/site/content/docs/v1.4/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.5/csi.md b/site/content/docs/v1.5/csi.md index 1f30a07ee..49f4f77e9 100644 --- a/site/content/docs/v1.5/csi.md +++ b/site/content/docs/v1.5/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.5/supported-providers.md b/site/content/docs/v1.5/supported-providers.md index 82daa0a15..466551c77 100644 --- a/site/content/docs/v1.5/supported-providers.md +++ b/site/content/docs/v1.5/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/)| 🚫 | CSI Volumes | [Velero plugin for CSI](https://github.com/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.6/csi.md b/site/content/docs/v1.6/csi.md index 1f30a07ee..49f4f77e9 100644 --- a/site/content/docs/v1.6/csi.md +++ b/site/content/docs/v1.6/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.6/supported-providers.md b/site/content/docs/v1.6/supported-providers.md index 10ad404dc..35b237fbe 100644 --- a/site/content/docs/v1.6/supported-providers.md +++ b/site/content/docs/v1.6/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.7/csi.md b/site/content/docs/v1.7/csi.md index 5c8a1f848..99365e719 100644 --- a/site/content/docs/v1.7/csi.md +++ b/site/content/docs/v1.7/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.7/supported-providers.md b/site/content/docs/v1.7/supported-providers.md index 122ecbd7b..3acb2752f 100644 --- a/site/content/docs/v1.7/supported-providers.md +++ b/site/content/docs/v1.7/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.8/csi.md b/site/content/docs/v1.8/csi.md index 5c8a1f848..99365e719 100644 --- a/site/content/docs/v1.8/csi.md +++ b/site/content/docs/v1.8/csi.md @@ -73,5 +73,5 @@ 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. [1]: customize-installation.md#enable-server-side-features -[2]: https://github.com/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.8/supported-providers.md b/site/content/docs/v1.8/supported-providers.md index 10ad404dc..35b237fbe 100644 --- a/site/content/docs/v1.8/supported-providers.md +++ b/site/content/docs/v1.8/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | +| [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/velero-io/velero/issues) diff --git a/site/content/docs/v1.9/csi.md b/site/content/docs/v1.9/csi.md index 46363e564..aa41bee7b 100644 --- a/site/content/docs/v1.9/csi.md +++ b/site/content/docs/v1.9/csi.md @@ -5,7 +5,7 @@ layout: docs Integrating Container Storage Interface (CSI) snapshot support into Velero enables Velero to backup and restore CSI-backed volumes using the [Kubernetes CSI Snapshot APIs](https://kubernetes.io/docs/concepts/storage/volume-snapshots/). -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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/velero-io/velero-plugin-for-csi/). +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 through CSI plugins. For more information about specific components, see the [plugin repo](https://github.com/vmware-tanzu/velero-plugin-for-csi/). ## Prerequisites @@ -71,5 +71,5 @@ For more details on how each plugin works, see the [CSI plugin repo][2]'s docume **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/velero-io/velero-plugin-for-csi/ +[2]: https://github.com/vmware-tanzu/velero-plugin-for-csi/ [3]: https://hub.docker.com/repository/docker/velero/velero-plugin-for-csi diff --git a/site/content/docs/v1.9/supported-providers.md b/site/content/docs/v1.9/supported-providers.md index a45bf70ef..c8ebc0edc 100644 --- a/site/content/docs/v1.9/supported-providers.md +++ b/site/content/docs/v1.9/supported-providers.md @@ -15,7 +15,7 @@ Velero supports a variety of storage providers for different backup and snapshot | [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/velero-io/velero-plugin-for-csi/) | [CSI Plugin Setup](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) | 🚫 | +| [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/velero-io/velero/issues) diff --git a/site/content/plugins/list/10-container-storage-interface.md b/site/content/plugins/list/10-container-storage-interface.md index 8649a947f..21ed41db7 100644 --- a/site/content/plugins/list/10-container-storage-interface.md +++ b/site/content/plugins/list/10-container-storage-interface.md @@ -1,6 +1,6 @@ --- title: Container Storage Interface (CSI) -link: https://github.com/velero-io/velero-plugin-for-csi +link: https://github.com/vmware-tanzu/velero-plugin-for-csi objectStorage: false volumesnapshotter: true localStorage: true 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 a4c3f067f..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 @@ -16,7 +16,7 @@ Velero v1.4.0 now extends Velero’s support for snapshotting beyond Velero’s The [Container Storage Interface](https://github.com/container-storage-interface/spec) (CSI) is a way for container orchestrators such as Kubernetes to provide a standard interface for storage systems, without having to create drivers for each orchestration system. While basic attach and detach volume operations are generally available in Kubernetes, the volume snapshotting APIs are still in beta. The Velero team is working with the Data Protection Working Group to ensure that the CSI snapshotting API specification is useful to end users and tool builders. We intend to trail behind the official Kubernetes support for the feature, entering general availability sometime after the feature is GA in Kubernetes itself. -Activating and using the CSI support in Velero will require enabling the `EnableCSI` feature flag and installing the [CSI plugin](https://github.com/velero-io/velero-plugin-for-csi/) alongside the Velero server. For full details on installing and using the feature, see our [CSI beta page](https://velero.io/docs/csi/). +Activating and using the CSI support in Velero will require enabling the `EnableCSI` feature flag and installing the [CSI plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi/) alongside the Velero server. For full details on installing and using the feature, see our [CSI beta page](https://velero.io/docs/csi/). As a very brief example of the seamless integration of CSI into Velero. We will back up and restore a sample workload in the `csi-app` namespace that is using volumes backed by the CSI hostpath plugin driver. Installing and configuring the driver is outside the scope of this blog post, but we will cover the complete example in the future. @@ -30,7 +30,7 @@ Waiting for backup to complete. You may safely press ctrl-c to stop waiting - yo Backup completed with status: Completed. You may check for more information using the commands `velero backup describe csi-b1` and `velero backup logs csi-b1`. ``` -Velero will detect the use of CSI volumes and invoke [BackupItemAction](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create the CSI VolumeSnapshot and VolumesnapshotContents as part of the backup. +Velero will detect the use of CSI volumes and invoke [BackupItemAction](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create the CSI VolumeSnapshot and VolumesnapshotContents as part of the backup. ``` $ kubectl -n csi-app get volumesnapshot,volumesnapshotcontent -lvelero.io/backup-name=csi-b1 -oname @@ -48,7 +48,7 @@ Waiting for restore to complete. You may safely press ctrl-c to stop waiting - y Restore completed with status: Completed. You may check for more information using the commands `velero restore describe csi-b1-20200515112009` and `velero restore logs csi-b1-20200515112009`. ``` -Velero will detect the CSI Snapshot API objects and invoke the [RestoreItemAction](https://github.com/velero-io/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create CSI VolumeSnapshotContent and statically bind to the VolumeSnapshot created during backup. +Velero will detect the CSI Snapshot API objects and invoke the [RestoreItemAction](https://github.com/vmware-tanzu/velero-plugin-for-csi#kinds-of-plugins-included) plugins that create CSI VolumeSnapshotContent and statically bind to the VolumeSnapshot created during backup. ``` $ kubectl -n csi-app get volumesnapshot,volumesnapshotcontent -lvelero.io/restore-name=csi-b1-20200515112009 -oname diff --git a/site/content/posts/2020-05-27-CSI-integration.md b/site/content/posts/2020-05-27-CSI-integration.md index 12337f33c..f5e308a42 100644 --- a/site/content/posts/2020-05-27-CSI-integration.md +++ b/site/content/posts/2020-05-27-CSI-integration.md @@ -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/velero-io/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. +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 @@ -199,4 +199,4 @@ More details about CSI volume snapshotting and its support in Velero may be foun - [Kubernetes 1.17 Feature: Kubernetes Volume Snapshot Moves to Beta](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/) for more information on the CSI beta snapshot APIs. - Prerequisites to use this feature is available [on our website](https://velero.io/docs/csi). - [Kubernetes CSI docs](https://kubernetes-csi.github.io/docs/sidecar-containers.html): To understand components in a CSI environment -- [Velero plugin for CSI snapshots](https://github.com/velero-io/velero-plugin-for-csi) for implementation details of the CSI plugin. +- [Velero plugin for CSI snapshots](https://github.com/vmware-tanzu/velero-plugin-for-csi) for implementation details of the CSI plugin. 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 cdf41c4ce..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 @@ -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/velero-io/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). +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