[
https://issues.apache.org/jira/browse/YUNIKORN-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822475#comment-17822475
]
Yu-Lin Chen commented on YUNIKORN-1351:
---------------------------------------
Hi [~ccondit],
Just updated the version 3.
* PDF: [Design Doc][v3] Define policy for when to use annotations vs
labels.pdf
([Link|https://issues.apache.org/jira/secure/attachment/13067200/%5BDesign%20Doc%5D%5Bv3%5D%20Define%20policy%20for%20when%20to%20use%20annotations%20vs%20labels.pdf])
* Google Doc:
([Link|https://docs.google.com/document/d/1lGaHI9gpgLsW_H0yp4KYzDSX77JcCpCuTC9AhnZUCWU/edit?usp=sharing])
Changes:
# Remove the AM configuration added in version 2.
# Note that YuniKorn should reject Pods with conflicting information.
> 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: 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
>
>
> 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]
