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

How to restrict Argo permissions to specific namespaces within its cluster #3163

Open
atheiman opened this issue Feb 6, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@atheiman
Copy link

atheiman commented Feb 6, 2025

As a cluster owner, I want to make Argo available to development teams to use in the cluster. I want to restrict Argo to only have permissions in certain namespaces. Most of the docs seem to suggest giving Argo permission to manage all resources in all namespaces.

Is there any way built in to the helm chart(s) to not create any admin type highly permissive ClusterRoleBindings and instead only create RoleBindings in a given list of namespaces I want Argo to be able to watch and deploy to? If this is not built-in to the helm chart(s), is there a step by step guide of which ClusterRoleBindings I should drop and replace with RoleBindings in my list of namespaces?

Related helm chart

argo-cd

To Reproduce

Deploy argo-cd, it is super admin across entire cluster. I want to restrict to only RoleBindings within given list of namespaces, not ClusterRoleBindings everywhere

Expected behavior

Restrict Argo to only operate in a restricted list of namespaces

@atheiman atheiman added the bug Something isn't working label Feb 6, 2025
@atheiman
Copy link
Author

atheiman commented Feb 6, 2025

I am new to Argo, but after some more digging it looks like Projects may be able to solve this use case for me. I just have to be sure only cluster admins can manage Argo projects

https://argo-cd.readthedocs.io/en/stable/user-guide/projects/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant