Add more glossary terms

[chenopis]

This is a...

• Feature Request
• Bug Report

Problem:
Now that the revamped Glossary has been launched, we need to add more terms to the list.

Proposed Solution:
Add missing terms at Kubernetes doc sprints.

Here is the original glossary list from v1.5 Reference ToC:

• Aggregation Layer
• Annotation (@spzala)
• Certificate (@sdague)
• Cloud Controller Manager (CCM)
• Cloud Provider
• ConfigMap (@zachpuck )
• Container Environment Variable
• Container Lifecycle Hook
• Controller Manager
• Cron Job
• Custom Resource Definition (formerly Third Party Resource) (Cheryl)
• DaemonSet (Brad)
• Deployment
• Device Plugin
• Disruption
• docker (@jtborek)
• Dynamic Volume Provisioning (@mohamed)
• Etcd (Tina)
• Extension
• Federation
• Garbage Collection
• Horizontal Pod Autoscaling (@zhangxiaoyu-zidif)
• HostAliases
• Image (Chris)
• Ingress Resource
• Init Container
• Job (Ryan)
• kube-proxy
• kubelet (@spzala)
• Label
• Logging
• Name
• Namespace
• Network Plugin
• Network Policy (Radhika)
• Node
• Persistent Volume (Tina)
• Pod
• Pod Disruption Budget
• Pod Lifecycle
• Pod Preset
• Pod Priority
• Pod Security Policy (Radhika)
• Preemption
• Proxy
• Replica Set (Ivange)
• Replication Controller (Chris)
• Resource Quota (@radhikapc)
• rkt
• Secret
• Security Context (@erwbgy)
• Selector
• Service
• Service Account (@radhikapc)
• Stateful Set (formerly Pet Set)
• Storage Class
• supervisord
• Sysctls
• Taint
• Toleration
• Volume (Jared)
• Volume Plugin (@midoblgsm)
• fluentd (@radhikapc)

Page to Update:
Add YAML files to /_data/glossary/ directory using the format outline in /_data/glossary/_example.yml. They should then automatically show up in
https://kubernetes.io/docs/reference/glossary/?all=true

For example, /_data/glossary/cluster.yaml has this:

id: cluster
name: Cluster
tags:
- fundamental
- operation
short-description: >
  A set of machines, called nodes, that run containerized applications managed by Kubernetes.
long-description: >
  A cluster has several worker nodes and at least one master node.

A glossary definition can refer to other glossary terms. Here's /_data/glossary/deployment.yaml. The definition of Deployment uses {% glossary_tooltip %} to refer to the definition of Pod:

id: deployment
name: Deployment
full-link: /docs/concepts/workloads/controllers/deployment/
tags:
- fundamental
- core-object
- workload
short-description: >
  An API object that manages a replicated application.
long-description: >
  Each replica is represented by a {% glossary_tooltip term_id="pod" %}, and the Pods are distributed among the nodes of a cluster.

Kubernetes Version: v1.9

[Bubblemelon]

Third Party Resource has been deprecated. Custom Resource Definition now replaces it. https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-third-party-resource/

[chenopis]

I just added:

• Aggregation Layer
• Certificate
• Cloud Controller Manager (CCM)
• Cloud Provider
• Container Environment Variable
• Container Lifecycle Hook
• Controller Manager
• Custom Resource Definition
• Device Plugin
• Disruption
• Dynamic Volume Provisioning
• Extension
• Federation
• Garbage Collection
• HostAliases
• Init Container
• Label
• Logging
• Network Plugin
• Pod Disruption Budget
• Pod Lifecycle
• Pod Preset
• Pod Priority
• Preemption
• Proxy
• Selector
• Storage Class
• Sysctls
• Taint
• Toleration
• Etcd

[nikhita]

It would be nice to have a glossary for Custom Resources as well. Most users who search for CRDs would want to search for Custom Resources too.

[midoblgsm]

It would be nice to add Volume Plugin to the list.

[sftim]

I suggest: update the issue description with a new list that clearly shows what terms are missing.
(If it helps, I can draw up the list and then someone with edit access can paste it in).

[sftim]

Is it OK to skip terms for:

• Federation (deprecated)
• supervisord (not relevant to v1.15 cluster operators)

?

[sftim]

If the above 3 PRs get merged, I think it'd be OK to close this issue as implemented.

[sftim]

/priority backlog
because most of the work is done

[sftim]

/status active

[sftim]

All remaining work (that is listed) is already started
/remove-good-first-issue

[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

[sftim]

Also see #19535

[sftim]

@chenopsis is this OK to /close?

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

Related: #24528 Add object to glossary