Reorganize the "Well-Known Labels, Annotations and Taints" reference page

[mtardy]

This is a Feature Request

This follows the discussion that took place here.

What would you like to be added

• Add the missing "Used on" on entries.
• Specify the complete API group for the resources in "Used on" or reorganize the page into API group categories.
• Remove dependencies between reference entries (like this one with the "The taints listed below are always used on Nodes").
• Follow the style guide for API objects: use inline code format.

Why is this needed The Well-Known Labels, Annotations and Taints reference page is a bit messy at the time. The annotations are not all harmonized with the same template.

Also, new annotations in the kubernetes.io namespace are not targeting Kubernetes API objects. For example, annotations on the audit logs Event (from the audit.k8s.io/v1 API), see #31602 and #31576 for concrete cases.

Finally, there is a certain amount of deprecated labels, annotations and taints that could be moved into a dedicated category.

[sftim]

/triage accepted /lifecycle frozen /language en

[mtardy]

Aside: we might in future allow filtering the annotations / labels / taints, the way you can filter glossary entries.

Originally posted by @sftim in https://github.com/kubernetes/website/issues/31602#issuecomment-1060721579

[sftim]

reorganize the page into API group categories

Anyone up for this?

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[sftim]

/priority backlog

[natalisucks]

/triage accepted