G2

Oleg P.

Senior DevOps Engineer

Mid-Market (51-1000 emp.)

8/18/2026

"Open-Source Kubernetes Management Without Vendor Lock-In"

4.5/5

What do you like best about SUSE Rancher?

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.

What do you dislike about SUSE Rancher?

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.

What problems is SUSE Rancher 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. Review collected by and hosted on G2.com.