Modified DomainInImage Upgrade usecase #2534
Merged
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
added 2 commits
September 10, 2021 19:55
…resource, instaed of hard-coded domain.yaml file
|
Just verifying: Note that this change did not remove the domain.yaml file. |
The file has been removed an earlier #2526 |
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.
Modified the DomainInImage usecases to
a) use k8s API to create domain resource, instead of hard-coded domain.yaml file
b) removed the commented Operator Release upgrade such as 2.5.0/2.6.0
Jenkin Upgrade Test
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6423/ ( Operator WLS upgrade)
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6424 ( All upgrade )