Skip to content
New issue

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

fix: revert failed pods marked as NotReady #821

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

aslafy-z
Copy link
Contributor

@aslafy-z aslafy-z commented Jan 27, 2023

This reverts to what I think is the correct behavior.

GracefulNodeShutdown features (enabled by default with 1.21) terminates pods on nodes and set they phase to Failed. However, these are evicted and should not be taken as failures. See kubernetes/kubernetes#113278.

See details in the history:

Initial issue #215
Added #1
Reverted #70
Added #221
Reverted #296
Added #784

I guess this query could be enhanced to support these previous use cases, however, changing it like it was done previously alerts on default Kubernetes behavior.

revert failed pod marked as NotReady
Copy link

This PR has been automatically marked as stale because it has not
had any activity in the past 30 days.

The next time this stale check runs, the stale label will be
removed if there is new activity. The issue will be closed in 7
days if there is no new activity.

Thank you for your contributions!

@github-actions github-actions bot added the stale label Sep 14, 2024
@aslafy-z
Copy link
Contributor Author

This is still a thing

@github-actions github-actions bot removed the stale label Sep 17, 2024
@skl skl added bug Something isn't working keepalive Use to prevent automatic closing labels Sep 30, 2024
@skl skl requested review from skl and povilasv September 30, 2024 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working keepalive Use to prevent automatic closing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants