Red Hat Enterprise Linux (RHEL) Reviews

Our primary use case for Red Hat Enterprise Linux is as an operating system foundation for running a wide range of applications and workloads. It is commonly found on Linux workstations and is frequently used in conjunction with Kubernetes and containerization deployments.

Red Hat Enterprise Linux facilitates standardization, streamlining automation and general server usage. Its seamless integration with Ansible simplifies network and infrastructure automation, ensuring consistency across development and operations for a more efficient workflow.

The hybrid use of Red Hat Enterprise Linux has positively impacted our operations by providing flexibility in where we run our systems. Whether in the cloud or locally, the consistency of the platform simplifies management. Potential network restrictions may arise, but it has streamlined our processes overall.

Red Hat Enterprise Linux enabled us to centralize development and standardize our platform. This means all developers, regardless of their programming language, like C# or .NET, develop for the same Red Hat Enterprise Linux platform. This standardization allows us to run applications consistently across different environments, whether on the cloud or on-premises.

We use Red Hat Enterprise Linux with Podman for containerization. The combination of Podman and Red Hat UBI has significantly benefited our workflow, primarily due to the ease of use. Setting up Podman on other systems, such as Ubuntu, can be challenging because the installer from the Debian repositories sometimes has compatibility issues. However, on Red Hat Enterprise Linux, installing Podman with Yum is seamless.

Red Hat Enterprise Linux is lauded for its robust security, though its strictness can tempt automation engineers to temporarily disable certain measures for specific tasks, potentially leading to oversights in reactivating them. While these stringent security protocols can pose challenges for some users, they ultimately enhance the overall reliability and stability of Red Hat Enterprise Linux systems and their applications, making them a worthwhile trade-off.

Containers built on Red Hat Enterprise Linux with Podman offer excellent portability, running consistently across various environments such as Kubernetes and other Linux distributions. While they run virtually anywhere, the containerization workflow on a Red Hat Enterprise Linux system is arguably more streamlined and user-friendly for professional use.

Red Hat Insights is an excellent tool for addressing urgent security issues, non-compliant settings, and unpatched systems. It provides a clear understanding of areas for improvement and existing vulnerabilities within an organization, enabling a focused approach to remediation and enhanced security.

While Red Hat Enterprise Linux offers robust security, the complexity of some security features can be a challenge when automating tasks. Nevertheless, I highly value its security measures, along with its user-friendliness, virtualization capabilities, and ease of deployment and automation.

To improve standardization, deprecate YUM and transition to DNF. While backward compatibility is necessary, a decision to move to DNF was made two years ago. Run both in parallel for a period, then drop YUM or limit it to Red Hat Enterprise Linux eight, not nine.

I have been using Red Hat Enterprise Linux for ten years now.

Red Hat Enterprise Linux is highly stable.

The solution is highly scalable due to the interconnectivity between installations and the central management capabilities like the Red Hat Cockpit. It allows for seamless scaling across different environments.

Customer service is rated highly, with support available out of the box through the subscription. The support team assists with bugs and mitigation guidance, and knowledge base articles help resolve common issues.

Positive

The biggest return on investment includes built-in security, ease of machine setup, and consistency across all deployments. These features contribute to efficiency in development and operations.

While the cost of Red Hat Enterprise Linux may seem high, it's necessary to support Red Hat's extensive research and development, which includes maintaining long update cycles for the operating system. This cost, however, can create a barrier to entry for those new to the industry, making knowledge of Red Hat Enterprise Linux more exclusive. Despite this drawback, the price is ultimately justified by the benefits of using a stable and well-supported operating system.

I would rate Red Hat Enterprise Linux nine out of ten.

For small-scale or hobby projects, open-source cloud-based Linux is perfectly sufficient. However, for professional workflows in larger organizations, investing in a Red Hat Enterprise Linux license is recommended. This provides support, a more standardized development process, and enhanced features.

The impact on the TOC is minimal because many people are already accustomed to it. This is a benefit of Red Hat Enterprise Linux's standardization, as widespread familiarity simplifies ownership. However, platforms outside the Red Hat Enterprise Linux scope, such as Ansible Automation Platform or OpenShift Container Platform, require specialization and have their own ownership structures. In my experience, this doesn't necessarily expand ownership of the underlying Red Hat Enterprise Linux virtual machines.

I work for a consulting company, and we have many customers using Red Hat. They use it both on-premises and on the cloud for various applications, including enterprise applications and manufacturing certificates.

We selected Red Hat Enterprise Linux for our workloads due to its excellent support, enhanced stability, reliable update cycle, and strong community.

Red Hat Enterprise Linux has enabled us to centralize development and manage a hybrid model with on-premises and cloud deployments. It comes with built-in features that allow for efficient management of applications using tools like Ansible.

We use Red Hat Enterprise Linux for containerization projects, and one of our recent projects is in the manufacturing sector, specifically on the shop floor, where the latest MES software relies on containers. OpenShift is a valuable solution in this scenario, enabling the use of existing hardware. For instance, if a user already has a VMware hypervisor, they can deploy VMs, utilize them as worker nodes, and build an OpenShift cluster on top of that existing infrastructure.

Red Hat is used both on-premises and in the cloud. By enabling Red Hat Enterprise Linux VMs with Azure Arc, we gain a single management pane for both environments, allowing us to apply policies, check for compliance and vulnerabilities, and more. This unified approach simplifies management and enhances security across our entire infrastructure.

Red Hat Enterprise Linux has consistently performed well for our business-critical applications. Its stability is evident, as many trading applications rely on this Linux-based operating system globally. Red Hat Enterprise Linux is also widely perceived as more secure than other operating systems.

It offers robust built-in security features.

Red Hat Enterprise Linux, particularly with tools like Ansible, has significantly reduced risk in our environment. Ansible enables continuous deployment, streamlined patching, and efficient management of Windows and Linux VMs from a central location.

The portfolio helps reduce our total cost of ownership because our enterprise applications are typically based on its subscription model. This includes application support, vendor support, and other associated costs, making it a cost-effective solution.

Red Hat Enterprise Linux provides a stable operating system, and OpenShift enhances efficiency with a built-in Ingress controller, unlike some managed Kubernetes services.

There is a steep learning curve, especially for users from a Windows or GUI background, because of the command-line interface.

I have been using Red Hat Enterprise Linux for over ten years.

Red Hat Enterprise Linux has proven to be a stable operating system suitable for business-critical applications like trading applications worldwide.

Red Hat Enterprise Linux scales beautifully as our needs change.

The customer service is good, but there is room for improvement, especially in terms of continuity when handing over between support personnel.

Neutral

The stability of Red Hat Enterprise Linux, especially with OpenShift, provides a significant return on investment. The built-in Ingress and efficient management interfaces add to its benefits.

I would rate Red Hat Enterprise Linux nine out of ten.

Red Hat Enterprise Linux customers typically begin AI integration by experimenting with chatbots or virtual assistants to improve productivity. However, a comprehensive business case outlining the use case and value proposition is crucial to secure sponsorship and justify a more extensive implementation.

I recommend considering the support system and available resources when choosing an enterprise Linux distribution. Red Hat, for example, offers a vast partner ecosystem, certified applications, and a subscription-based support model. Its open-source nature, strong community support, and extensive field experience contribute to its popularity. Furthermore, Red Hat's large developer base and significant code contributions demonstrate its wide-reaching impact and robust development.

We have RHEL running on our machines, which handle extensive computing tasks and data analysis. The team is responsible for managing the operating system and virtual machines that host various applications run by developers. My department doesn't use containerization, but other departments do.

Red Hat's security patches and standard compliance ensure risk management and continuity.

Red Hat Enterprise Linux helps us reduce risks in our environment through operating system patches. In my previous job, we ran baselines through Ansible to ensure every server was compliant with the company's standards based on CIS standards. Red Hat Enterprise Linux has contributed significantly to business continuity and compliance efforts.

We haven't encountered any critical vulnerabilities that required Red Hat Insights to resolve. They all had low CVE scores, so they could be handled with regular patching. We haven't had to use emergency procedures yet. Red Hat Insights has dashboards you can use to see your performance, what systems are critical or require patches and all that stuff. 

Red Hat could add some AI features. There's a lot of talk about AI nowadays, but I don't think will be in Red Enterprise Linux itself. The cloud applications benefit from AI, but I don't think that will be integrated into the OS yet. 

