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.
There is no differential choice, the two products fulfill very different functions within the Company, since one is a platform as a service and the other is an infrastructure as a service, and it is a consumption at the choice of the clients.
When we evaluated PCF, it was just running application as containers. Managing applications and workloads were not that easy. Ecosystem wise PCF was quite small. Just few resources to create and manage. But Red Hat OpenShift was based on K8s, any k8s capabilities' will able to …
We have replaced our local Kubernetes with open shift entirely and it is by far the better product. Compared to Amazon Elastic Kubernetes Service, it can be more difficult to configure. We currently utilize both (open shift onsite and EKS remotely) and find advantages of …
They are all nice products, and they all have their place. But I'm convinced that from now on, instead of instantly just creating a Kubernetes cluster, I'm going to start seeing if Red Hat OpenShift is the best answer based on the project's overall needs. It's truly made that …
The other platforms are cloud based, and less relevant when you have to choose an on prem scenario. Red Hat OpenShift encapsulates Kubernetes and provides more, so that you have an all-in-one platform instead of dealing with various separate services. [Red Hat] OpenShift is …
OpenShift is more flexible and can be deployed On-prem and on the cloud. Openshift was easier for the development teams to get up to speed and understand k8 terminology.
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. …
Stateful pods and DBs can be challenging to manage in OpenShifts. Depending on the configuration, lost deployments could result in data loss. The best use case for OpenShifts is any instance where agile and quick deployments are needed. Thanks to the OCP git runner, we can implement new builds across all environments quickly.
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."
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
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.
I've not noticed any significant performance impacts with Red Hat OpenShift. I think the development team has put a lot of effort into ensuring that it is performant. And so performance typically is not a major concern for us with Red Hat OpenShift.
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.
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.
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
