Add a subresource for defining labels
radiohead opened this issue · comments
What
Add a new optional "labels" subresource (similar to the "metadata" subresource) that can be used to define labels which must always be present on each resource.
Why
We allow for custom metadata which is stored in annotations but the annotations cannot be used in filters. There are use-cases for custom labels which must always be present for filtering purposes but we don't offer any out-of-the-box tooling for that.