Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E tests install/run in AWS, Azure, vSphere and KIND #3232

Closed
dsu-igeek opened this issue Jan 12, 2021 · 0 comments · Fixed by #3286
Closed

E2E tests install/run in AWS, Azure, vSphere and KIND #3232

dsu-igeek opened this issue Jan 12, 2021 · 0 comments · Fixed by #3286
Assignees
Labels
CI/CD Enhancement/Dev Internal or Developer-focused Enhancement to Velero

Comments

@dsu-igeek
Copy link
Contributor

Currently E2E tests are targeted to run in KIND with different backend providers. Need to move to install/run on all different cloud providers.

Describe the solution you'd like
Split cloud provider and storage provider in test framework.

Environment:

  • Velero version (use velero version): 1.6
  • Cloud provider or hardware configuration: AWS, Azure, vSphere and KIND

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.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "The project would be better with this feature added"
  • 👎 for "This feature will not enhance the project in a meaningful way"
@dsu-igeek dsu-igeek added P1 - Important Enhancement/Dev Internal or Developer-focused Enhancement to Velero CI/CD labels Jan 12, 2021
@dsu-igeek dsu-igeek self-assigned this Jan 12, 2021
@dsu-igeek dsu-igeek linked a pull request Jan 25, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Enhancement/Dev Internal or Developer-focused Enhancement to Velero
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant