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

Create private runner for running CAPV E2E #612

Open
alexander-demicev opened this issue Jul 23, 2024 · 3 comments
Open

Create private runner for running CAPV E2E #612

alexander-demicev opened this issue Jul 23, 2024 · 3 comments
Assignees
Labels
area/ci area/testing Indicates an issue related to test

Comments

@alexander-demicev
Copy link
Member

Setup a private runner to run E2E test for CAPV integration

@yiannistri
Copy link
Contributor

There is now an EIO ticket to move this forward https://github.com/rancherlabs/eio/issues/2579

@kkaempf
Copy link

kkaempf commented Nov 27, 2024

This should be unblocked and done now.

Anything missing @yiannistri ?

@yiannistri
Copy link
Contributor

yiannistri commented Nov 27, 2024

Now that we have an environment we need to:

  • Run the e2e tests manually to ensure they pass. As it's a new environment I anticipate that we need to do some configuration on the vSphere side to be able to create CAPI clusters.
  • Figure out how to run them as part of CI (*)

* After talking to Brandon, it became evident that we can't use VPN to access this environment for security reasons. So perhaps we need to create a self-hosted runner (a new VM basically) that is running on vSphere, that will be used to run e2e tests against Turtles using vSphere. We may need a research task/ticket for this.

@kkaempf kkaempf moved this from Blocked to CAPI Backlog in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/testing Indicates an issue related to test
Development

No branches or pull requests

3 participants