This message was deleted.
# general
a
This message was deleted.
f
Multiple Rancher instances is the one option...
e
Even so, when we add a new cluster we need to specify permissions for it
f
You can give global (instance-wide) permissions...
m
Or add them by code, same as adding cluster
e
We add them already via Terraform But the permissions is currently a static list of user group (we have SSO with Azure) to roles on each cluster If we could say for example that all the users in group
developers
will have read write access to dev clusters And all the users in group
qa
will have access to staging clusters, that would be great. I am not sure how to group the clusters and provide the permissions
m
If you created the cluster from a variable in terraform you maybe could have some kind of metadata there
e
The thing is that the clusters are created in a totally separate TF plan than where I'm defining the permissions
m
Could you it by some naming standard and figure it out that way?
When I do terraform stuff I usually use terragrunt to describe the different environments, then it's easy to add that kind of metadata