Implement container restart policy rules

[yuanwang04]

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it:

• Introduces container restart rules to API;
• Implements container restart rules in kubelet;
• Adds unit and e2e test coverage for container restart rules

Which issue(s) this PR is related to:

KEP: kubernetes/enhancements#5307

Special notes for your reviewer:

The API shape is outlined in https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/5307-container-restart-policy#design-details and discussed in kubernetes/enhancements#5308

Does this PR introduce a user-facing change?

Added a mechanism for configurable container restarts: _container level restart rules_. This is an alpha feature behind the `ContainerRestartRules` feature gate.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/issues/5307

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[k8s-ci-robot]

Hi @yuanwang04. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[yuanwang04]

/sig node

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[lmktfy]

/hold

The current changelog entry incorrectly implies that enabling the ContainerRestartRules feature gate is a required action. Yes, you must enable it to use the new feature but we are not saying that all cluster admins must do that.
OK to unhold once that's clear, eg after making a change like this suggestion:

-Introduces container level restart rules in the API under feature gate `ContainerRestartRules`. Action required to turn on the feature gate to use container restart rules.
+Added a mechanism for configurable container restarts: _container level restart rules_. This is an alpha feature behind the `ContainerRestartRules` feature gate.

[aaron-prindle]

/remove-sig api-machinery

[msau42]

Thanks for making the changes quickly! I just have one wording comment.

[msau42]

/approve
for api review

[SergeyKanzhelev]

/approve
/hold for @haircommander 's lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: msau42, SergeyKanzhelev, yuanwang04

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• api/OWNERS [msau42]
• pkg/api/OWNERS [msau42]
• pkg/apis/OWNERS [msau42]
• pkg/features/OWNERS [SergeyKanzhelev,msau42]
• pkg/generated/openapi/OWNERS [msau42]
• pkg/kubelet/OWNERS [SergeyKanzhelev]
• staging/src/k8s.io/api/OWNERS [msau42]
• staging/src/k8s.io/client-go/applyconfigurations/OWNERS [msau42]
• test/compatibility_lifecycle/reference/OWNERS [SergeyKanzhelev,msau42]
• test/e2e/apps/OWNERS [msau42]
• test/e2e/feature/OWNERS [SergeyKanzhelev,msau42]
• test/e2e/node/OWNERS [SergeyKanzhelev,msau42]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[haircommander]

/lgtm
/retest

[haircommander]

/unhold

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f01d052fa0cf6821f65bc8df3a398b44196562c9

[k8s-ci-robot]

@yuanwang04: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-kind-alpha-beta-features	b34f878	link	false	/test pull-kubernetes-e2e-kind-alpha-beta-features

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-sigs/prow repository. I understand the commands that are listed here.

[SergeyKanzhelev]

/skip
/retest-required