-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(argo-workflows): Add access to be able to see pod information #3191
fix(argo-workflows): Add access to be able to see pod information #3191
Conversation
…5.0 (argoproj#3184) Signed-off-by: Yorick <[email protected]>
…argoproj#3187) Signed-off-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com> Co-authored-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com> Signed-off-by: Yorick <[email protected]>
… runs the workflows (argoproj#3186) * feat(argo-workflows): allow additional rules for service account that runs the workflows Signed-off-by: fuyuan.chu <[email protected]> * Update charts/argo-workflows/templates/controller/workflow-role.yaml Co-authored-by: Aikawa <[email protected]> Signed-off-by: awx-fuyuanchu <[email protected]> --------- Signed-off-by: fuyuan.chu <[email protected]> Signed-off-by: awx-fuyuanchu <[email protected]> Co-authored-by: Aikawa <[email protected]> Signed-off-by: Yorick <[email protected]>
Signed-off-by: Tim Collins <[email protected]> Signed-off-by: Yorick <[email protected]>
…oj#3189) Signed-off-by: Marco Maurer <[email protected]> Signed-off-by: Yorick <[email protected]>
…oj#3190) Signed-off-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com> Co-authored-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com> Co-authored-by: Aikawa <[email protected]> Signed-off-by: Yorick <[email protected]>
Signed-off-by: Yorick <[email protected]>
Signed-off-by: Yorick <[email protected]>
Signed-off-by: Yorick <[email protected]>
027001d
to
ec2ea73
Compare
This seems to have more changes in than description suggests 🤔 |
# Conflicts: # charts/argo-workflows/Chart.yaml
I have concerns with this. Upstream does not include these permissions in their aggregate-to-* roles/clusterroles. So this should be 'addressed' upstream first. However, the argo server should be using the |
This PR wasn't properly set up. Sorry for the confusion. I made a new PR here: #3192 |
According to https://argo-workflows.readthedocs.io/en/latest/security/ UI users need access to pod(logs) to be properly displayed and updated in the argo workflows UI.
In this PR I added these to the view / edit / admin aggregate roles:
Checklist: