e2e/

directory
v1.14.0-rc.3 Latest Latest
Warning

This package is not in the latest version of its module.

 Go to latest Published: Jun 13, 2024 License: Apache-2.0

README

End-to-end tests

Document for running Velero end-to-end test suite.

The E2E tests are validating end-to-end behavior of Velero including install, backup and restore operations. These tests take longer to complete and is not expected to be part of day-to-day developer workflow. It is for this reason that they are disabled when running unit tests. This is accomplished by running unit tests in short mode using the -short flag to go test.

If you previously ran unit tests using the go test ./... command or any of its variations, then you will now run the same command with the -short flag to go test to accomplish the same behavior. Alternatively, you can use the make test command to run unit tests.

Prerequisites

Running the E2E tests expects:

  1. One or two running Kubernetes clusters, migration scenario needs 2 clusters:

    1. With DNS and CNI installed.
    2. Compatible with Velero- running Kubernetes v1.10 or later.
    3. With necessary storage drivers/provisioners installed.

  2. kubectl installed locally.

Note for migration scenario

Default Cluster refers to source cluster to backup from. Whereas Standby Cluster refers to destination cluster to restore to.

Limitations

These are the current set of limitations with the E2E tests.

  1. E2E tests only accepts credentials only for a single provider and for that reason, only tests for a single provider can be run at a time.
  2. To avoid debugging or coding effort, we only have one test suite for Velero E2E test, and run in random order as ginkgo default behavior.
  3. Flag -install-velero is for purpose of having tests on an existed Velero instance, but by default -install-velero is set to true, because it's mandatory for some of cases to testing on specific version of Velero, such as upgrade and migration tests. In upgrade tests, we must install a specific old version and then upgrade it to the target version, multiple installations is involved here, also migration tests have the same situation with upgrade tests, therefore if you're going to test against an existed Velero instance, make sure to skip upgrade and migration tests from a single E2E test execution.
  4. To improve E2E test execution efficiency, E2E tests will skip re-installation between test cases except for those which need a fresh Velero installation like upgrade , migration and some other test cases. When starting a E2E test execution which setting flag -install-velero with the default value(true), there will be a Velero installation at the beginning, then test cases will be run in random order, and test cases behavior is as below:
    1. If the scheduled test case is upgrade (or other cases needs a fresh Velero installation), then upgrade test will uninstall the current Velero instance at the beginning and uninstall the tested Velero instance in the end to avoid unexpected installation parameters for the following test cases.
    2. If the scheduled test case is the normal one, it will check the existence of Velero instance, if no one there then start a new standard instaillation, otherwise proceeding test steps.

Configuration for E2E tests

Below is a list of the configuration used by E2E tests. These configuration parameters are expected as values to the following command line flags:

  1. -credentials-file: File containing credentials for backup and volume provider. Required.
  2. -bucket: Name of the object storage bucket where backups from e2e tests should be stored. Required.
  3. -cloud-provider: The cloud the tests will be run in. Appropriate plugins will be installed except for kind which requires the object-store-provider to be specified.
  4. -object-store-provider: Object store provider to use. Required when kind is the cloud provider.
  5. -velerocli: Path to the velero application to use. Optional, by default uses velero in the $PATH
  6. -velero-image: Image for the velero server to be tested. Optional, by default uses velero/velero:main
  7. -restore-helper-image: Image for the velero restore helper to be tested. Optional, by default it is the built-in image address of velero image.
  8. -plugins : Provider plugins to be tested.
  9. -bsl-config: Configuration to use for the backup storage location. Format is key1=value1,key2=value2. Optional.
  10. -prefix: Prefix in the bucket, under which all Velero data should be stored within the bucket. Optional.
  11. -vsl-config: Configuration to use for the volume snapshot location. Format is key1=value1,key2=value2. Optional.
  12. -velero-namespace: Namespace to install velero in. Optional, defaults to "velero".
  13. -install-velero: Specifies whether to install/uninstall velero for the tests. Optional, defaults to "true".
  14. -use-node-agent: Whether deploy node agent daemonset velero during the test. Optional.
  15. -use-volume-snapshots: Whether or not to create snapshot location automatically. Set to false if you do not plan to create volume snapshots via a storage provider.
  16. -additional-bsl-plugins: Additional plugins to be tested.
  17. -additional-bsl-object-store-provider: Provider of object store plugin for additional backup storage location. Required if testing multiple credentials support.
  18. -additional-bsl-bucket: Name of the object storage bucket for additional backup storage location. Required if testing multiple credentials support.
  19. -additional-bsl-prefix: Prefix in the additional-bsl-bucket, under which all Velero data should be stored. Optional.
  20. -additional-bsl-config: Configuration to use for the additional backup storage location. Format is key1=value1,key2=value2. Optional.
  21. -additional-bsl-credentials-file: File containing credentials for the additional backup storage location. Required if testing multiple credentials support.
  22. -velero-version: Image version for the velero server to be tested with. It's set for upgrade test to verify Velero image version is installed as expected. Required if upgrade test is included in the test.
  23. -upgrade-from-velero-version: Comma-separated list of Velero version to be tested with for the pre-upgrade velero server.
  24. -upgrade-from-velero-cli: Comma-separated list of velero application for the pre-upgrade velero server.
  25. -migrate-from-velero-version: Comma-separated list of Velero version to be tested with on source cluster.
  26. -migrate-from-velero-cli: Comma-separated list of velero application on source cluster.
  27. -features: Comma-separated list of features to enable for this Velero process.
  28. -registry-credential-file: File containing credential for the image registry, follows the same format rules as the ~/.docker/config.json file. This credential will be loaded in Velero server pod to help on Docker Hub rate limit issue.
  29. -kibishii-directory: The file directory or URL path to install Kibishii. It's configurable in case the default path is not accessible for your own test environment.
  30. -debug-e2e-test: <true/false> A Switch for enable or disable test data cleaning action.
  31. -garbage-collection-frequency: frequency of garbage collection. It is a parameter for Velero installation. Optional.
  32. -velero-server-debug-mode: A switch for enable or disable having debug log of Velero server.
  33. -default-cluster-context: Default (source) cluster's kube config context, it's for migration test.
  34. -standby-cluster-context: Standby (destination) cluster's kube config context, it's for migration test.
  35. -uploader-type: Type of uploader for persistent volume backup.
  36. -snapshot-move-data: A Switch for taking backup with Velero's data mover, if data-mover-plugin is not provided, using built-in plugin.
  37. -data-mover-plugin: Customized plugin for data mover.
  38. -standby-cluster-cloud-provider: Cloud provider for standby cluster.
  39. -standby-cluster-plugins: Plugins provider for standby cluster.
  40. -standby-cluster-object-store-provider: Object store provider for standby cluster.
  41. -debug-velero-pod-restart: A switch for debugging velero pod restart.

These configurations or parameters are used to generate install options for Velero for each test suite.

Tests can be run with the Kubernetes cluster hosted in various cloud providers or in a kind cluster with storage in a specified object store type. Currently supported cloud provider types are aws, azure, vsphere and kind.

Running tests locally

Running using make

E2E tests can be run from the Velero repository root by running make test-e2e. While running E2E tests using make the E2E test configuration values are passed using make variables.

Below is a mapping between make variables to E2E configuration flags.

  1. CREDS_FILE: -credentials-file. Required.
  2. BSL_BUCKET: -bucket. Required.
  3. CLOUD_PROVIDER: -cloud-provider. Required
  4. OBJECT_STORE_PROVIDER: -object-store-provider. Required when kind is the cloud provider.
  5. VELERO_CLI: the -velerocli. Optional.
  6. VELERO_IMAGE: the -velero-image. Optional.
  7. RESTORE_HELPER_IMAGE : the -restore-helper-image. Optional.
  8. VERSION : the -velero-version. Optional.
  9. VELERO_NAMESPACE : the -velero-namespace. Optional.
  10. PLUGINS : the -plugins. Optional.
  11. BSL_PREFIX: -prefix. Optional.
  12. BSL_CONFIG: -bsl-config. Optional. Example: BSL_CONFIG="region=us-east-1". May be required for some object store provider
  13. VSL_CONFIG: -vsl-config. Optional.
  14. UPGRADE_FROM_VELERO_CLI : -upgrade-from-velero-cli. Optional.
  15. UPGRADE_FROM_VELERO_VERSION : -upgrade-from-velero-version. Optional.
  16. MIGRATE_FROM_VELERO_CLI : -migrate-from-velero-cli. Optional.
  17. MIGRATE_FROM_VELERO_VERSION : -migrate-from-velero-version. Optional.
  18. ADDITIONAL_BSL_PLUGINS : -additional-bsl-plugins. Optional.
  19. ADDITIONAL_OBJECT_STORE_PROVIDER: -additional-bsl-object-store-provider. Optional.
  20. ADDITIONAL_CREDS_FILE: -additional-bsl-bucket. Optional.
  21. ADDITIONAL_BSL_BUCKET: -additional-bsl-prefix. Optional.
  22. ADDITIONAL_BSL_PREFIX: -additional-bsl-config. Optional.
  23. ADDITIONAL_BSL_CONFIG: -additional-bsl-credentials-file. Optional.
  24. FEATURES: -features. Optional.
  25. REGISTRY_CREDENTIAL_FILE: -registry-credential-file. Optional.
  26. KIBISHII_DIRECTORY: -kibishii-directory. Optional.
  27. DEBUG_E2E_TEST: -debug-e2e-test. Optional.
  28. VELERO_SERVER_DEBUG_MODE: -velero-server-debug-mode. Optional.
  29. DEFAULT_CLUSTER: -default-cluster-context. Optional.
  30. STANDBY_CLUSTER: -standby-cluster-context. Optional.
  31. UPLOADER_TYPE: -uploader-type. Optional.
  32. SNAPSHOT_MOVE_DATA: -snapshot-move-data. Optional.
  33. DATA_MOVER_plugin: -data-mover-plugin. Optional.
  34. STANDBY_CLUSTER_CLOUD_PROVIDER: -standby-cluster-cloud-provider. Optional.
  35. STANDBY_CLUSTER_PLUGINS: -dstandby-cluster-plugins. Optional.
  36. STANDBY_CLUSTER_OBJECT_STORE_PROVIDER: -standby-cluster-object-store-provider. Optional.
  37. INSTALL_VELERO : -install-velero. Optional.
  38. DEBUG_VELERO_POD_RESTART: -debug-velero-pod-restart. Optional.
For example, E2E tests can be run from Velero repository roots using the commands below:

Basic examples:

  1. Run Velero tests in a kind cluster with AWS (or Minio) as the storage provider:

    Start kind cluster

    kind create cluster

    BSL_PREFIX=<PREFIX_UNDER_BUCKET> BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/aws-creds CLOUD_PROVIDER=kind OBJECT_STORE_PROVIDER=aws make test-e2e

    Stop kind cluster

    kind delete cluster

  2. Run Velero tests in an AWS cluster:

    BSL_PREFIX=<PREFIX_UNDER_BUCKET> BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/aws-creds CLOUD_PROVIDER=aws make test-e2e

  3. Run Velero tests in a Microsoft Azure cluster:

    BSL_CONFIG="resourceGroup=$AZURE_BACKUP_RESOURCE_GROUP,storageAccount=$AZURE_STORAGE_ACCOUNT_ID,subscriptionId=$AZURE_BACKUP_SUBSCRIPTION_ID" BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/azure-creds CLOUD_PROVIDER=azure make test-e2e

    Please refer to velero-plugin-for-microsoft-azure documentation for instruction to set up permissions for Velero and to set up azure storage account and blob container

  4. Run Ginko-focused Restore Multi-API Groups tests using Minio as the backup storage location:

    BSL_CONFIG="region=minio,s3ForcePathStyle=\"true\",s3Url=<ip address>:9000" BSL_PREFIX=<prefix> BSL_BUCKET=<bucket> CREDS_FILE=<absolute path to minio credentials file> CLOUD_PROVIDER=kind OBJECT_STORE_PROVIDER=aws VELERO_NAMESPACE="velero" GINKGO_FOCUS="API group versions" make test-e2e

  5. Run Velero tests in a kind cluster with AWS (or Minio) as the storage provider and use Microsoft Azure as the storage provider for an additional Backup Storage Location:

    make test-e2e \
  CLOUD_PROVIDER=kind OBJECT_STORE_PROVIDER=aws BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> BSL_PREFIX=<PREFIX_UNDER_BUCKET> CREDS_FILE=/path/to/aws-creds \
  ADDITIONAL_OBJECT_STORE_PROVIDER=azure ADDITIONAL_BSL_BUCKET=<BUCKET_FOR_AZURE_BSL> ADDITIONAL_BSL_PREFIX=<PREFIX_UNDER_BUCKET> ADDITIONAL_BSL_CONFIG=<CONFIG_FOR_AZURE_BUCKET> ADDITIONAL_CREDS_FILE=/path/to/azure-creds

Upgrade examples:

  1. Run Velero upgrade tests with pre-upgrade version:

    This example will run 1 upgrade tests: v1.11.0 ~ target.

    make test-e2e \
  CLOUD_PROVIDER=aws  BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/aws-creds \
  UPGRADE_FROM_VELERO_VERSION=v1.11.0

  2. Run Velero upgrade tests with pre-upgrade version list:

    This example will run 2 upgrade tests: v1.10.2 ~ target and v1.11.0 ~ target.

    make test-e2e \
  CLOUD_PROVIDER=aws  BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/aws-creds \
  UPGRADE_FROM_VELERO_VERSION=v1.10.2,v1.11.0

Migration examples:

  1. Migration between 2 cluster of the same provider tests:

    Before running migration test, we should prepare kubeconfig file which contains config of each cluster under test, and set DEFAULT_CLUSTER and STANDBY_CLUSTER with the corresponding context value in kubeconfig file.

    MIGRATE_FROM_VELERO_VERSION includes a keyword of self, which means migration from Velero under test (specified by VELERO_IMAGE) to the same Velero. This variable can be set to v1.10.0, v1.10.0,v1.11.1, self or v1.11.0,self.

    make test-e2e \
  CLOUD_PROVIDER=aws  BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> CREDS_FILE=/path/to/aws-creds \
  DEFAULT_CLUSTER=<CONTEXT_OF_WORKLOAD_CLUSTER_DEFAULT> \
  STANDBY_CLUSTER=<CONTEXT_OF_WORKLOAD_CLUSTER_STANDBY> \
  MIGRATE_FROM_VELERO_VERSION=v1.11.0,self

  2. Datamover tests:

    The example shows all essential make variables for a Datamover test which is migrate from a AKS cluster to a EKS cluster.

    Note: STANDBY_CLUSTER_CLOUD_PROVIDER and STANDBY_CLUSTER_OBJECT_STORE_PROVIDER is essential here, it is for identify plugins to be installed on target cluster, since DEFAULT cluster's provider is different from STANDBY cluster, plugins are different as well.

    make test-e2e
  CLOUD_PROVIDER=azure \
  DEFAULT_CLUSTER=<AKS_CLUSTER_KUBECONFIG_CONTEXT> \
  STANDBY_CLUSTER=<EKS_CLUSTER_KUBECONFIG_CONTEXT> \ 
  FEATURES=EnableCSI \
  OBJECT_STORE_PROVIDER=aws \
  CREDS_FILE=<AWS_CREDENTIAL_FILE> \ 
  BSL_CONFIG=region=<AWS_REGION> \ 
  BSL_BUCKET=<S3_BUCKET> \ 
  BSL_PREFIX=<S3_BUCKET_PREFIC> \ 
  VSL_CONFIG=region=<AWS_REGION> \ 
  SNAPSHOT_MOVE_DATA=true \ 
  STANDBY_CLUSTER_CLOUD_PROVIDER=aws \ 
  STANDBY_CLUSTER_OBJECT_STORE_PROVIDER=aws \
  GINKGO_FOCUS=Migration

Filtering tests

Velero E2E tests uses Ginkgo testing framework which allows a subset of the tests to be run using the -focus and -skip flags to ginkgo.

For filtering tests, using make variables GINKGO_FOCUS and GINKGO_SKIP :

  1. GINKGO_FOCUS: Dot-separated list of labels to be included for Ginkgo description-based filtering. Optional. The -focus flag is passed to ginkgo using the GINKGO_FOCUS make variable. This can be used to focus on specific tests.
  2. GINKGO_SKIP: Dot-separated list of labels to be excluded for Ginkgo description-based filtering.Optional. The -skip flag is passed to ginkgo using the GINKGO_SKIP make variable. This can be used to skip specific tests.

GINKGO_FOCUS/GINKGO_SKIP can be interpreted into multiple -focus/-skip describe in Description-Based Filtering by dot-separated format for test execution management please refer to examples below.:

