vCenter Role to Deploy Rancher Management Cluster(s)

For manual (aka DIY) deployments, while we may use a vCenter administrator account, it’s better not to.

The Rancher documentation has a list of minimum vCenter privileges required for automated deployment of Rancher v2.5 ‘local’ (i.e. Management) cluster. Feel free to work by it or (as of v2.5.2) you can use PowerCLI to load this text file to your vCenter and save some time.

If you have a newer version of Rancher or vSphere, take a look at the Rancher documentation to see if anything has changed.

With the file you can use PowerCLI to create a Rancher deployment account with these privileges. See this (example to get started.)

SSO and Github

Rancher supports SSO and Github integration. Kubernetes cluster managers and users may need to be able to authenticate and get authorized against related endpoints (Active Directory, etc.)

---