I have been using Red Hat Enterprise Linux for about seven years now.

We've hardly had any downtime. It goes down occasionally, but the system performs well overall. There aren't many problems, and when we do experience issues, Red Hat support resolves them quickly.

Red Hat Enterprise Linux can scale to meet the organization's needs as they evolve.

Customer service is rated eight out of ten.  Red Hat support has been instrumental. As an industry standard, it provides quick solutions to any technical problems that arise.

It is generally easy to initiate a support case with Red Hat, and there are clear escalation paths if needed. The support team responds based on the contract level.

Positive

I used Sun Solaris previously. It was nearly perfect, but it had some areas for improvement, similar to Red Hat Enterprise Linux.

The benefits of investing in Red Hat Enterprise Linux include stability, continuity, and robust support.

Other Linux operating systems like Debian are community-driven but lack the large company support that Red Hat offers.

I rate Red Hat Enterprise Linux nine out of 10. Red Hat is a large organization with a solid community that can provide upstream and downstream support. I don't give it a 10 because operating systems always have room for improvement. It's almost there, but there are a few things that Red Hat could do better. 

Red Hat Enterprise Linux serves a variety of purposes in our organization. Initially, we used it for web hosting and web application support. We've since expanded its use to banking, where it serves as the foundation for our applications, and to containerization projects utilizing Podman.

Red Hat Enterprise Linux has brought uniformity and standardization to our workflows, providing excellent support enhanced by using Ansible. This has allowed us to centralize development and standardize all our systems.

Red Hat Enterprise Linux enabled us to centralize development by providing a standard system used across the board. This streamlines development by consolidating our efforts into one system with a single template for deployment and maintenance.

We are successfully using Red Hat Podman for containerization projects without any negative impact.

Red Hat Enterprise Linux's support and broad community assistance minimize the effort required to reduce risk, maintain business continuity, and ensure compliance.

Red Hat's container platform enhances organizational agility through the portability of applications and containers. Its centralized approach, which consolidates all resources in a single repository, streamlines operations and reduces management overhead. This robust system simplifies maintenance and ensures consistency across the platform.

My favorite feature is Ansible.

Red Hat Enterprise Linux could improve its communication slightly, but even that is already quite good. They could become the most efficient solution by focusing on improving areas where there is always room for enhancement.

I have been using Red Hat Enterprise Linux for six years.

Red Hat Enterprise Linux is stable.

Regarding scalability, it's enterprise software, so we can make it as big as we want.

Red Hat's customer service and support are excellent. For example, when we experienced instability with IBM DB2, their support team helped us optimize the system for our specific use case and implementation.

Positive

Before I started with our company, they used CentOS. Later, they transitioned to Red Hat Enterprise Linux.

The greatest return on investment from Red Hat Enterprise Linux is the support received.

Companies considering open-source systems are often startups or those seeking platform flexibility. Switching to Red Hat Enterprise Linux due to subscription costs can be a significant financial step.

I would rate Red Hat Enterprise Linux nine out of ten.

While Rocky Linux is a viable open-source alternative to Red Hat Enterprise Linux for those seeking a cloud-based operating system, a Red Hat Enterprise Linux subscription offers numerous advantages beyond the operating system itself and may be a worthwhile investment, depending on budget.

We use Red Hat Enterprise Linux in the enterprise for production environments. We mostly use it on bare metal servers, which are dedicated. In terms of deployment, we use the on-premises version of Red Hat Enterprise Linux.

Red Hat Enterprise Linux has given us better insights and allowed us to manage the environment more effectively. In terms of overall performance improvements, it has provided us with increased visibility into security, which has been helpful for our cybersecurity team.

Its built-in security features seem pretty sufficient for our purposes, but we have other teams that manage the security and build aspects. I am more involved in the maintenance of it, but in terms of the built-in security features, I find it sufficient. The security team also takes care of the compliance aspect.

I mainly use the Red Hat database for vulnerabilities. It is pretty good for determining whether or not a vulnerability has been resolved. 

We use Red Hat Satellite for patching. I like Red Hat Satellite for patching and keeping us secure.

We have used Red Hat Enterprise Linux in hybrid environments. It seems to work fairly well. For hybrid environments, it is probably one of the easier ones to deploy because it allows us to scale.

We were able to realize the benefits of Red Hat Enterprise Linux immediately after the deployment.

In terms of the organization and structure, the support is on point. The reporting and other things are very standardized. It does not leave much room for error when working in production environments.

When we first deploy Red Hat Enterprise Linux, it is very challenging to determine which security features have been deployed. It would be beneficial to have more insight into this. Additionally, once it is built, there does not seem to be an option to retroactively change security features, which can make it difficult to ascertain which ones have been deployed.

Their knowledge base is very verbose. There is too much information. It can complicate things a little bit. It is very detailed. If they can shorten it, that might be helpful.

We have been using Red Hat Enterprise Linux for a few years now, approximately seven to eight years.

I would rate the stability of Red Hat Enterprise Linux as seven out of ten. We do encounter problems, most of which can be resolved. Occasionally, we face issues that cannot be resolved until the kernel developers address them. These are typically dealt with through quarterly releases or major upgrades.

In terms of scalability, I would rate Red Hat Enterprise Linux about a nine out of ten. It is easy for us to make snapshots when we are patching. If we need to clone, we can do so, although they might not be full backups necessarily.

We use their portal for contacting support. The support from Red Hat is quite quick because it operates on a service-level agreement (SLA). For the paid support features, they are very responsive.

Positive

I am familiar with CentOS, and I have used OpenSUSE and SUSE Enterprise for testing and comparison purposes.

CentOS did not have as many security features. Of course, CentOS had the community support. CentOS was bought by Red Hat, and then the support started lacking. It was then discontinued to promote Red Hat Enterprise Linux.

We have done some physical to virtual migrations using VMware. We have been mostly involved in that. We have done a little bit of virtual-to-cloud migration but not as much as physical-to-virtual.

The migration is more on the complex side. There are quite a few players involved. We need to collaborate with different teams. We need to make sure that the database is there, and that the database team is always involved. It is not terribly simple. It requires quite a bit of project planning and coordination. We usually have a six-month project so that it can be planned and tested.

It does require maintenance on our end but not very frequently.

Red Hat Enterprise Linux licensing is quite costly, but I personally do not deal with pricing.

My advice to new users would be to focus more on the build aspect because it can be overlooked by many new users.

The Leapp utility works well when you do not have a much-customized environment. The more customized your environment is, the more complicated it gets to get Leapp to work to switch over to Red Hat Enterprise Linux. It is possible, but the more customized your environment is, the harder it is because it will require the kernel module. Convert2RHEL is pretty much the same as Leapp. The more customized the environment, the harder it is. It is feasible. It is just a matter of how much time you are willing to spend on it.

I would rate Red Hat Enterprise Linux a seven out of ten.

I use Red Hat Enterprise Linux to control my Docker systems and build and run containers on them. I also use it for a tokenization project I'm working on.

Red Hat Enterprise Linux (RHEL) has improved the availability and security of our systems. The knowledge base, Wiki forums, and other resources are very helpful in simplifying my daily operations. We realized the benefits immediately after deployment. 

The most valuable features of Red Hat Enterprise Linux are the availability, file system performance, and overall system availability. The kernel is more secure than my previous operating systems, such as Windows.  Red Hat's knowledge base is helpful. I consult it several times in my daily work. I can ask questions on the forums and get help in my daily operations.

Using Red Hat Enterprise Linux's image builder is easy. I can use GitAI to pull any image I want to build on my system and reach into it using Red Hat. I use Convert2RHEL to publish my work on tokenization. I'm publishing more than 70 prints on my system daily, and saving this file. It's easy to use.

There are performance issues with the response time when accessing the console, but I'm unsure if that's Red Hat Enterprise Linux's fault or if it's due to the lack of CPU or memory on our machines. The enterprise interface could be improved. I can only use the keyboard to transfer files from one system to another. I want to use my mouse on the interface, not just scroll up and down. I would also like my logs archived as an RAR and sent to me. 

I have been using Red Hat Enterprise Linux for more than five years.

Stability is critical to us. Red Hat Enterprise Linux ensures our machine's availability and reduces the need for frequent restarts.

I have not contacted customer or technical support myself. Our infrastructure team handles any contacts with Red Hat support.

Positive

I have used Ubuntu before. Red Hat has a more robust knowledge base, and finding solutions to any problem is easier.

The infrastructure team handled the initial setup. I'm a software engineer working on my applications. The infrastructure team builds the machine, and I only use it. It was relatively easy, depending on the complexity of the deployment configuration. After deployment, we have maintenance on our machine if there are new patches to deploy. I have three machines, and each one is identical, with the same containers, so I don't need to do maintenance on our machines more than once monthly. 

It is important to use the knowledge base and familiarize oneself with key commands to gain more about Linux and ease its usage.

I'm using the Red Hat Platform with Open Stack and an RHEL product for storage. The use case is performance IOPS for Ceph Storage, which depends on a bare-metal RHEL server. 

For my security customer, we get greater than 90 percent uptime. RHEL helped us achieve security certification. It helped my end-user pass their security assessment. RHEL's built-in security features scan the third-party layer in the OpenStack and RHEL platform to assess the SSH and firewall security or patch updates from the RHEL platform and reset OpenStack. Security is the number one priority for my end user. They want to prevent hacker access from the outside. 

RHEL supports the hybrid cloud strategy. The goal of using a bare metal server has been to improve availability and database performance. The OpenStack platform uses network capability to improve database performance.

RHEL improves database and application performance for my end users. The application can collect regional and national data for my end user, a strategic customer in Indonesia.

I am confident in the managed services RHEL provides in terms of the OpenStack, Ceph Storage, and OpenShift container-based products. If there are any problems with the RHEL platform, Open Stack, Ceph Storage, etc., I can raise the issue to RHEL global support. 

For the past twenty or thirty years, Red Hat has reengineered its product from bare-metal on-prem to the cloud environment. Migrating an RHEL system from bare metal to cloud is somewhat difficult. They could add a fast boot. 

We deployed one side of RHEL in 2023, and we'll deploy the other side in 2025.

When I deploy RHEL for the first time, I try to learn about the performance and tune the performance. 

Scalability isn't an issue. Our customers haven't reported any performance problems from scaling up.

I rate Red Hat support eight out of 10. I have used Red Hat support since 2023. They escalate the ticket based on severity, and if they can't resolve the issue within the maintenance window, they will pass me to another engineer. 

Positive

We previously worked with Oracle Linux. My customer has two divisions. The network decision is focused on accounting database performance, while the IT division uses Oracle Linux. On the network side, the customer uses RHEL products like OpenStack, Ceph Storage, and OpenShift. 

My end user wanted to upgrade from RHEL OpenStack 16.1 to the latest 17.1.3 in April 2024. We also upgraded Ceph Storage and OpenShift. Now, my customer wants a testbed before upgrading to the RHEL version in live production. If there are problems, we open a ticket with global support and or two people will join our remote call. We have it deployed in Jakarta and plan to deploy it to Bandung.

I rate Red Hat Enterprise Linux eight out of 10. I recommend all the Red Hat products, including OpenShift and Ceph Storage. OpenShift Container is a mature product for RHEL portal customers.

The main use case is generating golden images. All the deployments of operating systems and virtual machines on the servers are based on the golden image. The developers and providers can run all the applications on top of those.

Whenever we need to remediate any vulnerabilities, patches are available. These patches are not only for current exploits but also for back-porting for bug fixes and security fixes. These patches are available from the most recent versions to the specific version that we are using.

Red Hat Enterprise Linux has enabled us to centralize development. We have a golden image of the operating system. That golden image sets the standard for all the security policies that we are applying to it. For example, the partition scheme and the best practices that we apply to the golden image are the starting point for all the developers to start working with all the applications and also executing appliances or applications from providers.

We are using Red Hat Enterprise Linux with Podman for containerization projects. Red Hat offers what is called UBI or Universal Base Image. That image is already configured to be secure and have good performance. To start working with containers, we just have to pull UBI as a base for our images and start working on those. It has impacted our containerization project because instead of using Docker, we can use Podman. There is a common container image that is used by the majority of the customers, but I forgot the name of that one. Instead of using that, which is like a very minimal image, we are using UBI because it is already secure. It has the majority of the benefits of our Red Hat Enterprise Linux image but in a container image.

