Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Currently, if the appId is not explicitly specified (eg: non spark jobs), all the pods running in a namespace will be grouped together under a single application id that will be derived from the namespace.
Instead of forcing the pods to be clubbed under a single umbrella, we should have an option for the user to decide whether they would like to have multiple applications or group them together under a single application
Design Doc: https://docs.google.com/document/d/17H9FIBIR_p_AlLKFfcnoAlZAzTauBBiCKn0EbmdadH0/edit?usp=sharing
Attachments
Issue Links
- relates to
-
YUNIKORN-2369 Using unique generated Application IDs breaks scheduling
- Closed
-
YUNIKORN-173 Generates one default application ID per namespace in the admission controller
- Closed
-
YUNIKORN-179 Allow changing app id generation via option
- Closed
- links to