We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a test for #3520.
My current idea is:
replicas
deletionTimestamp
Without #3520, it’s possible for more than one Pod to have deletionTimestamp set.
No response
The text was updated successfully, but these errors were encountered:
cc @MortalHappiness
Sorry, something went wrong.
Since we’re close to the branch cut, it’s best to have a PR submitted within a week.
Hi @kevin85421 , may I try this?
kenchung285
Successfully merging a pull request may close this issue.
Search before asking
Description
Add a test for #3520.
My current idea is:
replicas
from X -> X - 1deletionTimestamp
set. With [Fix][Operator] Explictly wait for pod not found for satisfying the delete scale exectation #3520, only one Pod should havedeletionTimestamp
set.Without #3520, it’s possible for more than one Pod to have
deletionTimestamp
set.Use case
No response
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: