vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
velero/test/testdata/storage-class
History
Xun Jiang e5354e123b Modify the StorageClass install and delete code. 
* Only install and uninstall SC and VSC once for default cluster.
* Install and uninstall SC and VSC for standby cluster on migration case.
* Refactor the StorageClass and VolumeSnapshotClass YAMLs.
* Prettify the e2e_suite_test.go

Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>
 		2024-11-19 11:10:50 +08:00
..
README.md Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
aws-legecy.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
aws.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
azure-legacy.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
azure.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
gcp-legacy.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
gcp.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
kind.yaml Set `GOBIN` so Makefile don't modify $PATH on `go install` Fix realPath resolving when cloud credentials is prefixed by `~` for home dir Use `~/.docker/config.json` if REGISTRY_CREDENTIAL_FILE not defined and skip step if does not exists since it is optional 2024-02-04 22:17:37 -05:00
vanilla-zfs.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
vsphere-legacy.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00
vsphere.yaml Modify the StorageClass install and delete code. 2024-11-19 11:10:50 +08:00

README.md

The test/testdata/storage-class directory contains the StorageClass YAMLs used for E2E. The public cloud provider (including AWS, Azure and GCP) has two StorageClasses.

  • The provider-name.yaml contains the default StorageClass for the provider. It uses the CSI provisioner.
  • The provider-name-legacy.yaml contains the legacy StorageClass for the provider. It uses the in-tree volume plugin as the provisioner. By far, there is no E2E case using them.

The vSphere environment also has two StorageClass files.

  • The vsphere-legacy.yaml is used for the TKGm environment.
  • The vsphere.yaml is used for the VKS environment.

The ZFS StorageClasses only have the default one. There is no in-tree volume plugin used StorageClass used in E2E.

The kind StorageClass uses the local-path provisioner. Will consider adding the CSI provisioner when there is a need.