action #155851
open[containers] Establish dedicated k3s test machine
0%
Description
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 or by a dedicated git repository in our qa-c gitlab group
Updated by ph03nix 10 months ago
- Related to action #154996: Investigate usage of k3s on s390x added
Updated by ph03nix 10 months ago
- Related to action #152593: [refactoring] Move k3s part away from podman_pods added
Updated by ph03nix 10 months ago
We might also need to update the current k3s test codes to do a proper cleanup. e.g. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18723 leaks resources as of now.
Another idea would be to wipe the k3s system every day or every other hour to ensure that dangling resources do not persist.
Updated by slo-gin 9 months ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by openqa_review 8 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kubectl_tests
https://openqa.suse.de/tests/14235616#step/kubectl/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by ph03nix 8 months ago
I think https://sd.suse.com/servicedesk/customer/portal/1/SD-153337 unblocks it again and redirect us to self-service?
Updated by slo-gin 7 months ago
- Priority changed from High to Normal
This ticket was set to High priority but was not updated within the SLO period. The ticket will be set to the next lower priority Normal.
Updated by ph03nix 5 months ago · Edited
https://sd.suse.com/servicedesk/customer/portal/1/SD-162647 - asking for more resources in the qe-c group so that we can create more than one VM there.
Updated by ph03nix about 2 months ago
- Subject changed from Establish dedicated k3s test machine to [containers] Establish dedicated k3s test machine
Updated by mloviska 23 days ago
Resource increase request for qe-c namespace https://sd.suse.com/servicedesk/customer/portal/1/SD-174733
Updated by mloviska 15 days ago · Edited
So as of now we have 2 nodes, only one worker though (waiting for more resources to be allocated for our namespace)
NAME STATUS ROLES AGE VERSION
galatea-worker-eaa5776c Ready <none> 14d v1.30.6+k3s1
neptune-controlplane Ready control-plane,etcd,master 15d v1.30.6+k3s1
Pods/deployments are running
NAMESPACE NAME READY STATUS RESTARTS AGE
default app-cache-56bdc58878-c5zpr 1/1 Running 0 49s
default kuard 1/1 Running 0 11s
kube-system coredns-7b98449c4-xrx5z 1/1 Running 4 (3d21h ago) 15d
kube-system local-path-provisioner-595dcfc56f-xmkvp 1/1 Running 4 (3d21h ago) 15d
kube-system metrics-server-cdcc87586-qg5zq 1/1 Running 4 (3d21h ago) 15d
Updated by mloviska 14 days ago
While configuring private registries, I have noticed that ca-certificates-suse package from https://download.suse.de/ibs/SUSE:/CA/openSUSE_Tumbleweed/noarch/ cannot be installed, as the repo is not reachable. Moving the node to publiccloud/vlan2236 network fixed the problem.