[ https://issues.jboss.org/browse/TEIIDSB-92?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-92: --------------------------------------- I tried adding an init container to the deploymentconfig.yml. However f-m-p does not handle init containers well. I checked across several versions: 3.5.41/42 - fails to deploy with: failed to update DeploymentConfig from openshift.yml. io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PUT at: https://192.168.42.57:8443/apis/apps.openshift.io/v1/namespaces/teiid-dat.... Message: DeploymentConfig.apps.openshift.io "rdbms-example" 4.0.0 - Fails earlier: Failed to execute goal io.fabric8:fabric8-maven-plugin:4.0.0:resource (build) on project rdbms-example: Execution build of goal io.fabric8:fabric8-maven-plugin:4.0.0:resource failed.: NullPointerException ... 4.1.0 - Deploys, but creates the wrong deployment config. Checking the console shows !screenshot-1.png|thumbnail! Note the extra spring-boot container. It also reports that it's failing to pull the image and fails to actually create pod. The most similar bug reports are: https://github.com/fabric8io/fabric8-maven-plugin/issues/1114 and https://github.com/fabric8io/fabric8-maven-plugin/issues/1283 which seems to describe the 3.5.x behavior. [~rareddy] did you ever get any closure on your issue? -- This message was sent by Atlassian Jira (v7.12.1#712002)