External reviews
130 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Rancher is a great tool to work
What do you like best about the product?
We can check the code deployed in various environments and also get thorugh the live logs and also we can check the config of every micro services
What do you dislike about the product?
It automatically gets logged out after some time
What problems is the product solving and how is that benefiting you?
I am able to check logs of every environment and helps me to catch live logs and container management is also very easy
Easing Kubernetes Management with Rancher
What do you like best about the product?
I like catalog of apps(appps and marketplace) feature it makes life easier by allowing us to install most of familiar opensource application into cluster with few clicks away
What do you dislike about the product?
As of now I don't dislike anything in rancher, but incase if I face any issue not liked when exploring more depply will update the same here
What problems is the product solving and how is that benefiting you?
As I tried it helps by providing tools to manage the resource allocation in the cluster and scaling option in the resource constraint environment which helps to manage the resource overall
Fantastico
What do you like best about the product?
I like the following things most about Rancher
1. It works with already existing tools like grafana and flientid
2. It maximizes the developer productivity
3. It has the ability to customize and extend its platform for specific use cases.
1. It works with already existing tools like grafana and flientid
2. It maximizes the developer productivity
3. It has the ability to customize and extend its platform for specific use cases.
What do you dislike about the product?
There nothing like I dislike about Rancher.
What problems is the product solving and how is that benefiting you?
The powerful UI and CLI helps us build complex workloads at scale by giving us easy access to Kubernetes environments.
Great opportunities matching my profile
What do you like best about the product?
Rancher is easy to use and crafted with a best user friendly UI, also it have very good customer support facilities, I frequently use it as it is very easy to understand and easy to implement .
What do you dislike about the product?
As of now I didnt found any downsides about Rancher .
What problems is the product solving and how is that benefiting you?
Rancher is very beneficial for Container management, also It handle the security for clusters as well,It give use option to integrate many tools with it .
Better tool to analyse logs and configuration
What do you like best about the product?
It's very simple User interface with lot of options to check pod instances and container logs and configuration. We can manage kubernetes namspace , workload and pod instances and can add more pod instances with plus option
What do you dislike about the product?
Not enough log if pod failure. We have to go to portainer to see the logs
What problems is the product solving and how is that benefiting you?
Application logs and pod configuration we can easily manage with rancher. We can create new instance and workload using UI of rancher
A great product for multi-cloud Kubernetes clusters
What do you like best about the product?
Robust integrations with K3S clusters, providing the most used features of K8s through a nice UI. Enabling you to configure, deploy and manage easily your K8s clusters.
Capable to handle several clusters and embedded public cloud drivers for easily add nodes, including good and secure user handling.
Deploy Rancher server is a simple task, very seamless deployment with minimal setup.
I used very often to check almost 10 K8s clusters handled by Rancher Server.
Capable to handle several clusters and embedded public cloud drivers for easily add nodes, including good and secure user handling.
Deploy Rancher server is a simple task, very seamless deployment with minimal setup.
I used very often to check almost 10 K8s clusters handled by Rancher Server.
What do you dislike about the product?
It doesn't come with DR/Backup tools, of course you can always use other software to complement.
What problems is the product solving and how is that benefiting you?
Handling multiple K8s clusters within a single pane of glass.
A Kubernetes based platform for service orchestration
What do you like best about the product?
Visual interface is very clear and allows to easily keep track of all running services and pods, as well as jobs or pods that have failed.
Quick commands allow to start, stop or restart services, while planning cronjob is also available.
Quick commands allow to start, stop or restart services, while planning cronjob is also available.
What do you dislike about the product?
Some setting pages are a bit confusing and some options could be grouped for clarity.
What problems is the product solving and how is that benefiting you?
Rancher allows to control our containerized cloud architecture all in one place.
Fastest way to have Kubernetes Cluster
What do you like best about the product?
The self managed kubernetes cluster that gets ready in minutes.
I can not only set my deployments but can pull or build my custom images to be used in deployments.
It gives access to all the master files allowing you to explore the cluster to its best .
I can not only set my deployments but can pull or build my custom images to be used in deployments.
It gives access to all the master files allowing you to explore the cluster to its best .
What do you dislike about the product?
The starting setup is a bit unclear but once your setup is ready it's all easy flowing.
What problems is the product solving and how is that benefiting you?
It's easy to setup and test your entire cluster before dealing it at production level.
Rancher helped a lot
What do you like best about the product?
Rancher desktop actually helped our organisation to move from docker desktop to containerd based solution. They give better UI and faster in provisioning pods.
What do you dislike about the product?
Kubernetes solution inside rancher is still k3s and need k8s based solution
What problems is the product solving and how is that benefiting you?
We have multiple local development environments and primarily focused on kubernetes based cloud deployment. Rancher has solved to have local development environments to all developers and move faster to kubernets
Rancher - Kubernetes-based platforms reimagined
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
Maintaining multiple very similar to each other Kubernetes clusters, within two main Rancher environments (non-production and production).
Time not consumed by repetetive Day-2 operations, we can spent on developing new functionalites of our Rancher-based platforms.
Time not consumed by repetetive Day-2 operations, we can spent on developing new functionalites of our Rancher-based platforms.
showing 51 - 60