For example, E2E tests can be run with specific cases to be included and/or excluded using the commands below:

  1. Run Velero tests with specific cases to be included:

    make test-e2e \
  GINKGO_FOCUS =Basic\][\Restic  \
  CLOUD_PROVIDER=aws BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> BSL_PREFIX=<PREFIX_UNDER_BUCKET> CREDS_FILE=/path/to/aws-creds

    In this example, only case [Basic][Restic] is included.

  2. Run Velero tests with specific cases to be excluded:

    make test-e2e \
  GINKGO_SKIP=Scale.Schedule.TTL.Upgrade\]\[Restic.Migration\][\Restic  \
  CLOUD_PROVIDER=aws BSL_BUCKET=<BUCKET_FOR_E2E_TEST_BACKUP> BSL_PREFIX=<PREFIX_UNDER_BUCKET> CREDS_FILE=/path/to/aws-creds

    In this example, case Scale, Schedule, TTL, [Upgrade][Restic] and [Migration][Restic] will be skipped.

Full Tests execution

As we provided several examples for E2E test execution, what if no filter is involved and despite difference of test environment, is that a full test that covered all features on some certain environment, unfortunately, to prevent long time running or for some special test scenarioes, there're some tests need to be run in a single execution or pipeline with specific parameters provided.

Suggested pipelines for full test

Following pipelines should cover all E2E tests along with proper filters:

  1. CSI pipeline: As we can see lots of labels in E2E test code, there're many snapshot-labeled test scripts. To cover CSI scenario, a pipeline with CSI enabled should be a good choice, otherwise, we will double all the snapshot cases for CSI scenario, it's very time-wasting. By providing FEATURES=EnableCSI and PLUGINS=<provider-plugin-images>, a CSI pipeline is ready for testing.
  2. Data mover pipeline: Data mover scenario is the same scenario with migaration test except the restriction of migaration between different providers, so it better to separated it out from other pipelines. Please refer the example in previous.
  3. Restic/Kopia backup path pipelines:
    1. Restic pipeline: For the same reason of saving time, set UPLOADER_TYPE to restic for all file system backup test cases;
    2. Kopia pipeline: Set UPLOADER_TYPE to kopia for all file system backup test cases;
  4. Long time pipeline: Long time cases should be group into one pipeline, currently these test cases with labels Scale, Schedule or TTL can be group into a pipeline, and make sure to skip them off in any other pipelines.

Note: please organize filters among proper pipelines for other test cases.

Adding tests

API clients

When adding a test, aim to instantiate an API client only once at the beginning of the test. There is a constructor newTestClient that facilitates the configuration and instantiation of clients. Also, please use the kubebuilder runtime controller client for any new test, as we will phase out usage of client-go API clients.

TestCase frame provide a serials of interface to concatenate one complete e2e test. it's makes the testing be concise and explicit.

VeleroBackupRestoreTest interface

VeleroBackupRestoreTest interface provided a standard workflow of backup and restore, which makes the whole testing process clearer and code reusability.

For programming conventions, Take ResourcePoliciesCase case for example:

Init
  • It's need first call the base TestCase Init function to generate random number as UUIDgen and set one default timeout duration
  • Assigning CaseBaseName variable with a case related prefix, all others variables will follow the prefix
  • Assigning NamespacesTotal variable, and generating namespaces
  • Assigning values to the inner variable for specific case
  • For BackupArgs, as Velero installation is using global Velero configuration, it's NEED to specify the value of the variable snapshot-volumes or default-volumes-to-fs-backup explicitly.
CreateResources
  • It's better to set a global timeout in CreateResources function which is the real beginning of one e2e test
Destroy
  • It only cleans up resources in currently test namespaces, if you wish to clean up all resources including resources created which are not in currently test namespaces, it's better to override base Destroy function
Clean
  • Clean function only clean resources in namespaces which has the prefix CaseBaseName. So the the names of test namespaces should start with prefix of CaseBaseName.
  • If wantting to clean up all resources including resources created which is not in currently test namespaces, it's better to override base Clean function
Velero Installation
  • Velero is installed with global velero config before the E2E test start, so if the case (such as upgrade/migration, etc.) does not want to use the global velero config, it is NEED TO UNINSTALL velero, or the global velero config may affect the current test.
TestFunc

The TestFunc function concatenate all the flows in a test. It will reduce the frequency of velero installation by installing and checking Velero with the global Velero. It's Need to explicit reinstall Velero if the case has specicial configuration, such as API Group test case we need to enable feature EnableCSI.

Tips

Look for the ⛵ emoji printed at the end of each install and uninstall log. There should not be two install/unintall in a row, and there should be tests between an install and an uninstall.

Troubleshooting

If velero log shows level=error msg="Failed to get bucket region, bucket: xbucket, error: operation error S3: HeadBucket, failed to resolve service endpoint, endpoint rule error, A region must be set when sending requests to S3." backup-storage-location=velero/default cmd=/plugins/velero-plugin-for-aws controller=backup-storage-location logSource="/go/src/velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:136" pluginName=velero-plugin-for-aws, it means you need to set BSL_CONFIG to include region=<region>.

Directories

Path Synopsis
api-group
backup-volume-info
resources-check

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL
go.dev uses cookies from Google to deliver and enhance the quality of its services and to analyze traffic. Learn more.