...
However the tests are currently launched manually after a cluster is deployed, integration with the CI is still pending, as we are hitting issues with the framework itself:
https://jira.akraino.org/projects/VAL/issues/VAL-108
https://jira.akraino.org/projects/VAL/issues/VAL-109
https://jira.akraino.org/projects/VAL/issues/VAL-110
The test that could be run are OS and conformance testing:
As we use OpenShift, we cannot use the standard k8s conformance tests, because they are aimed for upstream Kubernetes and not for OpenShift.
As an alternative, we can run the openshift test validation suite: https://logsgithub.akraino.org/redhat-kni/bluval_results/redhat-kni/20200423-061536/results/os/ltp/
https://logs.akraino.org/redhat-kni/bluval_results/blueprint-pae/20200423-113054/results/k8s/conformance/com/openshift/origin/blob/master/test/extended/conformance-k8s.sh
This is similar as the sonobuoy one, launching a set of e2e tests to validate that the cluster is deployed and works at a functional level. Those are the collected results:
https://logs.akraino.org/redhat-kni/bluval_results/blueprint-pae/2020042320200428-113054/results/k8s/kube-hunter/034810/ctr.log
Test Dashboards
https://jenkins.akraino.org/view/kni
...