This message was deleted.
# general
a
This message was deleted.
c
you cannot install multiple copies of rancher to the same cluster. it is a cluster management tool, and that includes managing the cluster it is deployed to
b
Hello @creamy-pencil-82913, thank you for answer my question. My goal is to have a dedicated cluster that manages access to other clusters. For the Rancher UI, I would like to have three separate domains, each one managing clusters in a specific environment (dev, stage, and prod). Do you have any ideas on how to achieve this, or does Rancher provide any built-in features that can support this use case? Thank you so much
c
you are not going to be able to do that with a single rancher installation
b
not clear much, so that mean i need 3 clusters that have 3 seperate rancher installation to manage 3 environments?
@creamy-pencil-82913 Please help if you have any idea for my case. Thank you!
h
You do not need 3 separate rancher installation for this.... How are you planning to do the authentication? ADFS/SAML etc? You can have single rancher "local" cluster. Setup authentication create 3 down stream clusters (from Rancher UI) where users workloads will be running one (dev/test/prod etc) then assign permissions to your users to those downstream clusters
c
You need separate installations if you want to separate the clusters by rancher server address. Rancher does not have the ability to scope or namespace clusters by the address used to access rancher. It doesn't even support multiple addresses - while you can of course route multiple things to it via DNS and ingress, rancher internally recognizes only a single address and will use that for all generated URLs.
1
c
If you want to limit physical resources involved, you can use K3k