Client Initiated Pod Termination Reason

[yguo0905]

Client Initiated Pod Termination Reason

• One-line feature description (can be used as a release note):
  A mechanism for specifying and delivering a signal to a Pod's containers indicating why the Pod has been terminated.
• Primary contact (assignee): @kow3ns, @yguo0905
• Responsible SIGs: sig-node
• Design proposal link (community repo): Initial commit of termination-reason proposal community#541
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @dchen1107
• Approver (likely from SIG/area to which feature belongs): @dchen1107
• Feature target (which target equals to which milestone):
  • Alpha release target (1.7): having all the design, API (alpha) and implementation finished.

[calebamiles]

Is kubernetes/kubernetes#45504, intended to implement this feature? If so it looks like it's going to miss the 1.7 release. Moving this feature to the next milestone, @yguo0905.

cc: @dchen1107, @kubernetes/kubernetes-release-managers, @kubernetes/sig-node-feature-requests

[yguo0905]

@calebamiles, yes, and we decided to move this to the next release. Thanks.

[calebamiles]

@yguo0905, is anyone planning to work on this feature for 1.8? If not perhaps we could close this issue to help reduce cruft.

cc: @kubernetes/sig-node-feature-requests, @kubernetes/kubernetes-release-managers

[yguo0905]

Yes, we are still working on it. The PR is pending review. We expect this to be in 1.8. Thanks for checking!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale