What do you like best about SUSE Rancher?
My first approach to Rancher were when I have almost 5 years of expertise in building and maintaining Kubernetes-based platforms at large enterprise scale (multiple cluster, tens of projects, 300 Namespaces, 500 applications developers and administrators, thousands of Business users and clients etc.)
What I noticed the most is how complete the vision of this product is. We also considered two other main market competitors of Rancher. From the great three, only Rancher has very soft dependencies with other SUSE products. You can choose to use them (for example: Longhorn, NeuVector, KubeWarden, Harvester) but you are not forced to do so to gain full functionality of Rancher.
Rancher is like Kubernetes on steroids: easy to install and learn, hard to master but have very high ROI. Some functionalities takes months to master, but will return that time when there is high Frequency of use of them in Day-2 operations (i.e. good configuration of some infrastructure providers takes months and requires implementing changes at infrastructure layer, but when finished gives possibility to create dozens of downstream clusters in minutes).
I love it's simple subscription model, as much as I cherish that it is fully open source. If you don't know what I mean then try to "install to learn" approach with two main Rancher's market competitors... it's not possible, the closest you get is "try and buy", yuck!
Rancher provides a very well documented REST API, so it can be easily integrate your services with it i.e. We have implemented self-service of Namespace lifecycle (create/quota mgmt/delete) that integrates Rancher's authentication and authorization model wth our corporate propetriary IAM solution. Review collected by and hosted on G2.com.
What do you dislike about SUSE Rancher?
Rancher has well-known roadmap with many functionalities planned, but some of them are neverending stories (i.e. We are waiting for "Projects 2.0" feature with implementation of hierarchical namespaces for over 1,5 year and it still will be available "soon").
Some internal modules are more mature than other. That is well seen on Rancher's drivers for different infrastructure and cloud providers.
Rancher is easy to implement within public cloud, but it's implementation in secure corporate air-gapped on-premise environment is uneven (some things are easy and well documented, some will bring one a lot of new grey hairs).
The multiple speeds of development of different Rancher's functionalities can lead to many breaking changes between releases, so administrators have a lot of work with every upgrade. Rancher is stable corporate-grade sofware, but every company that want to implement it at scale must have a very professional and well educated team of administrators and/or devopses.
That last but not least, the Customer Support is... the same as everywhere else in the world. Don't hesitate to open support tickets (that's the main reason you bought the subscriptions, right?), but also don't assume that they will resolve all of your problems in no time. Review collected by and hosted on G2.com.