SUSE Cloud Marketplace Program

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.

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

For our team, the biggest benefit has been reducing operational complexity and improving consistency across environments. It’s helped developers and admins work more efficiently, without needing to manage each cluster individually.

What do you like best about the product?

European distro that’s super clean, secure, and reliable.

What do you dislike about the product?

There are only a limited number of packages available in the distribution out of the box.

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

It was the main driver for our servers.

What do you like best about the product?

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.

What do you dislike about the product?

I find that SUSE Rancher struggles with performance in large environments.

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

I use SUSE Rancher for managing Kubernetes clusters at scale, which makes managing many clusters and switching contexts easier. It provides a centralized view with built-in RBAC and user management, enhancing my multi-cluster management capabilities.

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

SUSE Rancher helps solve the complexity of managing multiple Kubernetes clusters across different environments. It provides a centralized platform to provision, monitor, and control clusters, which reduces operational overhead and improves visibility. This makes it easier to enforce security policies, manage access, and streamline cluster operations for DevOps teams.

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

Problem it solves: Managing multiple Kubernetes clusters across different environments is chaotic without it.
Benefit: Rancher gives you one place to deploy, manage, and monitor all your clusters saving time, reducing errors, and making Kubernetes accessible to teams who aren't deep experts.