Closed collivier closed 1 month ago
Since cni_compatible is not part of the certification criterions (not "essential"), from my point of view it is ok to be removed from "cert" category.
I see no issues in removing this from the cert
option and from the list of tests for the certification prior to the v1.0.0 release we have planned. Once any bugs are fixed it can be added back, despite not being an essential
test, I still think it's a valuable test. It could likely be rewritten and improved.
Thoughts @wavell @denverwilliams @HashNuke ?
This test when running with the cert
command crashes with an error vs returning PASS/FAIL.
Suggestions on cert call for this test longer term
Suggestions for short term:
Describe the bug
cni_compatible installs a very EOL Kubernetes version (3y old)
More this kind/kubernetes version fails vs cgroup v2 because of lack of support
ERROR: failed to create cluster: could not find a log line that matches "Reached target .*Multi-User System.*|detected cgroup v1"
Please note that the test keeps failing and doesn't stop after the first issue
I would consider that cert won't install any additional cluster as it is a big issue out of a lab environment.
To Reproduce
Expected behavior
cni_compatible removed from cert and updated to an active kubernetes version.