[jira] [Updated] (YUNIKORN-1351) Define policy for when to use annotations vs. labels

["Yu-Lin Chen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YUNIKORN-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yu-Lin Chen updated YUNIKORN-1351:
----------------------------------
    Attachment: [Design Doc][v5] Define policy for when to use annotations vs labels.pdf

> 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: Sub-task
>          Components: shim - kubernetes
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Yu-Lin Chen
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: [Design Doc] Define Usage of Labels and Annotations in YuniKorn.pdf, [Design Doc][v2] Define policy for when to use annotations vs labels.pdf, [Design Doc][v3] Define policy for when to use annotations vs labels.pdf, [Design Doc][v4] Define policy for when to use annotations vs labels .pdf, [Design Doc][v5] Define policy for when to use annotations vs labels.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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org