Red Hat OpenShift on IBM Cloud is a comprehensive service that offers fully managed OpenShift clusters, on IBM Cloud platform. It is directly integrated into the same Kubernetes service that maintains 25 billion on-demand forecasts daily at The Weather Company.
N/A
SUSE Rancher
Score 8.0 out of 10
N/A
Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
1. The pricing is better than the other competitors. 2. We are already using other services being offered by IBM, so it makes better sense to utilize the IBM cloud red hat open shift. 3. Support is also valuable. 4. security is good. 5. constant updates on clusters. 6. cloud …
Both have unique benefits for different uses. Docker is great for smaller projects on a single host or small cluster, whereas OpenShift is ideal when you need a scalable, fully managed, and secure Kubernetes platform. OpenShift also offers a more fully featured web-based …
Red Hat OpenShift on IBM Cloud is best when it comes to security capabilities and hybrid scenarios. With Red Hat OpenShift on IBM Cloud we could provision new environments very quickly and in cost effective way. Customers could also use the cloud credits that they might have …
Red Hat OpenShift on IBM Cloud is a container application platform based on Kubernetes, that leverages our ability to start very quickly any containerized application developed with different languages, plus CI/CD, monitoring and logging and security.
I prefer RedHat OpenShift because with kubernetes there are tons more installations and work effort required to get applications ready to run in the containerized environment. RedHat OpenShift is faster and easier to get up and running.
Planning to do so late. The evaluation for more vendors is in the cooking, pending budget approval & assignment to the right top guns. With the recession looming, I do wish that this key project could get approved & more discoveries could be made soon as I wished before.
We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been …
We are using IBM Cloud App ID as a simple method to get an OIDC provider for our applications, that are running within the OpenShift cluster. Also, IBM Cloud Object Storage is used within the workload to store data via an s3 compliant way. The IBM Cloud Container Registry is an …
Red hat Openshift had a better user interface by far. Amazon EKS's was so basic it was essentially useless. We had to use a separate tool called lens to get basic stuff done. Lens was buggy and didn't work as well though, even for basic functionality like updating a K8s secret.
For our particular use case, Red Hat OpenShift on IBM Cloud was very cost-competitive. We already had RHEL, OpenShift, and Ansible skills that translated to the service. From a feature and function perspective, most solutions have a parity but being open source and less chance …
For one of our banking clients, I have explored and played around the Kubernetes platform on IBM Cloud. In the process to deploy the application, I had to create the deployment artifacts, which was quite cumbersome. But then for one of the automotive clients I was asked to …
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re …
We started using SUSE Rancher in the early days and spent a large amount of time getting to know and love it. This was before the days of some of the likes of Amazon Web Services who may now provide a cheaper but less feature-rich alternative to SUSE Rancher, however we have …
DevOps Architect for Containerization Platforms and Microservices
Chose SUSE Rancher
That is the one of the greatest values of Rancher. You can choose to add new features and functionalities to your environment by implementing other projects from SUSE, but you not forced to. You can use Longhorn as Persistent Storage, but you can use any other i.e. VMware CSI, …
As we use only AWS EKS Clusters originally we were using the AWS Console and CLI but that is too limited in scope. Also, we were using AWS IAM roles to provide access to users but that was lots of extra work to have them integrated into SSO while on Rancher we have just …
I find SUSE Rancher easier to use and configure with the features I want to really use. I'm finding more people in the community to help in getting support for the product. The other competitors seem to lock you too much into their own ecosystems and keep many needed details …
lens installs locally and needs access (network) to the kube_api of the clusters. With Rancher, you need access to the rancher front end (UI / 443), and your clusters Kube API does not need to be exposed (even over a VPN or whitelisted ips). For security reasons, the rancher …
We were looking for an open-source solution for simply deploying and managing K8s on bare metal in both big and small environments. SUSE Rancher was the easiest to install. Rancher Kubernetes Engine (2) and K3s will give you just a plain simple Kubernetes environment. The …
RedHat OpenShift is not only suited for IBM Cloud but can run in ANY cloud. We installed in Azure Cloud, for example. It can also run on Linux servers or a Power 9 machine. It is built for multi-cloud or on-prem environments. IBM support provides such excellent guidance in the installation and configuration that no other product on the market can beat it.
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.
The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.
We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been freed up to focus on activities that are more valuable.
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re dealing with only one or a few Kubernetes clusters, using SUSE Rancher might introduce unnecessary complexity. This is where EKS wins, as its native cloud based abilities are better suited to scale, support higher complexity and larger demand.
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications