[
https://issues.apache.org/jira/browse/YUNIKORN-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763199#comment-17763199
]
Craig Condit edited comment on YUNIKORN-1851 at 9/8/23 6:00 PM:
----------------------------------------------------------------
Thinking about the interaction with YUNIKORN-1961 a bit more... Maybe we can
relax the "no reuse of appID" restriction when the secondary pods come from the
same namespace as the original? This would fix the spark issue, and lines up
nicely with K8s permissions since the permission to create pods is
per-namespace. For ultra-strict environments, per-user namespaces could still
be utilized.
was (Author: ccondit):
Thinking about the interaction with YUNIKORN-1961 a bit more... Maybe we can
relax the "no reuse of appID" restriction when the secondary pods come from the
same namespace as the original?
> Don't allow similar app ids by different users
> ----------------------------------------------
>
> Key: YUNIKORN-1851
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1851
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
>
> YK allow different users to submit app with earlier used app ids because k8s
> allows this option for certain reasons (for ex, cron job etc). But allowing
> this option would end up in users abusing the system especially after user
> quota enforcement implementation.
> Hence we should detect this kind of app submission and allow only under
> certain circumstances .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
