Document init tasks

[iocanel]

Resolves: #35455

[iocanel]

@cescoffier: Added more docs around init task. The doc covers all areas mentioned in #35455

[github-actions]

🙈 The PR is closed and the preview is expired.

[cescoffier]

Much much better!

[cescoffier]

Squash and rebase?

[maxandersen]

not sure if this is just how it was done or new names but feels we are being somewhat inconsistent in naming here:

quarkus.kubernetes.init-task-defaults.wait-for-image vs quarkus.kubernetes.init-containers.wait-for-flyway

should it be init-task-defaults and -init-task.wait-for-flyway or init-containers-defaults and init-containers.wait-for-flyway ?

and should wait-for-flyway be wait-for-flyway-image ?

[cescoffier]

I agree with @maxandersen, it looks more consistent.

[iocanel]

and should wait-for-flyway be wait-for-flyway-image ?

In quarkus.kubernetes.init-container.wait-for-flyway.image the wait-for-flyway part is the container name. This is part of the container customization options that we have since forever.

The quarkus.kubernetes.init-task-defaults is a new object I added to hold a couple of flags and a default image.

I could possibly change the way we pass the image to be more aligned with how we configure containers and make it something like quarkus.kubernetes.init-task-defaults.wait-for-container.image. Would that work better @maxandersen @cescoffier ?

[cescoffier]

+1

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.