Update Garbage Collection Docs

[steveperry-53]

This is a...

• Feature Request
• Bug Report

Take a look at these two topics:

• Configuring kubelet Garbage Collection
• Garbage Collection

Are they redundant?
Do they belong under Concepts, or could some of this material be a Task?

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

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

[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
/remove-lifecycle stale

[tengqm]

My feeling is that the two pages should be remixed. We will still need a concept page because most of the garbage collection behavior are not controllable by a user but they need some high-level knowledge about the concept and how GC operations can be indirectly affected. We will need a task page dedicated to operators, for deeper involvement into the GC behavior tuning.

/remove-lifecycle rotten
/lifecycle frozen

[sftim]

/language en

[sftim]

In #15374 (comment), @jaypipes suggests a new page “Understanding object relationships”.

I like that idea so I'm mentioning it here.

[jaypipes]

@sftim are you interested in spearheading that effort in a new PR? or are you looking for an assist there?

[sftim]

Just wanting to track work that I think is worth doing. I don't particularly plan to pick this up myself.

[sftim]

/priority backlog

[sftim]

/triage accepted
/remove-label team/google

[k8s-ci-robot]

@sftim: The label(s) /remove-label team/google cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash

In response to this:

/triage accepted
/remove-label team/google

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]

This largely duplicates #4322

/triage duplicate
/remove-triage accepted

[k8s-ci-robot]

@steveperry-53: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

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/test-infra repository.

[sftim]

/close

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

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