Openshift v4.X rave reviews compared to OpenShiftv3.x.
Overall Satisfaction with Red Hat OpenShift
We use and maintain OCP for CI/CD, and delivery of internal gov applications. We also deploy and maintain our own infrastructure applications in our OCP clusters.
Pros
- Build processes are quicker, so our app devs can expedite application deployment.
- Openshift serves as a great environment for collaboration and testing applications, prior to Production deployment.
- Upgrades on OCPv4.X are easy, quick, and seamless.
- Redhat constantly adds new feature sets on a regular basis.
Cons
- Certificate management and rotation could be more definitive, i.e., which certificates expire every 1 year, as opposed to every 2 years.
- Sometimes, rarely at best, we need to cycle our Thanos-querier pods due to an alert target firing in the alert manager.
- Early warning, pertaining to control plane issues, ie ETCD slowness, due to HUGE workloads. We do get alerts, but usually after the fact.
- We were able to decommission many VMs in our data center, once our application developers migrated their internal application workloads to OCP. This saved overhead, as per server administration.
- Our infrastructure management team has been able to work with more agility to support our developers.
- With the OCP platform, groups and namespace separation provide more security between applications and lines of business.
- Collaboration is more of a reality due to the DevOps philosophy, which OCP reinforces.
Openshift is less complex as far as implementation and deployment. Also, better support with RedHat.
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?
Yes
Did implementation of Red Hat OpenShift go as expected?
Yes
Would you buy Red Hat OpenShift again?
Yes
Red Hat OpenShift Feature Ratings
Using Red Hat OpenShift
30 - System administrators, application developers, infrastructure management.
2 - Knowledge of runtimes that support containerization, and application development/deployment. Internal networking knowledge is also needed.
- Application development and deployment.
- Continuous Integration.
- Agility, and the ability to achieve the same with a smaller workforce.
- In our production OCP environment, our applications run consistently for long periods of time without disruptions.
- A replacement for applications running on stand-alone VMs.
- Training and knowledge transfers on how runtime, orchestration tools, and containerization works.
- We don't have any new ways to integrate OCP at this point in time.
Evaluating Red Hat OpenShift and Competitors
- Scalability
- Ease of Use
Personally, our evaluation process was right on the money.
Red Hat OpenShift Implementation
- Implemented in-house
Change management was minimal
- No issues implementing v4.x at all.
Red Hat OpenShift Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Yes, as we are gov., we always need the highest level of vendor support.
Yes - Yes.
We tested the ETCD migration on OSEv3.X, and our cluster was dead. We worked with RHN support for nearly 20 hours straight to recover our cluster quorum with success.
Using Red Hat OpenShift
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using | Lots to learn |
- The installation of supplemental operators.
- The application build process, then deployment.
- UPGRADES!
- None, if you were unfortunate enough to have experienced OSEv3.x!
Comments
Please log in to join the conversation