Keystone containers KEP

[adisky]

Enhancement Description

• One-line enhancement description (can be used as a release note): Terminate pods on the basis of keystone(main/app/essential) containers completion status.
• Kubernetes Enhancement Proposal: KEP-2872 Add keystone containers KEP #2869
• Discussion Link: https://kubernetes.slack.com/archives/C0BP8PW9G/p1620304727344300
• Primary contact (assignee): @adisky @matthyx
• Responsible SIGs: SIG Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.25
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[adisky]

/sig node

[adisky]

This KEP will be helpful in solving the blocking Job issue without making complex changes to pod lifecycle and kubelet code. We are planning to achieve with an annotation for alpha and depending on further feedback move it to pod API and proceed towards sidecar proposal

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[adisky]

/remove-lifecycle stale