There is portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. That is a very good option to have because you do not have to worry about the underlying system. You just have to worry about your application and have the application running on top of your image based on UBI. It is going to be so easy to have the application running either on a machine with Podman or have the same application running just on top of OpenShift. It is so easy to move a container-based application that can be executed on top of Red Hat Enterprise Linux with Podman or on top of OpenShift. 

Security, packages, and updates are valuable. There is also the possibility to do unattended installations. This way you can define how you want the installation to behave and be configured whenever you do the deployment.

One of the best features is having a tool called OSCAP, which is a tool that is going to allow us to apply security profiles to the golden image. This way, all the security features or policies can be applied in real time. This way, we can follow all the policies that are defined by our security teams.

There are not a lot of areas to improve because the majority of the time, Red Hat is constantly improving it. The only area would be in regards to being capable of running on other architectures like ARM. They are about to release a new version that is available to be executed on ARM architecture.

We have been using Red Hat Enterprise Linux for about a year.

It is very stable.

It is scalable. We have plans to increase its usage.

It used to be better. It is still good as long as you can get in touch with a level 3 support engineer. If you have a trained engineer who helps you with what you need and who understands how to ask for specific details of what you need, you should be good. But, unfortunately, if you start with a simple detail of what you are experiencing and what kind of help you need, you will receive the same response. For example, you are pointed to a knowledge base article, and that is it. The support engineer is supposed to help you with your issue or request, but unfortunately, that is not happening anymore. It used to, but I understand.

We are looking for a support engineer to go all the way. The only way for you to contact support is via the support case system or page. After that, you interact through the ticket or email. You do not have a chance to have a call. If we have escalated a case, it is usually better if you have a person for a proper understanding and proper advice on what you have to do and how to resolve the issue. It could be that you need a new product, subscription, or service, but you do not know that.

Neutral

When I got into the company, they were already using Red Hat Enterprise Linux, but back in the day, I used to have HP-UX. That was a very ancient system. It was Unix-based. It was a proprietary solution. HP-UX was a platform licensed based on the old Unix code that was tightly integrated into hardware built only by Hewlett-Packard. You could not run HP-UX in any other place. You could only run it on hardware created by Hewlett-Packard. The intention with that was to run only on the Itanium architecture, whereas Red Hat Enterprise Linux can run on x86 architecture. It is also open-source.

We have it on-premises. It is in different locations. We are following a strategy to publish the images of the operating system. This way, multiple teams can grab the images and have their own procedures to deploy within each separate environment. We have multiple teams working on developments and they need a base image to start working on all the development stuff. Because they are all independent teams, they have access to a single source of image. This way, they can start working on further customizations and whatever they need.

We implement it in-house.

The ROI is in terms of the time that I have to invest in doing customizations, applying security policies, and fixing the supply to the system, wherever I need those.

The reason for going for Red Hat Enterprise Linux is to improve the time to market. It is so easy to just generate a new image. We can configure it with all the security features and all the libraries and packages we need. We can also configure it with the ones requested by developers. We can do all of that. It is so much easier than what we can do with Windows, for example.

It is very straightforward. We do not have to think much about having to get all the subscriptions related to the Red Hat Enterprise Linux fleet that we have because all the subscriptions came in pairs of CPUs or even for an entire bare-metal server. That way you can partition your bare-metal server into multiple virtual machines, and then you are covered. As long as your bare-metal server is covered, you can roll out any number of virtual machines on top of it. It is very easy to get subscriptions for your bare-metal server, and you can utilize whatever you want.

We evaluated operating systems or Linux distributions created by the community or run by the community only. We evaluated them mainly because of costs.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that they would not have the same team supporting all the operations and all the critical features and patches that they receive with Red Hat Enterprise Linux. They can go with one of the clones, but unfortunately, at the end of the day, the clones are going to deviate from Red Hat Enterprise Linux. With Red Hat Enterprise Linux, you can also create support cases to receive back-ported bug fixes and security fixes, and you get very cool features such as Insights, Satellite, or system roles provided along with Ansible. 

We are currently not using Red Hat Insights but that is an awesome tool.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten. It is an enterprise Linux distribution. It was one of the first distributions to focus on the enterprise. There are others, but Red Hat is the main contributor to the Linux ecosystem. Because of that, it is so stable. It has proper support. It also provides the Linux ecosystem with new features and enhancements.