OpenShift Maven|Gradle Plugin should use Deployments by default

[manusa]

Description

We should switch OpenShift Maven|Gradle plugins to create Deployments instead of DeploymentConfigs (DC) by default. The application should behave as if the jkube.build.switchToDeployment was defaulted to true. Users should be able to still use DCs by setting that property to false or by setting any of the other related properties/configurations that set the kind of controller to be built.

Update 2024-01-25

OpenShift officially deprecates the usage of DeploymentConfigs in version 4.14 (see https://access.redhat.com/articles/7041372)

This has been already tackled by Quarkus (https://github.com/quarkusio/quarkus/pull/37229)

To be able to properly support image streams, we need to add the following annotation to the Pod template (as documented in https://docs.openshift.com/container-platform/4.14/openshift_images/using-imagestreams-with-kube-resources.html):

alpha.image.policy.openshift.io/resolve-names: '*'

Relates to:

• #630
• #667

/cc @rgordill :pray:

[rohanKanojia]

Related discussion https://github.com/fabric8io/fabric8-maven-plugin/issues/1042 on Fabric8 Maven Plugin

[manusa]

There seems to be recent effort involved in maintaining the S2I build approach, so it might make sense to delay this change until there's a clear vision on the future of S2I.