The solution is scalable. If our bid is high, OpenShift will work right out of the box. For example, if my work is at about 80% capacity, OpenShift can automatically scale a new worker. We can scale down our infrastructure also if needed.

The scalability of OpenShift is good, but a competitor like VMware Tanzu can run more pods on the same system or the same hardware. So there's a little room for Red Hat to make it more scalable.

For us, OpenShift is an enterprise-level platform. We have about 10,000 users and we have plans to increase our usage.

Our clusters currently have between 32 and 36 nodes and we have had no scalability issues with OpenShift.

As OpenShift is on-premise, there's not much scalability from it. My team is still coming up with new clusters, and some clusters have been deployed as well, but my company isn't ready to scale OpenShift at the moment.

Scaling up and down is happening, but my concern is that if we hit any kind of bugs, the open-source community won't be that active in terms of doing the bug fixes. If I get any bug, there might be a delay in getting the bug release or the patch coming up. When I'm hosting an enterprise data application on an open-source product, I will have a little higher risk of non-availability, and that might lead to revenue impact as well. Keeping that in mind, I would like to go for the enterprise edition, at least for my high revenue-generating applications.

In terms of the number of people working with this solution, I have about eight administrators. I have eight people in my team who manage the complete Kubernetes cluster for me, which is a combination of OKD and Tanzu. It is being used on a daily basis.

The scalability is fine. We haven’t had any problems in that regard.

The main reason that we chose OpenShift rather than Azure or AWS was the scalability. It’s the best one on the market.

It's very scalable. We can see the cluster size we need. We can also scale down. So, scalability is good. The MachineSet feature in OpenShift is very good. It's user-friendly, and we can scale up and scale down as per our needs.

We have thousands of projects. So, many users are using this solution. We have around three production clusters and two development clusters. For now, we don't have any plans to expand its usage. Currently, the market is still in a stagnant state, and there is not any plan for expansion. If the number of users increases, we might increase the number of clusters.

OpenShift is a scalable tool; we have 100-200 users, primarily developers and DevOps staff.

It's also extremely scalable. On our dev cluster, we auto-scale from 50 nodes up to 130 on a weekend, when there is a need. It also scales itself down to save money over the weekend. When people start hitting it on Monday, it scales back up, seamlessly.

In terms of users, we have about 20,000 developers, all over the world. It's used 24 hours a day. We have centralized development clusters that are being used all the time because we have deployments on every continent except Antarctica.

We're moving off mainframes and monolithic apps into the containerized world. Increasing our usage is a stated management decision in our organization. OpenShift has been growing in our company in the last couple of years.

I would rate its scalability capabilities seven out of ten. More than three thousand users use it daily.

It's scalable for one cluster. When it comes to multiple clusters, it could be better. 

We have about 100 users who use this solution.

Scalability is a big plus. There is scalability from nodes to machines and so on. However, I would prefer more options on scalability based on statistics. That would be very interesting and very nice to see in the future.

Currently, we have less than 100 users who use this solution. They are mostly developers. There are also some end-users, assessors, architects, administrators, and project managers. The end-user experience is quite self-explanatory, and it's very important.

OpenShift is easy to scale. You just need to make sure you have the capacity to purchase and the number of nodes needed. Scalability only depends on your budget.

Currently, they are more than 10 users of OpenShift in the organization.

It is a scalable or expandable solution. Scalability-wise, I rate the solution an eight out of ten.

Eight members of my company's team use OpenShift.

Scalability-wise, I rate the solution an eight out of ten.

The cloud version is scalable. The solution's on-prem scalability can be improved. 

We are not yet using this solution in production so I cannot speak to scalability yet. 

We use OpenShift on a daily basis. We have one engineer for the operation and a pre-engineer for monitoring. Additionally, we have more than five to handle the daily work.

It is able to scale based on load.

OpenShift is scalable. It automatically scales.

We have found the solution to be very scalable during our time using it, and we now have a large number of transactions passing through the product.

The product is expensive to scale for smaller businesses in an on-premise environment. They can instead opt for a public cloud setup. The enterprises that can afford the cost should only opt for it if they have a specific use case or want to transform applications.

This is a scalable solution. 

The product is scalable. 

We have 100 or hundred users on the solution right now in our organization. Most are developers. Some are end-users. There might be a handful of admins as well. 

It is very scalable. We have deployed approximately 30 plus apps with the help of OpenShift. We require one senior system engineer for maintenance. We plan to increase the workload on OpenShift once we get a staging environment.

It's pretty scalable because of the architecture. I don't see any issues in terms of scaling up or across. During our design phase, we had to scale across and as far as the design was concerned, it was pretty easy.

We can also scale it back. We can reduce or expand as per our needs.

In the future, it will be used by our entire bank, with between 8,000 and 10,000 users. 

We intend to expand the usage but we have to wash our hands of the core banking system first, which itself is a huge system. Once we're done with that, we'll think about other applications.

The solution is very scalable.

The scalability of OpenShift combined with Kubernetes is good. At least from the software standpoint, it becomes quite easy to handle the scalability through configuration. You need to constantly monitor the underlying infrastructure and ensure that it has adequate provisioning. If you have enough infrastructure, then managing the scalability is quite easy which is done through configuration.

We have approximately thousands of users using the solution. The business applications that we build, our customers use them regularly, this includes the banking and insurance applications.

We did not encounter any issues with scalability.

This is a scalable solution. 

The solution is easy to scale. Our organization plans to increase its usage for the next five years.

Scaling it is quite easy. We can scale to as many nodes as we want and scale down to as many nodes as we want. That is fast because we have an automated script in place to scale up and scale down the infrastructure. We are quite happy with the solution in that regard.

We had an issue with the default nodes configuration. Once we gave enough resources to it, it's been fine.

ITOps Engineer manage scalability easily aligned with Client's resources and its SLA's thanks to native features found in this product.

No, OpenShift is imminently scalable. Easy to deploy more containers. Easy to deploy additional nodes. Automating dynamic scaling capabilities was trivial.

OpenShift is easy to scale.

I have not encountered any big issues with scalability, but the application must be designed for scalability.

There were no scalability issues, but only some Docker issues.

We did not yet encounter any issues with scalability but I am looking forward to our first "go day."

The product is able to meet most scalability goals.

Not at this moment (still running in dev/QA phase).

This is a scalable solution, we have around 40 users.