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.
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. …
I have used numerous products. I'm not going to tell you anything. Like I haven't seen anything, something comparable. Even if I got something compared, I'm not going to speak about it. Well, to the question you asked, I have worked on brands, VMware, Zu Cubes, Docker, swam, …
So I mean not anywhere near the same level, right? But we've looked at the Amazon solutions for it. The AWS solutions. There's one that I wasn't part of that I didn't really look at, so I guess I won't speak to that one. But AWS has been the only one that I've really looked at. …
It is unique due to its hybrid cloud support, integrated platform , DevOps integration. Reason for choosing Red Hat OpenShift for its magnificent features.
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 …
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, …
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.
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."
Leverage OpenShift Online constantly at both the free and paid tiers. While AWS is convenient, it often brings more administration than I want to deal with for a quick application (i.e. Drupal or Wordpress blog). OpenShift also simplifies the DNS registration and ability to share application environments with team members
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
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
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.
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.
