-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Correctly filter terminated pods in kubectl #48786
Conversation
/lgtm How about cherry-picking to 1.7/1.6 since this is a regression? |
/approve no-issue |
+1 to cherrypick |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, yujuhong Associated issue requirement bypassed by: janetkuo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/retest |
Automatic merge from submit-queue (batch tested with PRs 48672, 47140, 48709, 48786, 48757) |
Automatic merge from submit-queue (batch tested with PRs 48672, 47140, 48709, 48786, 48757) Correctly filter terminated pods in kubectl We shouldn't use `Status.Reason` to determine whether the pod has terminated or not.
It looks like the bug was introduced in 1.5.0. Should we cherrypick that far back? |
Oops looks like my page was out of date. :) @janetkuo What do you think about 1.5 though? |
Automatic merge from submit-queue (batch tested with PRs 46738, 48827, 48831) Add test for kubectl resource filter. This should prevent regression of the bug fixed in #48786.
Commit found in the "release-1.6" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
We shouldn't use
Status.Reason
to determine whether the pod has terminated or not.