As an author of Commodore components, operators and others, one easily can get lost when it comes to naming labels and annotations. Having a guide would be of help. It can:
speed up the decision process for defining label names.
prevent collisions and thus unintended side effects.
None conclusive list to be covered in that guide:
labels to be used on different Kubernetes objects (e.g. Deployments, Services, etc.)
labels to be used for matchSelectors (e.g. to make Prometheus picking up service monitors or alert rules).
As an author of Commodore components, operators and others, one easily can get lost when it comes to naming labels and annotations. Having a guide would be of help. It can:
None conclusive list to be covered in that guide:
See also https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/.