SUSE Cloud Marketplace Program

What do you like best about the product?

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.

What do you dislike about the product?

When managing clusters from Azure and OCI cloud, SUSE Rancher has a lag issue. It seems to persist regardless of geolocation and internet connection.

What problems is the product solving and how is that benefiting you?

SUSE Rancher solves container management, image management, monitoring challenges, and reduces management time compared to CLI tools, boosting my efficiency. It cuts management time for k8 from different cloud vendors.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Rancher solves the problem of managing Kubernetes clusters scattered across on-prem, cloud, and edge from one place. With unified RBAC, policies, and monitoring, we enforce the same standards everywhere, which reduces misconfiguration risk and makes audits and compliance far easier to handle. Because Rancher is cloud-agnostic and open source, we run consistent Kubernetes across any provider and can shift workloads as needed, giving us negotiating leverage and long-term flexibility on cost.

What do you like best about the product?

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.

What do you dislike about the product?

I would like better performance and a simpler user interface.

What problems is the product solving and how is that benefiting you?

I use SUSE Rancher to simplify Kubernetes cluster management and troubleshooting.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Again, the vendor neutrality part is the best. We have some different Kubernetes solutions across the company, and it's nice that SUSE Rancher can handle them all.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

It solves the headache of cluster sprawl and fragmented Kubernetes management. Before using it, running multiple clusters across AWS, Azure, and on-prem meant juggling separate access controls, different monitoring setups, and nonstop context switching. Rancher brings all of that together under one roof.

For me, the biggest win is the huge drop in operational overhead. We can apply consistent security policies, manage user access through RBAC, and keep an eye on overall cluster health across environments from a single dashboard. It saves a lot of time on day-to-day maintenance and makes onboarding new team members much smoother.

What do you like best about the product?

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.

What do you dislike about the product?

I find version upgrades stressful because things sometimes break or get out of sync with downstream clusters. I also feel it is resource-heavy and can get kinda slow if I don't give it plenty of hardware.

What problems is the product solving and how is that benefiting you?

I use SUSE Rancher to manage Kubernetes clusters, saving time on app deployment and log checking. It simplifies tracking multiple clusters and permission setup with an easy UI, and lets me troubleshoot and deploy apps easily with built-in tools.

Recommendations to others considering the product:

To improve the experience, ensure that version upgrades are thoroughly tested to prevent disruptions. Consider optimizing resource usage to enhance performance, especially for larger deployments.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

SUSE Rancher gives us a central place to manage and operate our Kubernetes environments instead of having to manage each cluster separately. It makes day-to-day administration easier and gives us better visibility across clusters. It also helps us standardize how we manage Kubernetes while keeping the platform flexible and reducing the cost and complexity compared with some of the larger commercial platforms.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Kubernetes sprawl can quickly become a headache once you get beyond a handful of clusters. SUSE Rancher helps simplify things by giving you a single place to manage all your clusters.

What do you like best about the product?

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

What do you dislike about the product?

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

What problems is the product solving and how is that benefiting you?

The Rancher deployed in our organization is mainly aiming to solve the daily operation complixity, since rancher provides a single plane of glass in kubernetest deployment, operation and monitoring.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Before Rancher, every cluster was a kubeadm build stitched together with Terraform and Ansible, and most of the operational knowledge lived in a couple of people’s heads plus a repo full of playbooks. That approach works - until you need to onboard someone new, upgrade the control plane, or track down why one environment drifted from another.

Rancher gave us a consistent way to operate clusters across VMware, KVM, oVirt, and our hosted infrastructure: the same auth, the same RBAC, and the same view, regardless of what’s underneath. For a small team, the practical benefit is that day-two work stopped being bespoke on a per-cluster basis. Upgrades now follow a known path instead of a hand-rolled runbook, and the number of people who can safely touch production went from two to the whole team.