It provides a true single-pane-of-glass experience for managing multiple Kubernetes clusters. Handling access control, deployments, and monitoring across different cloud providers and on-prem environments becomes much easier, since I don’t have to keep jumping between separate consoles. The built-in RBAC is also very straightforward to configure, which makes it simple to set up the right permissions for team members. Review collected by and hosted on G2.com.

Upgrades can be a bit of a headache sometimes. Occasionally after updating, you run into minor UI bugs or find that the documentation isn't completely up to date for the newest release, so you end up having to dig through GitHub issues for a workaround. The UI can also feel a little sluggish when you're managing a large number of clusters at once. Review collected by and hosted on G2.com.

It's a good product overall for orchestrating Kubernetes clusters, especially in larger organizations with many environments and development teams. The security governance is quite good and it is very easy to provide the right level of permissions to different teams. Review collected by and hosted on G2.com.

It can add operational complexity for the teams managing it, particularly when managing upgrades, integrations, and troubleshooting across large environments and at the same time it might feel "out of date" for platform engineers who are used to other more modern UX design. Some advanced configurations require deeper Kubernetes expertise. Review collected by and hosted on G2.com.

It’s open source, and it doesn’t lock you into anyone’s infrastructure. Rancher can manage clusters wherever they run - on bare metal, VMware, edge deployments with K3s, or imported EKS/AKS/GKE - so we were able to standardize how we operate Kubernetes without having to standardize on a single underlying vendor. Having SUSE’s enterprise support available on top of an open-source core is what helped it get through our internal approval process. The surrounding ecosystem (Longhorn, NeuVector, Harvester) integrates cleanly if you want it, and if you don’t, nothing is forced on you. Review collected by and hosted on G2.com.

We moved from kubeadm clusters built with Terraform and Ansible, and the main tradeoff is that some state now lives in Rancher instead of in our repo. The rancher2 Terraform provider covers a lot, but it still lags behind the UI, so we’ve ended up with a mix of declarative config and click-ops that we haven’t fully reconciled yet.

Fleet helps on the workload side, but debugging it can feel opaque. When a bundle doesn’t reconcile, the error shown in the UI often isn’t enough to explain what’s wrong, and we end up going back into the cluster with kubectl to figure it out. More detailed troubleshooting output in Fleet would save us a lot of time. Review collected by and hosted on G2.com.

Rancher gives me a single control plane to manage all my Kubernetes clusters, whether they run on-prem, in the cloud, or at the edge. Provisioning clusters, managing workloads, and setting up users takes minutes instead of hours, which lowers the barrier for developers who aren't Kubernetes experts. Review collected by and hosted on G2.com.

Rancher's management server and integrated components can be fairly resource-heavy. Keeping Rancher, the underlying Kubernetes distributions, and the managed clusters all in compatible versions requires careful planning, and a bad upgrade can be disruptive if you don't test it thoroughly first. The pace of change is a double-edged sword. Review collected by and hosted on G2.com.

The main advantage for us is getting a modern Kubernetes-based virtualization platform without the licensing costs and complexity associated with VMware or a full OpenShift platform. It has been a good fit for moving less critical workloads like development and lab environments away from VMware. Review collected by and hosted on G2.com.

The main thing I dislike is that there can be a bit of a learning curve when you're first getting used to it, especially if you're coming from more traditional virtualization platforms. Some areas of the UI could also be a little more intuitive, but overall it's been a good experience.

The API integration can be a bit more complex in some areas compared with VMware, especially when integrating with existing automation and tooling. VMware has a very mature API ecosystem, so there are cases where the integration feels more straightforward. SUSE is improving, but this is an area where I'd like to see more consistency and simpler documentation. Review collected by and hosted on G2.com.

Independence from Providers (No Vendor Lock-in) Simplified Application Distribution: Includes an App Marketplace/Catalog I like the UI with the ability to provide users to create our custom apps Review collected by and hosted on G2.com.

Uses quite a bit of HW resources Either use Rancher or deploy via argocd, it's necessary to choose It's an additional abstraction layer, where if the management cluster goes down or has synchronization issues, you don't lose the application workloads, but you temporarily lose the ability to manage them and coordinate access. Review collected by and hosted on G2.com.

What I like the most is how it simplifies Kubernetes management across multiple environments without sacrificing flexibility. It has a clean intuitive UI which makes managing clusters much less intimidating.

Rancher integrates seamlessly with major cloud providers and monitoring tools, making it easy to fit into existing workflows.

Performance has been solid even when managing multiple clusters, and the centralized management experience helps reduce operational overhead, making it into a meaningful ROI.

The onboarding process is relatively straightforward, supported by a knowledgeable team and the platform's automation, monitoring and policy management capabilities helps teams opearte more efficiently and mantain compliance as they scale. Review collected by and hosted on G2.com.

While Rancher offers a solid user experience overall, certain integrations may require additional configuration and expertise to fully optimize.

Performance is generally reliable, though the management layer can become resouce-intensive in more complex deployments.

Another thing is that its AI-driven insights and predictive intelligence features are not as advanced as some competing platforms that have invested more heavily in AI-powered operations. Review collected by and hosted on G2.com.

it provides a nice GUI for most of the daily operational scenarios which are needed for kubernetes management, comparing to the CLI, some administrators prefer GUI Review collected by and hosted on G2.com.

comparing to CLI, rancher is slightly slower in daily operation. and also we need mainten a separate platform just for kubernetes management, which can be a overhead Review collected by and hosted on G2.com.

SUSE Rancher provides a centralized platform for managing Kubernetes clusters, offering tools for deployment, monitoring, and troubleshooting. It streamlines operations with a user-friendly interface and built-in app catalog. Review collected by and hosted on G2.com.

I mainly use SUSE Rancher as a central dashboard to manage all Kubernetes clusters, which saves me a ton of time when deploying apps or checking logs. The single pane of glass UI for all the clusters is definitely the best part, making onboarding new team members and setting up their permissions much simpler than doing it manually. I really like how easy it is to open a shell directly into a pod right from the browser for troubleshooting. The built-in app catalog is great too, as it lets me deploy Helm charts with just a few clicks instead of messing with YAML files. The initial setup was pretty straightforward and didn't take our team more than half an hour to set up and connect a K8s cluster with it. Review collected by and hosted on G2.com.

What I like most about SUSE Rancher is how easy it makes managing Kubernetes across different environments. I can manage multiple clusters from one place without having to jump between a bunch of different tools. It’s flexible, but still pretty straightforward to use, especially when dealing with larger or hybrid environments. Review collected by and hosted on G2.com.

The main thing I dislike is that it can feel a bit complicated at first, especially if you’re new to Kubernetes. There are a lot of options and settings, and sometimes troubleshooting an issue takes more digging than I’d like. Once you get familiar with it, it’s fine, but the learning curve could definitely be smoother. Review collected by and hosted on G2.com.