Allow more addresses to be present in the upgrade bounce case #1960
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
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Co-authored-by: nicmorales9 <153320946+nicmorales9@users.noreply.github.com>
johscheuer
commented
Mar 11, 2024
johscheuer
deleted the
allow-more-than-expected-processes-in-upgrade-case
branch
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
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.
Description
We have seen a case in our nightly runs where one process was marked for removal but not yet fully excluded. I believe in such cases it's fine to have more addresses than the expected list, as it could take a while until a process is fully excluded,
Type of change
Please select one of the options below.
Discussion
Testing
Ran unit tests and CI will run e2e tests.
Documentation
Follow-up