Document Pod eviction

[sftim]

This is a Feature Request

What would you like to be added
Describe the concept of eviction:

• what this means in Kubernetes terminology
• API objects used to trigger an eviction (link to the reference docs?)
• document that eviction can be requested manually or it can be triggered by a controller.
  • mention some of the ways that automated eviction can happen

Why is this needed
I wanted to link to the documentation for eviction, only I couldn't really find a place to link to.

Comments
It's relevant to #4322 as well.

[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.

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

[sftim]

/priority backlog
/kind feature

[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

[sftim]

I still want this
/remove-lifecycle rotten

[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.

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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[sftim]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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.

[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.

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

[tengqm]

/remove-lifecycle stale

[sftim]

Also see #20728

/remove-lifecycle stale

[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.

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

[kbhawkey]

Leave open or close?

[sftim]

I'd definitely keep #20728

It does still seem useful to document the concept of eviction. @kbhawkey what do you think?

[kbhawkey]

👍
/remove-lifecycle stale

[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.

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-contributor-experience at kubernetes/community.
/lifecycle rotten

[tengqm]

/remove-lifecycle rotten

We do need some docs about the eviction feature and its API. There are some API specifics that needs attention.

[tomkivlin]

/assign

[tomkivlin]

I will prepare a PR. Current thinking of structure is along the lines of:

Explanation of what eviction means (or should this go in the Glossary?)

Section on automated eviction, the mechanisms that drive / effect this (e.g. PDB, pre-emption, QoS, resource starvation, etc.), and links to relevant APIs etc.

Section on manual eviction, the mechanisms that drive this (e.g. drain, cordon, etc.), and links to relevant APIs etc.

[sftim]

If you want, you can write a glossary entry and then use the glossary_definition shortcode to include the same text at a suitable point in a longer page.

[tomkivlin]

Thanks @sftim I'll give that a go, looks good.

[sftim]

/close

Done in #27739

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

/close

Done in #27739

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.