Tim Collins
Tim Collins
You have the option to do this with Argo CD by passing in the `skipCrds` flag even if the values file doesn't offer it (assuming you are using the `helm`...
We have received user reports that it's fine in Safari, but fails in Firefox. So maybe it's a browser-specific issue too?
I'll repeat my comment from #3191 I have concerns with this. Upstream does not include these permissions in their aggregate-to-* roles/clusterroles. So this should be addressed upstream first. I asked...
I actually don't know... which is a bit embarrassing. There doesn't seem to be anything in the codebase. The implication appears to be that you are supposed to roll your...
Potentially but I think you'd struggle to make it nicely templatable. Unrelated, but I have hopefully helped to clarify why aggregateRoles exist in this PR: #3193
Thanks for this, can you please address the PR title and the changelog? (basically the things in the tick list)
Cheers for the fix, but you have to do all the other things too I'm afraid (chart version bump, better PR title, changelog update etc etc)
I don't see this in the upstream clusterrole that the workflow-controller uses. https://github.com/argoproj/argo-workflows/releases/download/v3.5.8/install.yaml (cluster role starts on line 1016) In fact those permissions don't appear anywhere in the upstream yaml....
Hey @valibali. Any update on this? Thanks
Can you please raise an issue to help understand the use case for this addition? Assuming we all agree it should go in like this then docs will need updating...