Skip to content

some fixing up #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 11, 2021
Merged

some fixing up #50

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 7 additions & 9 deletions documentation/staging/content/navigate/image.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,20 +24,18 @@ in a Kubernetes environment using the [WebLogic Image Tool](https://oracle.githu

### Design View
The `Design View` helps you specify the necessary data needed to run the WebLogic Image Tool to build an image for
running the WebLogic domain with all resources configured and applications deployed.

Use the design view to create a new or use an existing (the default) `Primary Image` and, depending on your choice of [domain location]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}),
an `Auxiliary Image`. Auxiliary images are available for "Model in Image" domains _only_.
running the WebLogic domain with all resources configured and applications deployed. The `Design View` page is divided into `Primary Image` and `Auxiliary Image` pages.
Auxiliary images are available for the "Model in Image" [domain location]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}) _only_.

- `Primary Image` - The image containing the Oracle Fusion Middleware software. It is used as the basis of all containers that run WebLogic Servers for the domain.
- `Auxiliary Image` - The image that supplies the WebLogic Deploy Tooling software and the model files. At runtime, the auxiliary image's content is merged with the primary image's content.

One primary image can be reused for hundreds of domains whereas an auxiliary image is domain-specific. When using auxiliary images,
the primary image contains the OS, JDK, and FMW software installations; the auxiliary image supplies the specifics for a single domain.


The `Design View` page for the `Primary Image` and the `Auxiliary Image` is divided into several primary panes and a few advanced panes.
Note that not all the fields described for the `Primary Image` are relevant for an `Auxiliary Image`, such as the JDK and Oracle installers, and patching. The exceptions will be called out.
Use the `Design View` to create a new or use an existing (the default) `Primary Image` and, for Model in Image domains only, an `Auxiliary Image`.
The `Design View` page for the `Primary Image` and the `Auxiliary Image` has several panes and a few advanced panes.
Note that _not all_ the fields described for the `Primary Image` are relevant for an `Auxiliary Image`, such as the JDK and Oracle installers, and patching. The exceptions are noted.

- [Target Image Name and Registry Credentials](#target-image-name-and-registry-credentials)
- [Base Image to Use](#base-image-to-use)
Expand Down Expand Up @@ -72,7 +70,7 @@ field. Any container image registry address found in the base image tag will be
`Custom Base Image Pull Username` and `Custom Base Image Pull Password` fields.

When using a custom base image, the application requires the image to be inspected using the WebLogic Image Tool's
[Inspect Image](https://oracle.github.io/weblogic-image-tool/userguide/tools/inspect-image/) command. Note that this
[Inspect Image](https://oracle.github.io/weblogic-image-tool/userguide/tools/inspect-image/) command. **Note**: This
action is relevant for `Primary Images` only. To invoke this inspection, click
`Inspect Custom Base Image`. This inspection tells the application if Java or the
Oracle Fusion Middleware software is already installed in the image. If it finds either of these software packages
Expand Down Expand Up @@ -115,7 +113,7 @@ latest capabilities, many of which are exposed by this application. As such, us
recommended.

#### Patch Oracle Home
This pane is relevant for `Primary Images` only. Oracle strongly recommends patching all Oracle Fusion Middleware installations with the latest Patch Set Updates (PSUs)
**NOTE**: This pane is relevant for `Primary Images` only. Oracle strongly recommends patching all Oracle Fusion Middleware installations with the latest Patch Set Updates (PSUs)
and other recommended patches to ensure that the latest security fixes are applied. This pane configures the WebLogic
Image Tool to apply the specified patches to the Oracle Home during the image creation process. There are two mechanisms
for specifying that patches should be applied:
Expand Down
6 changes: 3 additions & 3 deletions documentation/staging/content/navigate/kubernetes/k8s-weblogic-domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The following sections describe the other panes that support configuring the gen
#### Primary Image to Use for the Domain
This pane focuses on the container primary image to use to run the WebLogic Server domain in a container.
- When using either "Model in Image" or "Domain in Image" [domain location]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}), the `Primary Image Tag` field is read-only; its value is set using the
`Image Tag` field in the `Primary Image` section.
`Image Tag` field in the `Image` section.
- In the case of "Domain in PV", the `Image Tag` field is not read-only and _is_
the place to specify the image to use to run the WebLogic domain's containers.
- The read-only `Image Registry Address` field is populated by parsing the value of the `Image Tag` field
Expand All @@ -95,7 +95,7 @@ The choices are:
- `Never` - Never pull the image; this will result in an error if the image is not already present on the Kubernetes node.

If pulling the image from the specified image registry does not require authentication,
then `Specify Auxiliary Image Pull Credentials` should be disabled. When enabled, use the `Use Existing Image Pull Secret` field to tell the application
then `Specify Image Pull Credentials` should be disabled. When enabled, use the `Use Existing Image Pull Secret` field to tell the application
whether to use an existing image pull secret or create a new one. Specify the image pull secret name in the
`Image Pull Secret Name` field. When creating a new secret, specify the secret data using the
`Image Registry Pull Username`, `Image Registry Pull Email Address`, and `Image Registry Pull Password` fields.
Expand All @@ -104,7 +104,7 @@ whether to use an existing image pull secret or create a new one. Specify the i

For "Model in Image" domains only, this pane focuses on the container auxiliary image to use for the domain.
- The `Auxiliary Image Tag` field is read-only; its value is set using the
`Auxiliary Image Tag` field in the `Auxiliary Image` section of the Image page.
`Auxiliary Image Tag` field in the `Auxiliary Image` page of the `Image` section.
- Use the `Auxiliary Image Pull Policy` field to specify when to pull the domain's auxiliary image from the image registry. The choices are:

- `If Not Present` (default) - Only pull the image if it is not already present.
Expand Down