Disable admin console on wildfly images

[deewhyweb]

When running wildfly or JBoss images on kubernetes the admin console is not required. All configuration changes should be made using scripts at image build time or on startup using the jboss-cli.

Disabling the admin console will allow the health check required by the wildfly operator to work without causing any potential security implications. For the health check to work the management interface needs to be available on 0.0.0.0

The OpenShift JBoss image defaults to disabled admin console. It does this by using a standalon-openshift.xml configuration with the console disabled.

I recommend we do something similar, e.g. include a custom standalone.xml, or edit the standalone.xml using an xml parser in the dockerfile.

[deewhyweb]

Add console-enabled="false" to in standalone.xml (or host.xml):

Raw

...(snip)...

[HarikrishnanBalagopal]

The OpenShift JBoss image defaults to disabled admin console. It does this by using a standalon-openshift.xml configuration with the console disabled.

@deewhyweb would using the Openshift JBoss image instead of UBI

move2kube/assets/built-in/transformers/dockerfilegenerator/java/jboss/templates/Dockerfile.jboss

Line 2 in 14357a9

FROM registry.access.redhat.com/ubi8/ubi-minimal:latest

fix this issue?