[YUNIKORN-1273] Add option to have unique application ids in a namespace

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.3.0
• Assignee: Mit Desai
• Reporter: Mit Desai
• Created: 01/Aug/22 22:12
• Updated: 08/Feb/24 05:14
• Resolved: 23/May/23 04:48

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

Issue Links

• relates to: YUNIKORN-2369 Using unique generated Application IDs breaks scheduling
• relates to: YUNIKORN-173 Generates one default application ID per namespace in the admission controller
• relates to: YUNIKORN-179 Allow changing app id generation via option
• links to: GitHub Pull Request #458
• links to: GitHub Pull Request #594
• links to: GitHub Pull Request #594

Sub-Tasks

• Document support for generating unique application id: Closed