[
https://issues.apache.org/jira/browse/YUNIKORN-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-1351:
-----------------------------------
Description: Currently, we have very inconsistent use of labels vs.
annotations in YuniKorn. Additionally, some values are namespaced under
yunikorn.apache.org while some are not. We will likely need to keep legacy
values around for backwards compatibility but we should define a strategy for
defining canonical representations of this metadata as well as a
developer-oriented pollcy around when to use labels vs. annotations. (was: For
most values we prefer the annotations above the labels when set on a pod. For
the queue we prefer the label. We need to make this consistent and always
prefer annotations. We also need to look at deprecating the labels and move
everything to annotations using the {{yunikorn.apache.org}} namespace.)
> Define policy for when to use annotations vs. labels
> ----------------------------------------------------
>
> Key: YUNIKORN-1351
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1351
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Yu-Lin Chen
> Priority: Major
> Labels: newbie, pull-request-available
> Attachments: [Design Doc] Define Usage of Labels and Annotations in
> YuniKorn.pdf
>
>
> Currently, we have very inconsistent use of labels vs. annotations in
> YuniKorn. Additionally, some values are namespaced under yunikorn.apache.org
> while some are not. We will likely need to keep legacy values around for
> backwards compatibility but we should define a strategy for defining
> canonical representations of this metadata as well as a developer-oriented
> pollcy around when to use labels vs. annotations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
