Glossary list of core objects is wrong about website HOT 8 OPEN

We should fix this.

/priority backlog
/triage accepted

from website.

/language en

from website.

PRs that cover just one entry at a time are very welcome.

from website.

/assign

from website.

In general, do the glossary categories correspond to the API categories? If they aren't, should they be so that new additions are easier to put into buckets? If they are, are we socializing that information well (like with comments in the source directory or style guide)?

from website.

We don't really have API categories.

https://kubernetes.io/docs/reference/kubernetes-api/ does have some categories, but (IIRC) this SIG and its tech leads at the time were keen to de-emphasize or drop them.

from website.

Putting APIs into categories or a taxonomy might be useful, but it makes work for maintainers that I think isn't justified by the value you get from it.

from website.

BTW I'm taking “core object” to mean “API kinds built in to Kubernetes”, and not “API kinds in the core API group”.

from website.