IBM Cloud Foundry vs. Red Hat OpenShift

IBM Cloud Foundry is a solid service from the IBM Cloud platform. It is easy to learn, and does not usually require you to make drastic changes to your existing applications. It is especially good for new applications that are cloud native, or micro-services, that can be easily updated and deployed. With its blue/green deployment, you can achieve 0 downtime for your customers.

Incentivized

Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.

Incentivized

• Intuitive user interface makes it easy for anyone to use, regardless of their professional background.
• A lot of the services integrate well with external platforms, APIs, and programs, not just IBM services. A lot of the competitors in this space lack this ability.
• Maybe it is just our contract in particular, but support and help is always made available.

Incentivized

• 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.

Incentivized

• Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
• Provide access to Postgres Database in Sydney datacentre for Australia.
• Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
• Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.

Incentivized

• 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."

Incentivized

This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications

Incentivized

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

Incentivized

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.

Incentivized

Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.

Incentivized

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

Incentivized

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.

Incentivized

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.

Incentivized

The learning curve is quite high but worth it.

Incentivized

IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.

Incentivized

We utilized the Thycotic Secret Service to manage all our application secrets, resulting in seamless integration with our applications. We developed all the applications using Red Hat Fuse (currently migrated to Quarkus). We used the built-in Kali Linux support of OpenShift to manage and configure the services and API. Additionally, the Red Hat Developer Studio facilitates faster development.

Incentivized

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

Incentivized

• This was the founding solution used to allow us to move in to and test out a cloud pipeline. This is what paved the way for a full production cloud solution to be possible.
• Having Cloud Foundry at the base of our development and sandpit environment, segregated away from our standard on premise solution has moved away red tape and ensured an agile way forward.

Incentivized

• It has allowed us to see where we need to be in the container world. I'm going to call it a net neutral impact, not negative or positive. It has given us a sense of what we are ready for and what we're not ready for. You know where you stand.
• You don't know what you don't know, so it helps us know what we want to know.

Incentivized