SUSE Rancher

We use SUSE Rancher as our central tool for orchestrating our Kubernetes landscape to enable standarization, governance, lifecycle managment and visibility.
By using SUSE Rancher we will get support for our Kubernetes landscape, which is no possible by just using open source, and reduce the complexitiy of setting up Kubernetes clusters.
We started with on-premise and extended to AWS EKS and plan to also add Azure AKS in future.

We need to run our Kubernetes-Clusters in an Air-Gapped environment and need the opportunity to manage all these clusters and also append new ones in short time.

We work with multiple clients and by the time we have multiple cluster hosted on multiple cloud platforms. It's very difficult to manage all those cluster manually or through cli tools. With Rancher we can easily create, upgrade and delete clusters in almost all the major cloud platform. One of the major issue was managing users and monitoring the cluster, Rancher helps us in that as well.

I am using Suse Rancher to manage Kubernetes system. This has a good Graphical user interface to Manage the Kubernetes Cluster. We are using the cloud environment for our Kubernetes configuration. It is good to have Rancher product which are easy to manage the Kubernetes solution. We have some web base application hosted on Kubernetes cluster & this is managed by Suse Rancher.

We use SUSE Rancher to run Kubernetes production workloads.
We chose Rancher because:
+) It's easy to manage users and their permissions.
+) It's the most complete Kubernetes GUI on the market.
+) Developers don't need to know kubectl cli and Kubernetes YAML syntax to start deploying workblows.
+) It's very easy to upgrade Kubernetes versions with just a few mouse clicks.

We needed a web dashboard software for our AWS EKS development clusters on Kubernetes with granular user access connected to our SSO and as we had been using in the past Rancher 1 successfully in pre-Kubernetes days it was good to investigate the new Rancher completely built for Kubernetes. The tool is invaluable and the user interface is so easy that also our more technically minded Product Managers can use it. It also unifies authentication for command-line access for kubectl and provides its own command-line tool for developers who prefer not to use the web interface.

We use SUSE Rancher to help us with the management of Kubernetes clusters and the management of our containers in several environments.

We started using SUSE Rancher to manage K8s clusters on bare metal. In the beginning, we mainly use it to deploy and upgrade new clusters. Then we noticed that the UI is a great feature to bring K8s to the customers. The UI gives you an easily understandable overview of all of your managed clusters. We didn’t find that feature with other software.

Customers of Datalounges build, maintain and manage cloud native applications on a variety of Kubernetes platforms. Often these are provided by hyper scalers such as Google and AmazonWeb Services. A small environment is easy for customers to keep under control, but as the use cases start varying and requirements for security, configuration management and more common ops-related problems arise, SUSE Rancher is introduced to the equation to maintain those platforms. Key use cases may include controlled delivery of apps from a trusted source and then their lifecycle or controlling the configurations of the Kubernetes environments to keep them similar enough over their lifecycle. Mainly it is a scaling thing though. Rancher provides a good basis for skilled engineers to automate and those with less experience to administrate in scale.

We use SUSE Rancher in our organization for managing our Production environment which consists of multiple K8s Clusters. We also use Rancher to set up our clusters in multi-cloud environments like GCP/AWS. We do user authentication & authorization via Rancher's support for AD & LDAP. We also use Rancher Desktop for for a simplistic way of looking into our prod environment.

The main use of SUSE Rancher has been to easily manage different Kubernetes clusters using different environments. One of the main advantages provided by this solution is its interoperability with different environments and cloud providers so that deployments are executed in a faster and more controlled way. In addition, thanks to the possibilities offered at the cluster management level, the process of adding high availability to the applications that are running are facilitated.

We currently use SUSE Rancher as a consolidated service for our Kubernetes developmental endeavors. We're relatively new to the platform so have been experimenting using it as a head piece for many of our existing systems. The more we become familiar with the functionality, the more we see opportunities to integrate our existing solutions and make them even better and easier to maintain.

We use SUSE Rancher to help us and others with the management of Kubernetes clusters and the management of containers. The UI gives a great overview of all clusters/software components--right now a unique feature. CLI is for more complex scenarios (really, really helpful)--especially when it comes to integration into existing environments/clouds.

We have two installations of Rancher (prod and non-prod). each rancher instance manages multiple clusters. We are using rancher to better enable users to interact with the clusters, get visual interactions for quicker understanding, and lower the barrier to adoption of the Kubernetes ecosystem. Our Kubernetes clusters and self-managed, and run on k3s. Rancher - fleet (which comes as part of the rancher installation) enables our deployments to follow the Gitops system. Deployments are managed by the feature teams, with versioning and audit of releases done via git. The ability to scale workloads, and get new developers to adopt is so much easier than having to upscale knowledge of CLI tools.