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.

Sign up for GitHub

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

Jump to bottom

Separate rancher from tested clusters #570

Open

kravciak opened this issue Dec 6, 2023 · 0 comments

Assignees

Labels

area/qa

Collaborator

kravciak commented Dec 6, 2023

Currently everything runs on the same VM:

k3d cluster created in VM
rancher installed on k3d cluster
everything installed on local cluster
tests running on the same VM

This sometimes leads to a problem, for example when kubewarden policies are changed it takes resources from local cluster and rancher is affected.

Look into the solution where rancher runs on it's own cluster. Tested clusters are either imported or created on demand.

kravciak added the area/qa label

kravciak self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment