Options with quarkus.openshift.init-containers prefix are ignored

[fedinskiy]

Describe the bug

I have an application, which uses flyway and deployed on openshift via quarkus extension. I want to change init container by using properties quarkus.openshift.init-containers.wait-for-flyway and quarkus.openshift.init-containers.wait-for-flyway.image-pull-policy described in the guide[1]. However, these changes are not reflected in generated openshift.yml file.

[1] https://quarkus.io/guides/init-tasks#using-a-custom-wait-for-container-image

Expected behavior

Generated openshift.yml file contains custom image and pull policy in its initContainers section, quay.io/quarkusqeteam/wait and Always respectively.

Actual behavior

Generated openshift.yml file contains default image and pull policy in its initContainers section, groundnuty/k8s-wait-for:no-root-v1.7 and IfNotPresent respectively.

How to Reproduce?

1. git clone -b configure-container git@github.com:fedinskiy/reproducer.git
2. cd reproducer && mvn clean verify -Popenshift
3. grep -B4 "wait" target/kubernetes/openshift.yml

Output of uname -a or ver

6.7.3-200.fc39.x86_64

Output of java -version

Java version: 21.0.1, vendor: Eclipse Adoptium

Quarkus version or git rev

3.8.1

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)

Additional information

Container image can be changed via quarkus.openshift.init-task-defaults.wait-for-container.image property, but a) for all tasks b) there is no way to change pull policy.

[quarkus-bot]

/cc @geoand (kubernetes,openshift), @iocanel (kubernetes,openshift)

[fedinskiy]

The changes were added here: #35918 and are related to this task: #35455

[appiepollo14]

Would like to give this one a try

[appiepollo14]

@fedinskiy did some digging, controlling the image works when using the following config:
quarkus.openshift.init-tasks.flyway.image=quay.io/quarkusqeteam/wait
However, this is not according to the documentation page.

Trying to control the IPP in the same way, results in nothing as there is no imagePullPolicy config in the initTasks class.
quarkus.openshift.init-tasks.flyway.image-pull-policy=Always
I can create an extra initContainer using for example:

quarkus.openshift.init-tasks.xx.image=quay.io/quarkusqeteam/wait
quarkus.openshift.init-containers.xx.image-pull-policy=IfNotPresent

I just can't combine the two things above to work as intended.

@geoand @iocanel do you have any directions to continue solving the issue? I don't know how to proceed.

Do you have pointers for a way to debug what is going on in the Quarkus sources when compiling for example the reproducer project?

[appiepollo14]

Looks to me like for example the Flyway extension, creates an initTask as a buildStep. https://github.com/quarkusio/quarkus/blob/main/extensions/flyway/deployment/src/main/java/io/quarkus/flyway/deployment/FlywayProcessor.java#L265-L273

The initTaskConfig doesn't have that many config properties, like for example the image-pull-policy isn't available. https://github.com/quarkusio/quarkus/blob/main/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/InitTaskConfig.java