You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Amit Sharma (Jira)" <ji...@apache.org> on 2021/05/11 21:45:00 UTC
[jira] [Updated] (YUNIKORN-667) Update user label key using
helm-charts
[ https://issues.apache.org/jira/browse/YUNIKORN-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Sharma updated YUNIKORN-667:
---------------------------------
Description: User label key is customizable using defined in (was: Define user identity in pod labels and retrieve user identity info from the labels.
Few assumptions:
* All pods from one application are started by one same user
* Support the case where user label is not given, the default behavior should still work as expected
* Use pod label in order for easier querying & selecting
* Known security risk: malicious users may be able to impersonate others by injecting values to pod's labels. It is up to other layers in K8s to enforce the label can't be modified by users directly, e.g a mutation webhook.)
> Update user label key using helm-charts
> ---------------------------------------
>
> Key: YUNIKORN-667
> URL: https://issues.apache.org/jira/browse/YUNIKORN-667
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Amit Sharma
> Assignee: Amit Sharma
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.11
>
>
> User label key is customizable using defined in
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org