The setup is quite similar to the Openshift CI testing and is introduced in https://github.com/wildfly/quickstart/pull/908.

The kubernetes-ci.yml in the PR essentially calculates from the changed files which quickstarts we should test. Then for each quickstarts it calls the .github/workflows/scripts/kubernetes/core/run-quickstart-test-on-kubernetes.sh with the name of the quickstart directory.

Locally, you should be able to run the quickstart by doing the following:

• Run minikube and enable the registry similar to what we do in the cloud tests. See the README in https://github.com/wildfly-extras/wildfly-cloud-tests for how to do that
• In the root directory of the quickstarts clone, run .github/workflows/scripts/kubernetes/core/run-quickstart-test-on-kubernetes.sh <quickstart name>

Some quickstarts have a .github/workflows/scripts/kubernetes/qs-overrides/micrometer/overridable-functions.sh file to install additional things etc.similar to what we did in the OpenShift CI setup.

If you need more control over the script execution, you can add some sleeps in the script to pause it while debugging. Or you try to install everything manually. Essentially the script does the steps in https://docs.wildfly.org/wildfly-charts/guides/kubernetes.html along with the extra stuff from the overridable-functions.sh (for the quickstarts where this applicable). Once the application is ready in Kubernetes, it runs the tests by running mvn verify -Pintegration-testing.

When everything is working, remove the quickstart from .github/workflows/scripts/kubernetes/core/excluded-directories.txt so that kubernetes-ci.yml can pick it up.