[ https://issues.apache.org/jira/browse/YUNIKORN-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821820#comment-17821820 ]
Craig Condit commented on YUNIKORN-1351: ---------------------------------------- As an implementation detail, it's really vital that we query *all* the possible sources for each piece of metadata and reject Pods which have conflicting information. This can be done in the AM via rejecting the Pod definition entirely, and can be done in the scheduler by rejecting the task. > 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 > > > 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-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org