Add a new field maxRestartTimes to podSpec when running into RestartPolicyOnFailure

[kerthcet]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a new field maxRestartTimes to podSpec when running into RestartPolicyOnFailure
• Kubernetes Enhancement Proposal: WIP
• Discussion Link: Add max retries when pod's restartPolicy is RestartPolicyOnFailure kubernetes#65797
• Primary contact (assignee): @kerthcet
• Responsible SIGs:
  • sig/node
  • sig/apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.29
  • Beta release target (x.y): 1.31
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3322: add a new field maxRestartTimesOnFailure to podSpec #3339
  • 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.

[kerthcet]

/sig node apps

[kerthcet]

I think the goal of the KEP is clearly as the title describes, and the KEP is also on the way. Just want to make sure whether this feature will be accepted on top design.
/assign

[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

[kerthcet]

/remove-lifecycle stale

[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