Marc Nuri

Relates to #1425

I really don't mind. However, note that some users might be triggering these separately or concurrently (e.g. in our Integration Tests we run these goals in parallel). For the Outer...

As I see it this would be more or less the expected execution order: | Inner Loop | Outer Loop | |------------|------------| | build | build | | _push_ |...

### Eclipse JKube [CI Report](https://github.com/jkubeio/ci) Started new GH workflow run for https://github.com/eclipse/jkube/pull/1636 (_2022-08-23T09:37:26Z_) :gear: [JKube E2E Tests (2910306139)](https://github.com/jkubeio/ci/actions/runs/2910306139) - :heavy_check_mark: [Bootstrap CI test run (#1636)](https://github.com/jkubeio/ci/runs/7969783224?check_suite_focus=true) - :heavy_check_mark: [K8S v1.12.0 dockerfile...

> VertxHealthCheckEnrichers's configuration seems to have really different nested enricher configuration. It works for properties but it doesn't seem to be working when configuration is provided from Gradle Groovy DSL...

Now that #1673 is merged we need to rebase this one.

### Eclipse JKube [CI Report](https://github.com/jkubeio/ci) Started new GH workflow run for https://github.com/eclipse/jkube/pull/1672 (_2022-07-26T12:05:35Z_) :gear: [JKube E2E Tests (2739234537)](https://github.com/jkubeio/ci/actions/runs/2739234537) - :heavy_check_mark: [Bootstrap CI test run (#1672)](https://github.com/jkubeio/ci/runs/7519438118?check_suite_focus=true) - :heavy_check_mark: [K8S v1.12.0 dockerfile...

### Eclipse JKube [CI Report](https://github.com/jkubeio/ci) Started new GH workflow run for https://github.com/eclipse/jkube/pull/1492 (_2022-08-24T06:12:29Z_) :gear: [JKube E2E Tests (2916741610)](https://github.com/jkubeio/ci/actions/runs/2916741610) - :heavy_check_mark: [Bootstrap CI test run (#1492)](https://github.com/jkubeio/ci/runs/7988234669?check_suite_focus=true) - :heavy_check_mark: [K8S v1.12.0 dockerfile...

Your YAML template doesn't seem to adapt to the structure of a DeploymentConfig: https://docs.openshift.com/container-platform/4.10/rest_api/workloads_apis/deploymentconfig-apps-openshift-io-v1.html#spec-strategy https://docs.openshift.com/container-platform/4.10/rest_api/workloads_apis/deploymentconfig-apps-openshift-io-v1.html#spec-strategy-rollingparams I'm not sure, but this seems more like the input you need: ```yaml spec: strategy:...

> how do I get it to just generate a deployment for openshift? There are several options available. The easiest is to use the `jkube.build.switchToDeployment` property: ```xml true ``` https://www.eclipse.org/jkube/docs/openshift-maven-plugin#jkube-openshift-deploymentconfig