mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-04-23 17:20:38 +00:00
e5354e123b
* 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>
13 lines
876 B
Markdown
13 lines
876 B
Markdown
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.
|