Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Currently, we support queue/applicationID set in both label and annotation.
Queue
- queue [label] → If set, ignore annotation’s value
- yunikorn.apache.org/queue [annotation]
ApplicationID
- applicationId [label]
- yunikorn.apache.org/app-id [annotation] → If set, ignore label’s value
According to the new policy defined in YUNIKORN-1351.
We will add canonical representation to Queue/ApplicationId:
- yunikorn.apache.org/queue [label]
- yunikorn.apache.org/app-id [label]
Also align the ordering when fetch app-id/queue from pod:
app-id should be fetched in below order:
- Label: yunikorn.apache.org/app-id (New)
- Annotation: yunikorn.apache.org/app-id
- Label: applicationId
- Label: spark-app-selector
queue name should be fetched in below order:
- Label: yunikorn.apache.org/queue (New)
- Annotation: yunikorn.apache.org/queue
- Label: queue
Non-canonical format will be kept for backward compatibility.
However, If the same metadata (queue or applicationID) is specified in multiple locations and their values are inconsistent, the admission controller and scheduler should reject the pod. (Version 1.6.0 only prints out warnings; task rejection should occur in version 1.7.0.) This change is tracked by YUNIKORN-2810 and YUNIKORN-2811.
Please refer the changes in YUNIKORN-1351 for more details.
Attachments
Issue Links
- is related to
-
YUNIKORN-2810 Throw a warning if a pod has inconsistent metadata
- Resolved
-
YUNIKORN-2811 Reject task if a pod has inconsistent metadata in the shim
- Open
- relates to
-
YUNIKORN-2631 Support canonical labels for queue/applicationId in Admission Controller
- Resolved
- links to