OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
$0.08
per hour
SUSE Rancher
Score 8.2 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…
I have worked with Kubernetes, which shares great similarities with Red Hat openShift, but in terms of ease of use, Red Hat is better as Kubernetes requires extra tools for completing certain tasks, which can be a little taxing sometimes. On top of it, Red Hat has built-in …
Some of the various other Kubernetes out there, including Rancher, is probably one of the biggest one. Rancher has a reputation for being very easy to implement. I've found that Red Hat OpenShift is just as easy to implement as Rancher. People just don't really know about it. …
Red Hat OpenShift is a more complete and integrated platform, with lots of out of the box components that the other platforms don't have, and customers need to stack lots of other software in order to have monitoring, cost management, log management, user policies governance, …
Kubernetes is powerful, but managing it yourself takes time. Red Hat OpenShift offers a user-friendly interface, built-in developer tools, and security features, all on top of Kubernetes. It simplifies management and gets you developing faster with all best practices and …
K3S supports constrained resource environments but does not have the governance controls needed for our company Rancher RK2 is being actively developed for constrained environments where Red Hat OpenShift is too heavy.
OpenShift offers a complete suite of plugins and services already set and configured. Saving time to connect with authentication services, monitoring, logs and CI/CD.
Red Hat OpenShift combines Kubernetes with additional features, streamlining management by avoiding the need to handle separate services.Enterprise. Users appreciate the blend of enterprise-grade support and community collaboration. Efficiency wise Some users find that Red …
I've seen multiple universities that have quite investments in Red Hat enterprise virtualization. They don't want to go with the VMware route due to the expense. So Red Hat OpenShift virtualization is a natural fit for them in that environment. I've also seen a lot of VMware customers that are not able financially to sustain the cost increases with the product. So they're looking for an alternative. And Red Hat OpenShift virtualization fills that need.
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.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
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.
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
The usability and user experience are good in general, although sometimes some errors can cause confusion, especially for those users who are not experts.
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Openshift performance is based on the underlying infrastructure, the K8s design, and the applications' design. Cloud-native applications should have resilience baked in and should not depend on infrastructure resilience. Standard stateful apps may still depend on the underlying infrastructure. It depends on the approach.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
Our developer community is using Red Hat OpenShift for years and they are familiar and comfortable with the product. Red Hat OpenShift UI makes it easier for new developers to adopt without knowing much of Kubernetes. Our platform team feels it’s easy to mange the cluster and upgrades. Other options has more operation overhead and less friendly to developers not have in-depth knowledge of Kubernetes.
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 connected our GitHub login with the Alfresco organization and that uses, in turn, Okta for SSO so provisioning for access is automatic for any developer who has been assigned to GitHub.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
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