action #155851
Updated by ph03nix 4 months ago
Since k3s is not available on s390x anymore (see #154996) we need a different approach for test runs that rely on k3s as kubernetes platform. We agreed that a possible approach is to create a dedicated k3s test machine in the O3 network, which can be used for openQA test runs.
This ticket is about setting up a dedicated k3s machine and adapt our test runs to use that machine, instead of a local k3s installation.
Please note, that for publiccloud tests we likely still need to rely on a local k3s installation.
## Acceptance criteria
* Ask infra team for a dedicated VM (Be reasonable with the requested resources) in the O3 network
* Ensure that this machine can be accessed from OSD
* Adapt our test code to use this VM instead of installing k3s locally
* Document the new machine, either as a dedicated Confluence page in the [Infrastructure Section](https://confluence.suse.com/pages/viewpage.action?pageId=808091683) or by a dedicated git repository in our [qa-c gitlab group](https://gitlab.suse.de/qac/)