Item: SUSE Rancher
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We use SUSE Rancher as our central tool for orchestrating our Kubernetes landscape to enable standarization, governance, lifecycle managment and visibility.
By using SUSE Rancher we will get support for our Kubernetes landscape, which is no possible by just using open source, and reduce the complexitiy of setting up Kubernetes clusters.
We started with on-premise and extended to AWS EKS and plan to also add Azure AKS in future.

Pros and Cons

Easy rollout of Kubernetes Clusters
Multi-Tenancy
Container deployment via Helm

Connection to cloud providers could be easier
The documentation could be more comprehensible
It would be nice to have best practices for the setup

Return on Investment

Faster provisioning of Kubernetes clusters
Enablement of standardized container deployment on-premise
Enablement of standardized container deployment in the cloud

Alternatives Considered

VMware Tanzu

While Tanzu has a deeper integration in an existing VMWare cluster, we decided for SUSE Rancher because of a more open approach.

Key Insights

Do you think SUSE Rancher delivers good value for the price?

Yes

Are you happy with SUSE Rancher's feature set?

Yes

Did SUSE Rancher live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of SUSE Rancher go as expected?

Yes

Would you buy SUSE Rancher again?

Yes

Likelihood to Recommend

Rancher is perfect if you have to manage multiple Kubernetes clusters, especially if you have to provide them for different teams with their own access rights and requirements. With Rancher we can provide such clusters on-premise, even in different sites, and in the cloud on different hyperscalers.
If you only have to manage one or some few Kubernetes clusters, it would surely be too much overhead to use Rancher.

Orchestrate Kubernetes everywhere

Software Version

Modules Used

Overall Satisfaction with SUSE Rancher