We use it to host our integration …
Development environment creation (25)
Development environment replication (24)
Platform access control (24)
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Red Hat OpenShift, and make your voice heard!
3-Year Reserved Instance
1-Year Reserved Instance
Azure On Demand
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Starting price (does not include set up fee)
- $42 per month
Red Hat OpenShift Container Platform
- A Kubernetes platform on clients' own infrastructure designed with security in mind
- Build, deploy, and manage container-based applications consistently across cloud and on-premises infrastructure
- Full-stack automated operations to manage hybrid and multicloud deployments
Red Hat OpenShift Dedicated
- Professionally managed, enterprise grade Kubernetes
- Private, high-availability OpenShift clusters hosted on Amazon Web Services
- Delivered as a hosted service and supported by Red Hat
Red Hat | Microsoft Azure
- Enterprise-grade Kubernetes jointly managed by Microsoft and Red Hat
- Highly available Red Hat OpenShift clusters hosted on Microsoft Azure
- Delivered as a hosted service jointly engineered, operated, and supported by Red Hat and Microsoft
- It is way simpler than Openstack so it requires less number of employees.
- It can host both containerized applications and Virtual machines which makes it a great candidate to be a common infrastructure for both legacy workloads and new workloads.
- Easiness of deployment, we can deploy the full stack completely and hardened easier than other container products
- Used to host different workloads (CNF and VNF).
- Easy to scale on both the worker and the infra layer
- Infra nodes do not require subscriptions, which means we are only paying for our workload only, and no hidden costs.
- For Openshift to be perfect, Red Hat has to follow strict life cycle timelines (i.e. as Openstack), rather than postponing a release for a few days, which will make our life easier when we plan the patching
- For Openshift to be perfect, Red Hat has to follow a strict roadmap for instance Multus Support for ODF is in Tech Preview since Openshift 4.8 and we are always getting a promise that it will be supported in the next release and it is now Openshift 4.10 and it is not supported yet, that is complicating our design work.
- Openshift is great as a common infrastructure to host both CNF and VNF.
- As until now network segregation is not possible on ODF, and the storage traffic is using the public interface, it makes the Openshift with Hyperconverged Storage not meet our security guidelines, and we are using an external CEPH, but that makes the life cycle management is a bit complicated, as we need to have 2 life cycles one for Openshift and one for CEPH.
- Logs in Openshift 4.9 are not always clear, which is making the troubleshooting a bit complicated, logs require more content.
- Compatibility with most of the infrastructure providers (public or private clouds) and the installations methods
- User Exprience in the console and the integration between components
- The management of operators
- The separation on Dev Experience and Admin Experience in the console
- The observability stack still looks like it's separated from the rest of the console. Need to be more integrated like providing a feature that will make "easy" todo customize some dashboards
- The migration between versions in clusters that include a lot of operators sometimes is really risky because of the versions compatilbility
- Automated installation, upgrades, and life cycle management for every part of your container stack.
- Service mesh abstracts the logic of interservice communication into a dedicated infrastructure layer, so communication is more efficient, and distributed applications are more resilient.
- Consistent managed Kubernetes experience for on-premises and cloud-based deployments.
- You can only install OpenShift on a handful of operating systems, including Red Hat Enterprise Linux Atomic Host (RHELAH), CentOS, Fedora, and Red Hat Enterprise Linux (RHEL).
- OpenShift has a small community of developers, mostly from Red Hat. As a result, support for this product is limited.
- Because cluster logs on OpenShift are hard to understand, they are also challenging to manage.
- Out of the box package of tools and services for DevSecOps practices.
- Possibility to start small and then scale up.
- Very nice user interface.
- There should be a proper way to manage and view logs which will reduce overhead.
- Community support can be better.
- Documentation can be improved with best practices.
- Route registration is automatic
- Massive scaling opportunity , both horizontally and vertically
- Free Trial period
- More python and nodeJS nodes can be added
- Checking logs could be made simpler
- Not practical for small patch updates or deployments
On the other hand, if an issue occurs, it is very difficult to find the proper logs and the root cause of the issue immediately. It can be made more search friendly.
- Easy to manage deployments across public, private and hybrid cloud environments
- Simple and seamless experience with deploying cluster of business applications
- Ready made monitoring capabilities for PODS
- Automated deployments based on the business and development requirements
- Cost is somewhat on the higher side
- Documentation needs a lot of improvement and detailed information about certain functionalities
- Support is good, but more videos and small tutorials would be an added advantage
- it has a great user-friendly interface
- guaranteed scalability and flexibility
- having the Git repositories is great
- unexpected crashes that require a restart
- poor accessibility to log records
- technical support could be improved
- The same as many similar K8 vendor solutions, OpenShift provides a managed Kubernetes environment with advanced facilitative components built-in.
- It provides the life cycle management/monitoring toolset to help users better visualize and understand both the application and infrastructure environment.
- Provides the scaling and recovering mechanism to ensure the high resilience of the application.
- CI/CD pipeline integration following the DevOps concept.
- The monitoring feature is still not mature, at least not in satisfying our requirements.
- Logging is somehow tricky. We can not stream all log info in real-time. Maybe it is our setup issue because we only see a partial log. This is a very negative part of our evaluation.
- The installation and set up process is a little complex.
- Only has the Jenkins as the CI/CD.
- As long as we stay in the pre-built component suite it is fine, but if we want to add more 3rd party components into the portfolio it is not straightforward.
- Documentation is not sufficient and it is also hard to find troubleshooting info from a public forum, requiring the purchase of the professional service from RedHat, which will lead to bigger cost concerns.
- The auto-scaling setting is not perfect. It can not apply ad-hoc changes after the initial set up.
- Managing multiple container instances across different environments
- Allows real time tracing of logs
- Relatively simple UI which does not take much training to get used to
- There is a limit to how much logs can be viewed on the browser
- No feature to search the logs (like how it can be done on Splunk)
- Absence of graphical representation of CPU and Memory usage
- Deploying new applications is a breeze
- Excellent configuration and management controls through tools
- [The] development team can take control of its own hosting and scaling needs without the need for any other team's involvement (apart from the initial setup of course)
- The shift from v2 to v3 was a huge transition, and Red Hat [OpenShift] really failed at making this step easy for users - their documentation at the time was fairly lacking
- When things go wrong it can be hard to diagnose
We use it to host our integration platform. As [the] first step, we use its container orchestration capabilities.
It enables us to build applications using a choice of programming languages, frameworks, and application lifecycle tools.
It allowed us to switch our existing project environments from traditional virtualization to the containerized world without excessive costs.
- Very efficient support and very active community on the internet
- Very efficient and user-friendly UX and CLI
- Scalable, extensible
- Multi-platforms, multi-technologies
- Platform management made easy
- Very smooth learning curve
- OS log management could be improved (log reading can be tough)
- It's sometimes hard to follow the new features flow
[Red Hat OpenShift] is not suited for old windows server virtualization [or if] you have legacy heavy systems.
- Nice user interface
- Fine grained access control
- Easy way to shell into a running container
- Slow to adopt Docker features like multi stage builds
- Inconsistent with Docker build behavior
- No Redhat supported client libraries for k8 APIs to Redhat CRDs
- It's flexibility and enablement for DevOps and collection wide collabration.
- It has user friendly UI.
- Easy to manage the container architecture, provisioning containers and performing Health management checks all at a single click.
- Deploying containers across various frameworks and language is very easy.
- When you have several miocrservices, then creating an image for each microservices is costly in OpenShift.
- takes more time to configure.
- OpenShift product support can be improved.
Red Hat is less appropriate because there is no proper way to manage an view the logs which heavily increases our loads.
- Works on a bare metal environment.
- Auto route registration.
- Log management.
- Nicely supports Red Hat Enterprise Linux for worker nodes.
- Helps teams reach production faster and easier.
- Starter plan only supports one project.
- No native support for agents other than Jenkins.
- Easy to use interface.
- Free 1GB access on signup.
- It is considerably fast.
- When there is a failure while uploading a project it may take time to understand where the problem is coming from.
- SSL certification knowledge is required before deploying web projects.
- Difficult to check and understand logs.
2. Learning platform to cloud technologies / Computer Science / DevOps (e.g. kubernetes, minishift).
3. An experimenting / testing platform to test new services, functions, features.
4. As a showcasing platform, where staging working prototypes are presented to clients.
- Integrations (github)
- Latest versions environments (python, node, etc.)
- Scalabilty and extensibility
- Maybe more python and nodejs apps.
- Built on top of Kubernetes giving it a solid base to work with.
- Extensive API support allowing developers to extend the platform as needed.
- Built for security. For instance, containers are expected to run as a non-root user inside the container. If this is not the case, OpenShift complains and requires an explicit override to allow the container to run.
- There is a bit of a learning curve. Especially for how OpenShift expects code to be developed.
- Not for small deployments. OpenShift runs on Kubernetes and with that comes a fairly hefty server count requirement.
- LocalHost using Minishift, having your own PaaS locally
- Fast Build times
- Node Support
- .Net Support
- Runs on CoreOS
- Vertical Scaling
- Horizontal Scaling
- No Credit Card Needed
- Free Tier
- There is a steep earning curve
- More tutorials
- Openshift has an intuitive easy-to-use web interface as well as an OC client if you need to automate (oc stand for Openshift client).
- Openshift concepts are clear and well defined (pod, route, probe etc...).
- Fast, stable with an integrated monitoring tool that covers most the needs.
- I would like to use another CI tool instead of Jenkins.
- It would be useful to have a tool to apply global changes on all applications across all tenants at once.
- An integrated statistical module keeping historical data would be interesting.
It was helpful in these ways:
1) very easy to upload
2) Easy manuals are available
3) Easy troubleshooting
It was not only one application but multiple applications. I could deploy the applications with ease and use OpenShift for software as a service. Links were quite responsive and compatible with other SAAS as well. My DB was also always deployed on the cloud.
- Easy Deployment
- Proper Instructions
- I personally had never faced any problem deploying my applications
2) When the number of people involved is not more than 100 (provided you are using a free version).
3) Also, there is a minimum number of applications we can keep active at one time. So if you have to keep multiple applications on at a time it is not possible [to use] free Open Shift.
Previously, developers would have been limited to the languages and tools available to them, which restricted innovation. The speed at which environments can be created has enabled great creativity.
- Pre built cartridges, giving a huge range of software ready to go. Reduces the amount of time required to get up and running.
- Integration with GIT was an advantage, cloning the repo and making changes was straight forward.
- Speed, creating an environment in minutes, ready to deploy.
- Swapping between different Openshift accounts wasn't as intuitive as I would have imagined, although I doubt that the tool is primarily aimed towards front end developers.
- No work seems to be required in order to scale up.
- Free service when use is low.
- I love the ability to login with SSH!
- Data storage seems a bit costly in comparison with the other services, but maybe I am just cheap.
- Quick setup complete with pre-configured gears.
- Easy to manage modules and gears.
- Comes with a git repo.
- If my site doesn't get much traffic it goes offline sometimes, so I had to set up a service to ping my site frequently.
- Sometimes my site just goes offline randomly and I have to go restart my app.
From developing these applications, I have learned a lot about OpenShift. I really like their devops architecture such as using environment variables per environment for username/passwords, so no need to maintain extra properties files. I like their "hooks" that triggers builds when a code is pushed-in using GIT or you can customize the process how you like using OpenShift marker files. They also have support for Docker integration which makes it more worthwhile to integrate applications using OpenShift now.
- OpenShift is really designed well particularly from a developers perspective. I think as a developer myself I just want to pick my target app-server runtime and choose the cartridges I need using OpenShift and I can just deploy. If you are a newbie or want to try it out you can use the OpenShift public cloud and start from there.
- OpenShift Integration with Git makes it a attractive point. You can also use OpenShift marker files to control when to build and when to deploy after each check-in makes it convenient to customize the build and deploy behavior per environment.
- OpenShift and Docker integration makes it a very appealing choice.
- I would like to see a public cloud using OpenShift and Docker integration. I am not aware if this is already available now.
- I would like to see a tool that can help with extracting log files from the remote server like it being available on a Samba shared folder. And other applications that want to scan for keywords in the application log can check if there have been any errors or exceptions thrown by the application.