-
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
clear init container status annotations when cleared in status #46305
clear init container status annotations when cleared in status #46305
Conversation
@sjenning -- can we have a test? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need a test.
bug link should be https://bugzilla.redhat.com/show_bug.cgi?id=1453180 |
29b7b9d
to
e5312ea
Compare
e5312ea
to
86bc27b
Compare
@derekwaynecarr test added |
/lgtm |
@smarterclayton -- can you approve? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, sjenning, smarterclayton
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@k8s-bot pull-kubernetes-federation-e2e-gce test this |
@sjenning: The following test(s) failed:
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Automatic merge from submit-queue |
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. |
1 similar comment
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. |
When I pod with an init container is terminated due to exceeding its active deadline, the pod status is phase
Failed
with reasonDeadlineExceeded
. All container statuses are cleared from the pod status.With init containers, however, the status is being regenerated from the status annotations. This is causing kubectl to report the pod state as
Init:0/1
instead ofDeadlineExceeded
because the kubectl printer observes a running init container, which in reality is not running.This PR clears out the init container status annotations when they have been removed from the pod status so they are not regenerated on the apiserver.
xref https://bugzilla.redhat.com/show_bug.cgi?id=1453180
@derekwaynecarr