[
https://issues.apache.org/jira/browse/YUNIKORN-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YUNIKORN-1731:
-----------------------------------
Description:
After YUNIKORN-1306, we set user names on pods automatically. We also do this
for service accounts. Service account user names can look like this:
{{system:serviceaccount:namespace:myusername}}
Defining such a username in Yunikorn is not possible, because the config
validator rejects it. The same applies to groups
({{{}system:serviceaccounts{}}},{{{}system:serviceaccounts:namespace{}}},{{{}system:authenticated{}}},
etc).
was:
After YUNIKORN-1306, we set user names on pods automatically. We also do this
for service accounts. Service account user names can look like this:
{{system:serviceaccount:grp:myusername}}
Defining such a username in Yunikorn is not possible, because the config
validator rejects it. The same applies to groups
({{system:serviceaccounts}},{{system:serviceaccounts:grp}},{{system:authenticated}},
etc).
> Allow service account user names in filters
> -------------------------------------------
>
> Key: YUNIKORN-1731
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1731
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Peter Bacsko
> Priority: Major
>
> After YUNIKORN-1306, we set user names on pods automatically. We also do this
> for service accounts. Service account user names can look like this:
> {{system:serviceaccount:namespace:myusername}}
> Defining such a username in Yunikorn is not possible, because the config
> validator rejects it. The same applies to groups
> ({{{}system:serviceaccounts{}}},{{{}system:serviceaccounts:namespace{}}},{{{}system:authenticated{}}},
> etc).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
