SUSE Rancher Reviews & Product Details

I really appreciate SUSE Rancher because it cuts time for management, making it much faster than traditional CLIs from cloud vendors in addition to getting rid of cloud vendor issues. I find it incredibly easy to use and install, which is a big plus. Review collected by and hosted on G2.com.

When managing clusters from Azure and OCI cloud, SUSE Rancher has a lag issue. It seems to persist regardless of geolocation and internet connection. Review collected by and hosted on G2.com.

I like that SUSE Rancher simplifies a lot of our work with Kubernetes clusters and helps with maintenance. It really makes it easier to manage and monitor all the clusters from one platform. The interface is very good, allowing me to easily track the cluster's health and resources. Review collected by and hosted on G2.com.

I would work on better documentation and tutorials for beginners. This could solve problems when a new team member comes that don't know the platform. Review collected by and hosted on G2.com.

A central platform to manage your on-prem clusters. With RBAC, Fleet for bootstrapping clusters, and hardened images, it helps ensure you’re building secure apps. Review collected by and hosted on G2.com.

The pricing is quite high and hinders us from adding central cloud clusters, which can be managed through other means, to the Platform. Also, there could be better guidance on what prerequisites you need to deploy your clusters and the full suite, incl. the SUSE Observability. Review collected by and hosted on G2.com.

Cliché, but it really does offer a single pane of glass across all our clusters, giving us a quick view of our whole estate. It also provides centralized, role-based access control, which means we don’t have to configure access at a lower level. And it’s open source, too. Review collected by and hosted on G2.com.

As with most things Kubernetes, there’s a steep learning curve. Personally, I found the documentation a bit lacking. Given the overhead, in my mind it’s only worth considering if you manage a large number of clusters or if you frequently destroy and redeploy them. Review collected by and hosted on G2.com.

We used Rancher as part of a small POC to see how our microservices would behave in a Kubernetes setup. What stood out right away was how easy it was to move around the interface. Even for someone who isn’t deep into Kubernetes every day, it was straightforward to check what’s running, look at logs, and understand what’s healthy or not.

During the POC, we deployed a few basic services, including our Managed Microservices module and some integration‑related components. Rancher made it simple to see everything in one place instead of jumping between different tools or terminals. Review collected by and hosted on G2.com.

Some parts of the setup took a bit of figuring out, especially when we tried running Rancher on a local machine just to test things out. A couple of settings, like the built‑in cluster name, are locked down, so you can’t rename them the way you might want for a clean demo. It wasn’t a big issue, but it did slow us down at the start while we worked around it.

It should be a clean slate rather than fixing things up. When setting up initially or POC, I expected it to be guiding us rather than working on the stuff that's fixed. Review collected by and hosted on G2.com.

What I like best about SUSE Rancher is its centralized multi-cluster management. It allows teams to manage, monitor, and secure multiple Kubernetes clusters from a single interface, which greatly simplifies operations. The intuitive UI and strong RBAC features also make it easier for DevOps teams to control access and maintain governance across environments. Review collected by and hosted on G2.com.

One downside of SUSE Rancher is that the initial setup and configuration can be complex, especially for teams that are new to Kubernetes. Some advanced features also require a deeper understanding of Kubernetes concepts, which can create a learning curve for smaller teams. Review collected by and hosted on G2.com.

Vendor neutrality for sure. Our company uses different Kubernetes vendors and solutions, so it's nice that we can use SUSE Rancher to manage all of them. Review collected by and hosted on G2.com.

We had some troubles after some updates, causing some of our downstream clusters to become stuck in updating. Other than that, this is just a personal preference, but I'm not a huge fan of the UI. Review collected by and hosted on G2.com.

I like SUSE Rancher for its simplicity and easy Kubernetes management. It makes cluster management and troubleshooting straightforward. The initial setup was fairly easy, and I would highly recommend it to my colleagues. Review collected by and hosted on G2.com.

I would like better performance and a simpler user interface. Review collected by and hosted on G2.com.

I like SUSE Rancher's multi-cluster management because it helps me manage Kubernetes clusters at scale. I also appreciate the built-in RBAC and user management that provide a centralized view. The initial setup was easy as well. Review collected by and hosted on G2.com.

I find that SUSE Rancher struggles with performance in large environments. Review collected by and hosted on G2.com.

Rancher's best feature is its unified multi-cluster management. it lets you manage multiple Kubernetes clusters across any infrastructure (cloud, on-prem, edge) from a single, easy-to-use UI, which drastically simplifies what is otherwise very complex orchestration. Review collected by and hosted on G2.com.

Rancher's biggest downside is its complexity at scale. the setup and maintenance overhead can be significant, and when things go wrong, troubleshooting is often difficult due to the many moving parts. It can also feel resource-heavy for smaller deployments. Review collected by and hosted on G2.com.