[YUNIKORN-521] Placeholder pods are not cleaned up even when the job is deleted

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.10
• Component/s: core - scheduler
• Labels: pull-request-available
• Target Version: 0.10
• Assignee: Kinga Marton
• Reporter: Ayub Pathan
• Created: 28/Jan/21 02:29
• Updated: 21/Jan/22 21:48
• Resolved: 16/Mar/21 18:39

Description

This one is a negative test...

• Create a namespace with quota
• Submit a job where the placeholder pods resource requests are more than queue quota.
• Delete the job using kubectl
• Still the placeholder pods are in running state occupying the resources.
  From an end user perspective, each job is an application consisting of all related pods. If the user decides to purge the job, Yunikorn should also recognize this action and clean up the placeholder pods.

From a yunikorn point of view, the application and job are 2 different entities. The placeholder pods are not cleaned up because the application is still alive even though the job is deleted. Does it make sense to create a one on one mapping for job and application? Once the lifecycle of job is complete, application should also terminate in Yunikorn world. Let me know your thoughts.

Issue Links

• is related to: YUNIKORN-519 Cleanup placeholders when the app is Completed
• links to: GitHub Pull Request #232