Make OpenShift Container Platform Your Local Container Platform.
June 19, 2024

Make OpenShift Container Platform Your Local Container Platform.

Joshua Jordan | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Software Version

Red Hat OpenShift Container Platform (self-managed)

Overall Satisfaction with Red Hat OpenShift

We replaced our existing local Kubernetes container platform with the Openshift Container Platform. We now combine this platform with Jenkins (which is also running on the Openshift container platform) to automate code changes to all pods and applications. We also take advantage of the DevOps Console and logging to monitor all applications and the hardware underneath. This creates an agile, consistent, reliable, and fast platform for us to work with.

Pros

  • Highly Configurable/Customizable.
  • Redundant
  • Logging Visibility.
  • Deployment Automation.

Cons

  • Ease of configurability.
  • More detailed host metrics/logs.
  • Free support on the site.
  • Developer Speed/Code Deployment.
  • Application Scalability/Reliability.
  • Initial deployment required several upfront hours of configuration from 3 of our senior engineers.
OpenShift has drastically improved the speed at which we can deploy new code to our applications. We utilize Jenkins and give developers access to push new builds to our manifest files as an image tag. Openshift reaches out to our Nexus repo and deploys the pod without issue. Developers have also been given access to the console, which allows them to watch the deployment logs and address issues without engineer intervention. OCP has expedited this process and removed multiple manual steps.
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.
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 offsite, preconfigured, environments of EKS have been very helpful in expediting configuration. However, for development, nothing beats the local OCP environment.

Do you think Red Hat OpenShift delivers good value for the price?

Yes

Are you happy with Red Hat OpenShift's feature set?

Yes

Did Red Hat OpenShift live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Red Hat OpenShift go as expected?

Yes

Would you buy Red Hat OpenShift again?

Yes

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.

Red Hat OpenShift Feature Ratings

Platform-as-a-Service
8.2
Ease of building user interfaces
6
Scalability
10
Platform management overhead
7
Workflow engine capability
9
Platform access control
8
Services-enabled integration
9
Development environment creation
10
Development environment replication
10
Issue monitoring and notification
8
Issue recovery
7
Upgrades and platform fixes
6

Comments

More Reviews of Red Hat OpenShift

  1. Home
  2. Platform-as-a-Service (PaaS) Solutions
  3. Red Hat OpenShift Reviews
  4. User Review of Red Hat OpenShift