Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
DevOps Architect for Containerization Platforms and Microservices
Chose SUSE Rancher
That is the one of the greatest values of Rancher. You can choose to add new features and functionalities to your environment by implementing other projects from SUSE, but you not forced to. You can use Longhorn as Persistent Storage, but you can use any other i.e. VMware CSI, …
Verified User
Professional
Chose SUSE Rancher
While Tanzu has a deeper integration in an existing VMWare cluster, we decided for SUSE Rancher because of a more open approach.
Verified User
Administrator
Chose SUSE Rancher
SUSE Rancher has the most complete Kubernetes GUI.
As we use only AWS EKS Clusters originally we were using the AWS Console and CLI but that is too limited in scope. Also, we were using AWS IAM roles to provide access to users but that was lots of extra work to have them integrated into SSO while on Rancher we have just …
SUSE Rancher has a great GUI, and seems to be a little bit mor open than the competitors.
Verified User
Administrator
Chose SUSE Rancher
We were looking for an open-source solution for simply deploying and managing K8s on bare metal in both big and small environments. SUSE Rancher was the easiest to install. Rancher Kubernetes Engine (2) and K3s will give you just a plain simple Kubernetes environment. The …
Verified User
Director
Chose SUSE Rancher
I find SUSE Rancher easier to use and configure with the features I want to really use. I'm finding more people in the community to help in getting support for the product. The other competitors seem to lock you too much into their own ecosystems and keep many needed details …
Verified User
Engineer
Chose SUSE Rancher
lens installs locally and needs access (network) to the kube_api of the clusters. With Rancher, you need access to the rancher front end (UI / 443), and your clusters Kube API does not need to be exposed (even over a VPN or whitelisted ips). For security reasons, the rancher …
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
The usability and user experience are good in general, although sometimes some errors can cause confusion, especially for those users who are not experts.
As we use only AWS EKS Clusters originally we were using the AWS Console and CLI but that is too limited in scope. Also, we were using AWS IAM roles to provide access to users but that was lots of extra work to have them integrated into SSO while on Rancher we have just connected our GitHub login with the Alfresco organization and that uses, in turn, Okta for SSO so provisioning for access is automatic for any developer who has been assigned to GitHub.
The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications