fix: Fix infinite resource updates due empty EnvVars #2804
Closed
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
Signed-off-by: Antonio Fernandez Alhambra <[email protected]>
|
closing this, atm the PRs should target main since there will be a release shortly, after the release from main, we will move again to next. |
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.
Fixes #2802
Not completely sure if this is the right branch for getting this into the next JOSDK release (backport is sent to
mainbranch)Seems the refactor/rename of the
ResourceRequirementsSanitizertoPodTemplateSpecSanitizeris not noticed properly in this PR by GitHub. Looks better to review in the backport PR #2803