Cherry pick gracefulshutdown

[wgahnagl]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

allows pods to gracefully shut down

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

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 20902a8|Stop probing a pod during graceful shutdown: does not specify an upstream backport in the commit message
• 68f03a8|Implement shutdown manager in kubelet: does not specify an upstream backport in the commit message
• 6ddfa01|Promote kubelet graceful node shutdown to beta: does not specify an upstream backport in the commit message
• e78c797|Add systemd package to interface with dbus: does not specify an upstream backport in the commit message

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wgahnagl
To complete the pull request process, please assign sttts after the PR has been reviewed.
You can assign the PR to them by writing /assign @sttts in a comment when ready.

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

Hi @wgahnagl. Thanks for your PR.

I'm waiting for a openshift 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/test-infra repository.

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 149f5a6|UPSTREAM: 20902a88733 Stop probing a pod during graceful shutdown: does not specify an upstream backport in the commit message
• 38f99f3|UPSTREAM: 68f03a883fa Implement shutdown manager in kubelet: does not specify an upstream backport in the commit message
• 7e649e9|UPSTREAM: 6ddfa01f5d4 Promote kubelet graceful node shutdown to beta: does not specify an upstream backport in the commit message
• cfdeeb7|UPSTREAM: e78c7975d0f Add systemd package to interface with dbus: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 0da889f|UPSTREAM: #96129 Add systemd package to interface with dbus: does not specify an upstream backport in the commit message
• a54b4b3|UPSTREAM: #96129 Implement shutdown manager in kubelet: does not specify an upstream backport in the commit message
• bb08b19|UPSTREAM: #99735 Promote kubelet graceful node shutdown to beta: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1bc1d38|UPSTREAM: #96129: Implement shutdown manager in kubelet: does not specify an upstream backport in the commit message
• 3b18acb|UPSTREAM: #99735: Promote kubelet graceful node shutdown to beta: does not specify an upstream backport in the commit message
• 4db14c3|UPSTREAM: #96129: Add systemd package to interface with dbus: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could be automatically validated.

The following commits are valid:

• 0e3e3e3|UPSTREAM: 96129: Add systemd package to interface with dbus: the upstream PR kubernetes/kubernetes#96129 has merged
• 3df3fee|UPSTREAM: 99735: Promote kubelet graceful node shutdown to beta: the upstream PR kubernetes/kubernetes#99735 has merged
• 50d8049|UPSTREAM: 96129: Implement shutdown manager in kubelet: the upstream PR kubernetes/kubernetes#96129 has merged

[rphillips]

/ok-to-test

[wgahnagl]

/retest

[openshift-ci-robot]

@wgahnagl: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 0e3e3e3|UPSTREAM: 96129: Add systemd package to interface with dbus: the upstream PR kubernetes/kubernetes#96129 has merged
• 50d8049|UPSTREAM: 96129: Implement shutdown manager in kubelet: the upstream PR kubernetes/kubernetes#96129 has merged
• d7e0d9b|UPSTREAM: 99735: Promote kubelet graceful node shutdown to beta: the upstream PR kubernetes/kubernetes#99735 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 72be487|kubelet: Delete static pods gracefully: does not specify an upstream backport in the commit message

[openshift-ci]

@wgahnagl: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/verify-commits	d7e0d9b	link	/test verify-commits
ci/prow/unit	d7e0d9b	link	/test unit
ci/prow/verify	d7e0d9b	link	/test verify
ci/prow/e2e-gcp-upgrade	d7e0d9b	link	/test e2e-gcp-upgrade
ci/prow/e2e-aws-downgrade	d7e0d9b	link	/test e2e-aws-downgrade

Full PR test history. Your PR dashboard.

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.

[openshift-ci]

@wgahnagl: PR needs rebase.

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale