When using an initialization job (liquibase, flyway, soon kafka and amqp), Quarkus generates:

1. A Kubernetes job
2. An init container configuration waiting for the job execution

Currently, the second step uses a random image based on Alpine (groundnuty/k8s-wait-for:no-root-v1.7 - https://github.com/groundnuty/k8s-wait-for) and with a few CVEs. It's important to understand that this image runs in production at the start of the application.

This issue is about:

1. Make that image configurable
2. Find a better image, ideally validated by Red Hat

Unfortunately, the approach recommended in the OpenShift documentation (https://docs.openshift.com/container-platform/4.8/nodes/containers/nodes-containers-init.html) is not suitable as UBI does not provide kubectl. We at least need kubeclt to, then, write an entry point command waiting for the job execution.