Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better docs for garbage collection #4322

Closed
1 of 2 tasks
zacharysarah opened this issue Jul 7, 2017 · 41 comments · Fixed by #28870
Closed
1 of 2 tasks

Better docs for garbage collection #4322

zacharysarah opened this issue Jul 7, 2017 · 41 comments · Fixed by #28870
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@zacharysarah
Copy link
Contributor

This is a...

  • Feature Request
  • Bug Report

Problem

K8s docs discuss garbage collection in different articles:

Multiple topics show little to no awareness of each other.

Descriptions of garbage collection sometimes conflict.

No single article fully describes garbage collection as a concept or comprehensively demonstrates its implementation.

There is currently no task for garbage collection: only two concept articles and some incidental reference material.

Proposed Solution

  1. Consolidate conceptual content at https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/.

See Additional information for more details about conceptual content.

Explain garbage collection in Kubernetes as a whole: what it is; why and how different components (kubelet, kube-controller-manager) handle it separately; and interactions and dependencies between components' garbage collection functions.

Provide an end-to-end description of garbage collection in a typical production environment.

  1. Create a new task article.

Explain how to set up garbage collection in a typical production environment:
- Which components to configure, and in what order, for default function
- How to assess the health of garbage collection for a pod

Pages to update

Additional information

Different aspects of garbage collection appear to be handled by kubelet and kube-controller-manager. It's unclear from the documentation whether these components' garbage collection functions interact and the extent to which their functions are interdependent.

It's unclear which garbage control functions are available in which versions of Kubernetes:

Different topics' descriptions of garbage collection don't match:

Some of the most helpful material for understanding garbage collection mentions it only incidentally:

Multiple topics break the style guide by making statements about the future:

@zacharysarah
Copy link
Contributor Author

/cc @steveperry-53 for visibility

@zacharysarah zacharysarah added the P2 label Jul 7, 2017
@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2017
@nikhita
Copy link
Member

nikhita commented Jan 20, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2018
@zacharysarah zacharysarah added Actionable good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jan 23, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 23, 2018
@nikhita
Copy link
Member

nikhita commented May 4, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 4, 2018
@nikhita
Copy link
Member

nikhita commented Jun 8, 2018

Adding the help-wanted label as well, since it has good first issue.

/help

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 8, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 6, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 6, 2018
@fejta-bot
Copy link

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
Copy link
Contributor

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

@rskrishnar
Copy link

/reopen

@k8s-ci-robot
Copy link
Contributor

@rskrishnar: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

@rskrishnar
Copy link

@zacharysarah Is this still needed ?. I want to work on this.

@zacharysarah
Copy link
Contributor Author

@rskrishnar Great--feel free to create a PR!

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Dec 5, 2018
@k8s-ci-robot
Copy link
Contributor

@zacharysarah: Reopened this issue.

In response to this:

@rskrishnar Great--feel free to create a PR!

/reopen

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
Copy link

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
Copy link
Contributor

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 30, 2019
@sftim
Copy link
Contributor

sftim commented Aug 30, 2019

/lifecycle frozen

This is an important topic to cover

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 30, 2019
@nelvadas
Copy link
Contributor

nelvadas commented Aug 30, 2019

/assign @nelvadas

@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/kind feature
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 10, 2019
@Aut0R3V
Copy link
Contributor

Aut0R3V commented Jan 2, 2021

Hey guys is anyone working on this?

@sftim
Copy link
Contributor

sftim commented Apr 22, 2021

We should move https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/ to a new home. The other pages in this section are about resources you can create to manage a workload (eg CronJob, Deployment).

@sftim
Copy link
Contributor

sftim commented Apr 22, 2021

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Apr 22, 2021
@shannonxtreme
Copy link
Contributor

/assign

@shannonxtreme
Copy link
Contributor

Doc plan is here @sftim @zacharysarah please review, leave comments, and LGTM when ready or add other reviewers. Let's get the scope sorted before I dive into content :)

@sftim
Copy link
Contributor

sftim commented Jun 9, 2021

Maybe something to bring up in the SIG Docs Slack channel and / or during a SIG weekly meeting?

@shannonxtreme
Copy link
Contributor

CC: @jimangel

@shannonxtreme
Copy link
Contributor

Draft content for the concept topic is here, with questions: https://docs.google.com/document/d/1fEzX14PQy8jpvgAmx-Qkdd9R-2XMV8YRjRPJ1dLuoSU/edit?usp=sharing

@sftim
Copy link
Contributor

sftim commented Jul 7, 2021

@shannonxtreme that looks like a great starting point - feel free to open a pull request

@Goclipse27
Copy link
Contributor

@shannonxtreme - I have given some review comments. Kindly do the changes if it inches the docs ahead.

@shannonxtreme
Copy link
Contributor

@shannonxtreme - I have given some review comments. Kindly do the changes if it inches the docs ahead.

Noticed! I wish we could call it Waste Management, lol. Thank you for the reviews! Feel free to review the PR as well and give feedback.

@Goclipse27
Copy link
Contributor

What inspired me was dependent cleanup for resources, in PV/PVCs came across retain, reclaim and recycle (Deprecated). :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet