[Release 2.3.x] fix(e2e): don't rollout Pods on operator upgrade #5504
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
An IntegrationPod should not be rolled over during the operator upgrade
squakez
changed the title
gansheer
approved these changes
May 15, 2024
|
Given the investigation provided in #5491 (comment), I will revert partially these changes. |
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.
This PR is making sure that we use Integration status version and runtime version for environment variables. During upgrade process those parameter are not updated as the Integration digest is not changing either.
We cannot move this yet on main branch as there are other changes there affecting Deployment that would require additional attention.
Release Note