Skip to content
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

Closed

Conversation

yorickdevries
Copy link

@yorickdevries yorickdevries commented Mar 6, 2025

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:

- apiGroups:
    - ""
  resources:
    - events
    - pods
    - pods/log
  verbs:
    - get
    - list
    - watch

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the documentation according to documentation
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

@yorickdevries yorickdevries changed the title add access to be able to see pod information [Argo Workflows] Add access to be able to see pod information Mar 6, 2025
@yorickdevries yorickdevries changed the title [Argo Workflows] Add access to be able to see pod information fix(argo-workflows): Add access to be able to see pod information Mar 6, 2025
argoproj-renovate bot and others added 9 commits March 6, 2025 11:07
…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]>
…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]>
@github-actions github-actions bot added size/M and removed size/L labels Mar 6, 2025
@mbevc1
Copy link
Collaborator

mbevc1 commented Mar 6, 2025

This seems to have more changes in than description suggests 🤔
Could you please check changes files or update the description please?

# Conflicts:
#	charts/argo-workflows/Chart.yaml
@github-actions github-actions bot removed the argo-cd label Mar 6, 2025
@tico24
Copy link
Member

tico24 commented Mar 6, 2025

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 argo-server role/cluster role, which does already have these permissions anyway, so adding them is somewhat moot.

@yorickdevries
Copy link
Author

This PR wasn't properly set up. Sorry for the confusion. I made a new PR here: #3192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants