Presales Engineer at a tech services company with 51-200 employees
Real User
Top 10
Feb 17, 2026
My main use case for SUSE Rancher was majorly about container orchestration and microservices onboarding and deployments. I was working for a Telco with my previous organization where we used SUSE Rancher for container orchestration and microservices onboarding. This Telco wanted to deploy the Kubernetes solution at the edge as well as in the centralized location. The application was developed by a telecom solution provider and was supposed to be deployed on SUSE. We used Rancher K8s and K3s for deployment, and the application had a lot of small microservices to build to cover the end-to-end application. This was the major use case. The biggest project was the Telco deployment with SUSE Rancher, but there were some other projects as well. One was for a multi-Kubernetes management plane for a government entity here, where the customer was using multiple Kubernetes solutions across OpenShift, Tanzu, and native Kubernetes, as well as Google GKE. A single plane to manage everything was where we deployed SUSE Rancher. It was a small deployment, but the use case was significant. SUSE Rancher is deployed in various ways in my organization and my clients' organizations. For the Telco project, it was considered hybrid because there was edge involved and private cloud. The second use case was hybrid cloud as SUSE Rancher deployment was on-premise but had multiple clouds within their on-premise infrastructure including OpenShift, Tanzu, native Kubernetes, and GKE. In Saudi Arabia, all major deployments are locally deployed, primarily on top of VMware or bare metal solutions. While GKE and other cloud providers are integrated, Google is the only major player here right now as AWS and Azure are not available in Saudi.
Chief Executive Officer at a training & coaching company with 10,001+ employees
Real User
Top 20
Jan 5, 2026
My main use case for SUSE Rancher is managing multi-clusters, such as Kubernetes platform-based Kubernetes, GKE, AKS, and EKS. That was the main purpose. For managing those clusters with SUSE Rancher, let's say my client is looking for a deployment which needs to be tested on physical VMs just for checking, probably a development scenario. For dev, from SUSE Rancher itself, I can simply select a development scenario and it goes to that particular cluster. I can push that to prod easily using SUSE Rancher itself in a single dashboard from a single location. As the main use case with SUSE Rancher, I do not have anything else to add.
My main use case for SUSE Rancher is to manage the cluster in the GUI instead of looking at the master nodes. I use SUSE Rancher to monitor all health checks for a Kubernetes cluster, including nodes, pods, and failed jobs. I also use it for Prometheus rules that I define from time to time in the SUSE Rancher GUI. This is my daily task. I handle the basic components for the cluster there and I check the logs for each pod and each node. All of my troubleshooting is performed in the SUSE Rancher GUI.
Research Engineer at a educational organization with 10,001+ employees
Real User
Top 5
Feb 26, 2025
My primary use case for SUSE Rancher is managing Kubernetes clusters, allocating them to different users, and monitoring workloads. I manage all cluster-related activities through Rancher.
We are working with Rancher Desktop to run Kubernetes on local machines for testing and development purposes. We also conduct POCs to explore how our APIs will work before publishing them to Kubernetes.
SUSE Rancher manages and deploys Kubernetes clusters, simplifies container orchestration, and enhances DevOps practices, supporting multi-cloud environments and facilitating application scalability and monitoring.
SUSE Rancher provides robust Kubernetes cluster management and seamless integration with different tools and platforms, making it valuable for complex cloud infrastructures. It aids in automating workflows, ensuring consistent application performance across environments, and...
My main use case for SUSE Rancher was majorly about container orchestration and microservices onboarding and deployments. I was working for a Telco with my previous organization where we used SUSE Rancher for container orchestration and microservices onboarding. This Telco wanted to deploy the Kubernetes solution at the edge as well as in the centralized location. The application was developed by a telecom solution provider and was supposed to be deployed on SUSE. We used Rancher K8s and K3s for deployment, and the application had a lot of small microservices to build to cover the end-to-end application. This was the major use case. The biggest project was the Telco deployment with SUSE Rancher, but there were some other projects as well. One was for a multi-Kubernetes management plane for a government entity here, where the customer was using multiple Kubernetes solutions across OpenShift, Tanzu, and native Kubernetes, as well as Google GKE. A single plane to manage everything was where we deployed SUSE Rancher. It was a small deployment, but the use case was significant. SUSE Rancher is deployed in various ways in my organization and my clients' organizations. For the Telco project, it was considered hybrid because there was edge involved and private cloud. The second use case was hybrid cloud as SUSE Rancher deployment was on-premise but had multiple clouds within their on-premise infrastructure including OpenShift, Tanzu, native Kubernetes, and GKE. In Saudi Arabia, all major deployments are locally deployed, primarily on top of VMware or bare metal solutions. While GKE and other cloud providers are integrated, Google is the only major player here right now as AWS and Azure are not available in Saudi.
My main use case for SUSE Rancher is managing multi-clusters, such as Kubernetes platform-based Kubernetes, GKE, AKS, and EKS. That was the main purpose. For managing those clusters with SUSE Rancher, let's say my client is looking for a deployment which needs to be tested on physical VMs just for checking, probably a development scenario. For dev, from SUSE Rancher itself, I can simply select a development scenario and it goes to that particular cluster. I can push that to prod easily using SUSE Rancher itself in a single dashboard from a single location. As the main use case with SUSE Rancher, I do not have anything else to add.
I use SUSE Rancher for managing containers in logistical applications.
My main use case for SUSE Rancher is to manage the cluster in the GUI instead of looking at the master nodes. I use SUSE Rancher to monitor all health checks for a Kubernetes cluster, including nodes, pods, and failed jobs. I also use it for Prometheus rules that I define from time to time in the SUSE Rancher GUI. This is my daily task. I handle the basic components for the cluster there and I check the logs for each pod and each node. All of my troubleshooting is performed in the SUSE Rancher GUI.
My primary use case for SUSE Rancher is managing Kubernetes clusters, allocating them to different users, and monitoring workloads. I manage all cluster-related activities through Rancher.
We are working with Rancher Desktop to run Kubernetes on local machines for testing and development purposes. We also conduct POCs to explore how our APIs will work before publishing them to Kubernetes.