Set LTPA Job to match olapp leader's config #509
Merged
Conversation
This file contains 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
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.
Relating to WASdev/websphere-liberty-operator#568. This change covers the scenario when the LTPA Job config is outdated (i.e. pull secret ref or service account ref has changed) just before the LTPA Secret is created. In this case, the operator could potentially be waiting on an LTPA Job that might fail. Instead, the operator will react to this and restart LTPA generation once again matching the olapp spec (pullsecret/service account/etc.), lowering the risk of waiting on a failed Job.