Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: Now that the revamped 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 : [ ] Aggregation Layer [ ] Annotation ( [x] Certificate ( [x] Cloud Controller Manager (CCM) [ ] Cloud Provider [ ] ConfigMap ( ) [ ] Container Environment Variable [ ] Container Lifecycle Hook [x] Controller Manager [x] Cron Job [x] Custom Resource Definition (formerly Third Party Resource) (Cheryl) [ ] DaemonSet (Brad) [x] Deployment [ ] Device Plugin [ ] Disruption [x] docker ( [x] Dynamic Volume Provisioning ( [x] Etcd (Tina) [ ] Extension [ ] Federation [ ] Garbage Collection [x] Horizontal Pod Autoscaling ( [ ] HostAliases [x] Image (Chris) [x] Ingress Resource [x] Init Container [x] Job (Ryan) [ ] kube-proxy [ ] kubelet ( [x] Label [ ] Logging [ ] Name [x] Namespace [ ] Network Plugin [x] Network Policy (Radhika) [x] Node [x] Persistent Volume (Tina) [x] Pod [ ] Pod Disruption Budget [ ] Pod Lifecycle [ ] Pod Preset [ ] Pod Priority [x] Pod Security Policy (Radhika) [ ] Preemption [ ] Proxy [x] Replica Set (Ivange) [ ] Replication Controller (Chris) [ ] Resource Quota ( [ ] rkt [x] Secret [x] Security Context ( [ ] Selector [x] Service [x] Service Account ( [x] Stateful Set (formerly Pet Set) [x] Storage Class [ ] supervisord [ ] Sysctls [ ] Taint [ ] Toleration [x] Volume (Jared) [x] Volume Plugin ( [x] fluentd ( Page to Update: Add YAML files to directory using the format outline in . They should then automatically show up in For example, has this: A glossary definition can refer to other glossary terms. Here's . The definition of Deployment uses {% glossarytooltip %} to refer to the definition of Pod: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.9 <!--Additional Information:--
Third Party Resource has been deprecated. Custom Resource Definition now replaces it.
I just : [ ] 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 [x] Etcd
It would be nice to have a glossary for as well. Most users who search for CRDs would want to search for too.
It would be nice to add Volume Plugin to the list.
Label appears to already be to the glossary -
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
/remove-lifecycle rotten still some terms left
would the label suit here? this also looks like something new contributors could tackle! :) might be nice as well.
Yes, for sure. The glossary is probably the easiest thing to contribute to, especially for new contributors. =)
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale fejta-bot <:
I would like to have a glossary for Most users who search for setting up custom rules for namespace access also search for
I updated your list and these are the ones that still haven't been written yet [ ] Device Plugin [ ] Disruption [ ] Extension [ ] Federation [ ] Garbage Collection [ ] HostAliases [ ] Logging [ ] Network Plugin [ ] Pod Disruption Budget [ ] Pod Lifecycle [ ] Pod Priority [ ] Preemption [ ] Proxy [ ] Sysctls
I would like to work on this
/assign
GitHub didn't allow me to assign the following users: sourabh1031. Note that only and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I worked on adding HostAliases, Pod Priority, Extension and Preemption to the Glossary page, Please feel free to pick others.
/language en
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).
Is it OK to skip terms for: Federation (deprecated) (not relevant to v1.15 cluster operators) ?
If the above 3 PRs get merged, I think it'd be OK to close this issue as implemented.
/priority backlog because most of the work is done
/status active
All remaining work (that is listed) is already started /remove-good-first-issue
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Also see
is this OK to /close?
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Related: Add object to glossary

Discussion:
<ins> id: volume name: Volume full-link: kubernetes.io/docs/concepts/storage/volumes/ related: - pod - container - secret tags: - core-object - fundamental short-description: > A directory containing data, accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. long-description: > A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it. Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the {% glossary_tooltip text="pod" term_id="pod" %}, and data is preserved across {% glossary_tooltip text="container" term_id="container" %} restarts. </ins>