Merge master into dev-1.22 to keep in sync

content/en/docs/reference/glossary/api-eviction.md

@@ -2,7 +2,7 @@
 title: API-initiated eviction
 id: api-eviction
 date: 2021-04-27
-full_link: /docs/concepts/scheduling-eviction/pod-eviction/#api-eviction
+full_link: /docs/concepts/scheduling-eviction/api-eviction/
 short_description: >
   API-initiated eviction is the process by which you use the Eviction API to create an
   Eviction object that triggers graceful pod termination.

content/en/docs/reference/glossary/finalizer.md

@@ -0,0 +1,31 @@
+---
+title: Finalizer
+id: finalizer
+date: 2021-07-07
+full_link: /docs/concepts/overview/working-with-objects/finalizers/
+short_description: >
+  A namespaced key that tells Kubernetes to wait until specific conditions are met
+  before it fully deletes an object marked for deletion.
+aka: 
+tags:
+- fundamental
+- operation
+---
+Finalizers are namespaced keys that tell Kubernetes to wait until specific
+conditions are met before it fully deletes resources marked for deletion.
+Finalizers alert {{<glossary_tooltip text="controllers" term_id="controller">}}
+to clean up resources the deleted object owned.
+
+<!--more-->
+
+When you tell Kubernetes to delete an object that has finalizers specified for
+it, the Kubernetes API marks the object for deletion, putting it into a
+read-only state. The target object remains in a terminating state while the
+control plane, or other components, take the actions defined by the finalizers.
+After these actions are complete, the controller removes the relevant finalizers
+from the target object. When the `metadata.finalizers` field is empty,
+Kubernetes considers the deletion complete.
+
+You can use finalizers to control {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}
+of resources. For example, you can define a finalizer to clean up related resources or
+infrastructure before the controller deletes the target resource.

content/en/docs/reference/glossary/garbage-collection.md

@@ -0,0 +1,24 @@
+---
+title: Garbage Collection
+id: garbage-collection
+date: 2021-07-07
+full_link: /docs/concepts/workloads/controllers/garbage-collection/
+short_description: >
+  A collective term for the various mechanisms Kubernetes uses to clean up cluster
+  resources.
+
+aka: 
+tags:
+- fundamental
+- operation
+---
+ Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up
+ cluster resources. 
+
+<!--more-->
+
+Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images),
+[failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection),
+[objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/),
+[completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources
+that have expired or failed.

content/en/docs/reference/glossary/kube-controller-manager.md

@@ -11,7 +11,7 @@ tags:
 - architecture
 - fundamental
 ---
- Control Plane component that runs {{< glossary_tooltip text="controller" term_id="controller" >}} processes.
+ Control plane component that runs {{< glossary_tooltip text="controller" term_id="controller" >}} processes.
 
 <!--more-->
 

content/en/docs/reference/glossary/kube-scheduler.md

@@ -2,7 +2,7 @@
 title: kube-scheduler
 id: kube-scheduler
 date: 2018-04-12
-full_link: /docs/reference/generated/kube-scheduler/
+full_link: /docs/reference/command-line-tools-reference/kube-scheduler/
 short_description: >
   Control plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.