name : wildfly-parameters -  mountPath : "/out" name : wildfly-config containers : -  image : jboss/wildfly:10.1.0.Final name : server command : - "/opt/jboss/wildfly/bin/standalone.sh" - "-Djboss.server.config.dir=/config" ports : -  containerPort : 8080 name : http protocol : TCP volumeMounts : -  mountPath : "/config" name : wildfly-config volumes : -  name : wildfly-parameters configMap : name : wildfly-parameters -  name : wildfly-config emptyDir : {} Image holding the configuration templates Parameters are mounted from a ConfigMap  wildfly-parameters The target directory for writing out processed templates. This is mounted from an empty volume. The directory holding the generated full configuration files is mounted as  /config Volume declaration for the parameters’ ConfigMap and the empty directory used for sharing the processed configuration. This declaration is quite a mouthful, so let’s drill down: the Deployment specification contains a Pod with our init container, the application container, and two internal Pod volumes: • The first volume,  wildfly-parameters , contains our ConfigMap with the same name (i.e., it includes a file called  config.yml  holding our parameter value). • The other volume is an empty directory initially and is shared between the init container and the WildFly container. Solution  |  169