Portainer.io
Replies: 2 comments 3 replies
-
|
Hi @woopla, Please make sure that the users/teams you want to assign to the Namespace have been given access to the environment itself. Go to Environments, select manage access and assign your teams/users then they will show there. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @Nick-Portainer, I see. Is there a way to "dereference" a group into its individual users without having to add all of them manually? Otherwise I don't see the value of a group 😉 In other words, I'd like to use the group (fetched from LDAP) to give access to resources automatically, but I'd like to be able to reference individual users that belong to these groups to when needed (such as this case). The users already have access to the resource, since they are in that |
Beta Was this translation helpful? Give feedback.
-
|
@woopla Good question. We currently support that for Docker containers where if the team is assigned to the environment, you can then select users from that team to select resources but Namespaces doesn't seem to support this. EDIT: |
Beta Was this translation helpful? Give feedback.
-
|
Could you revisit these design choices to make it possible, or at least less confusing to this user? |
Beta Was this translation helpful? Give feedback.
-
|
As of now, we are not looking at adding this as working around the limitations of Kubernetes to implement this requires a lot of engineering effort. |
Beta Was this translation helpful? Give feedback.
-
Ask a Question!
I'd like to create a user-specific namespace in Kubernetes. The namespace management page wont let me do that:
The only available option in the dropdown is for a group (called
big). The page and the docs mention users, so that should be possible, no?Beta Was this translation helpful? Give feedback.
All reactions