Operator 3.2.4 #2417
Merged
Operator 3.2.4 #2417
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mriccell
reviewed
Jun 18, 2021
| * Resolved an issue related to scalingAction.sh when there were multiple domains in the same namespace ([#2388](https://github.com/oracle/weblogic-kubernetes-operator/pull/2388)). | ||
| * Updated introspection and other scripts to consistently use ISO-8601 timestamp formatting ([#2386](https://github.com/oracle/weblogic-kubernetes-operator/pull/2386)). | ||
| * Resolved an issue related to monitoring exporter integration and Istio ([#2390](https://github.com/oracle/weblogic-kubernetes-operator/pull/2390)). | ||
| * Additional diagnostics when the Node Manager fails to start ([#2393](https://github.com/oracle/weblogic-kubernetes-operator/pull/2393)). |
There was a problem hiding this comment.
Is this 2393 related to the liveness probe? If so I would prefer a more generic description otherwise it would lead to confusion.
tbarnes-us
reviewed
Jun 18, 2021
ddsharpe
reviewed
Jun 18, 2021
| - Supply a new image with new or changed model files | ||
| and use your Domain YAML `spec.image` field to reference the image. | ||
| - Supply a new image with new or changed model files. | ||
| - If the files are located in the image specified in the Domain YAML file `spec.image`, |
There was a problem hiding this comment.
specified in the Domain YAML file -> specified in the domain resource YAML file
|
|
||
| - Change, add, or delete environment variables that are referenced by macros in your model files. | ||
| Environment variables are specified in the Domain YAML `spec.serverPod.env` | ||
| Environment variables are specified in the Domain YAML file `spec.serverPod.env` |
| or `spec.serverPod.adminServer.env` attributes. | ||
|
|
||
| {{% notice note %}} | ||
| It is advisable to defer the last two modification options, or similar Domain YAML changes to | ||
| It is advisable to defer the last two modification options, or similar Domain YAML file changes to |
|
|
||
| Use the following steps to initiate an offline configuration update to your model: | ||
|
|
||
| 1. Ensure your updates are supported by checking [Supported](#supported-updates) and [Unsupported](#unsupported-updates) updates. | ||
| 1. Modify, add, or delete your model resources as per [Updating an existing model](#updating-an-existing-model). | ||
| 1. Modify your domain resource YAML file: | ||
| 1. If you have updated your image, change `domain.spec.image` accordingly. | ||
| 1. If you have updated your image: | ||
| - If the files are located in the image specified in the Domain YAML file `spec.image`, |
mriccell
approved these changes
Jun 18, 2021
ddsharpe
approved these changes
Jun 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepare to release operator 3.2.4 as we have a number of important fixes ready for external and internal customers.