Domain creation images are used for supplying WebLogic Deploy Tooling (WDT) model files, WDT variables files, WDT application archive files (collectively known as WDT model files), and the directory where the WebLogic Deploy Tooling software is installed (known as the WDT Home) when deploying a domain using a Domain on PV model. You distribute WDT model files and the WDT executable using these images, then the operator uses them to manage the domain.
NOTE: These images are only used for creating the domain and will not be used to update the domain.
You can configure one or more domain creation images in a domain resource.
Optionally, you can set the imagePullPolicy
,
which defaults to Always
if the image
ends in :latest
and IfNotPresent
,
otherwise.
If image pull secrets are required for pulling the images, then the secrets must be referenced using domain.spec.imagePullSecrets
.
Also, optionally, you can configure the source locations of WDT model files and WDT Home
using the sourceModelHome
and sourceWDTInstallHome
fields, as described in this
section.
For details about each field, see the References.
For a basic configuration example, see Configuration example 1.
Run the kubectl explain domain.spec.configuration.initializeDomainOnPV.domain.domainCreationImages
command, or
See the initializeDomainOnPV.domain.domainCreationImages
section
in the domain resource
schema.
Use the optional attributes, sourceModelHome
and
sourceWdtInstallHome
, to specify non-default locations for the
WDT model files and WDT Home in your domain creation image(s).
Allowed values for sourceModelHome
and sourceWdtInstallHome
:
/auxiliary/models
and /auxiliary/weblogic-deploy
, respectively.None
- Indicates that the image has no WDT model files or WDT Home, respectively.If you set the sourceModelHome
or sourceWDTInstallHome
to None
or,
the source attributes are left unset and there are no files at the default locations,
then the operator will ignore the source directories. Otherwise,
note that if you set a source directory attribute to a specific value
and there are no files in the specified directory in the domain creation image,
then the domain deployment will fail.
The files in sourceModelHome
and sourceWDTInstallHome
directories will be made available in /aux/models
and /aux/weblogic-deploy
directories of the WebLogic Server container in all pods, respectively.
For example source locations, see Configuration example 2.
If specifying multiple images with WDT model files in their respective sourceModelHome
directories, then WDT model files are merged. Files from later images take precedence over files from earlier images.
When specifying multiple images, ensure that only one of the images supplies a WDT Home using
sourceWDTInstallHome
.
If you provide more than one WDT Home among multiple images,
then the domain deployment will fail.
Set sourceWDTInstallHome
to None
, or make sure there are no files in /auxiliary/weblogic-deploy
,
for all but one of your specified domain creation images.
For an example of configuring multiple images, see Configuration example 3.
The following configuration examples illustrate each of the previously described sections.
This example specifies the image location; all other fields are at default values.
spec:
configuration:
initializeDomainOnPV:
domainCreationImages:
- image: wdt-model-image:v1
This example is the same as Example 1, except that it specifies the source locations for the WDT model files and WDT Home.
spec:
configuration:
configuration:
initializeDomainOnPV:
domainCreationImages:
- image: wdt-model-image:v1
sourceModelHome: /foo/models
sourceWDTInstallHome: /bar/weblogic-deploy
This example is the same as Example 1, except it configures multiple images and sets the sourceWDTInstallHome
for the second image to None
.
In this case, the source location of the WDT installation from the second image wdt-model-image2:v1
will be ignored.
spec:
configuration:
initializeDomainOnPV:
domainCreationImages:
- image: wdt-model-image:v1
- image: wdt-model-image2:v1
sourceWDTInstallHome: None