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 image sources hard coded #2243

Open
lentzi90 opened this issue Nov 8, 2024 · 0 comments
Open

E2e image sources hard coded #2243

lentzi90 opened this issue Nov 8, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@lentzi90
Copy link
Contributor

lentzi90 commented Nov 8, 2024

/kind bug

What steps did you take and what happened:

I noticed that we have hard coded a few things with the introduction of ORC in the e2e tests. This unfortunately makes the tests much less flexible than they used to be. In theory, we could point to any OpenStack-based cloud, tune the e2e config to match and run the suite.
The images used could differ.

Now with ORC we have hard coded where the images should come from, while still allowing the exact name to be configurable.
This does not make sense to me. We should make the source also configurable.

I think/hope it is already possible to pre-create the images and ORC will just adopt them. This is good.

What did you expect to happen:

It should be possible to run the e2e test suite in different configurations without assumptions on what exact images would be used or where they can be found.

Anything else you would like to add:

I intend to work on this but I don't have an estimate on when I will have the time.

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Status: Inbox
Development

No branches or pull requests

2 participants