Red Hat Enterprise Linux (RHEL) Reviews

My main use case for Red Hat Enterprise Linux (RHEL) is using it as an operating system for all of our Linux VMs, converting all of them from 42 different operating systems and versions over to Red Hat.

One pain point that Red Hat Enterprise Linux (RHEL) helps me solve is patch management, as we previously used a giant Ansible playbook that would run updates across our infrastructure with so many conditionals in it, but now we can simplify it down to essentially just one. It was previously one playbook, but it simplifies the workload to approximately half of what it was.

The features of Red Hat Enterprise Linux (RHEL) that I like the most include the cohesion among all of our VMs, so I do not have to remember that if I am SSHing into this server, it is apt update, and this one it is DNF update, and that one it is yum update; it is all going to be the same, DNF or yum update for all of them.

For navigating security risks in Red Hat Enterprise Linux (RHEL), Satellite is a big feature for us, as in the last couple of weeks, we just had two critical security vulnerabilities come out for Linux, and we use Satellite to find all of the vulnerable servers and then Ansible to patch them as soon as Red Hat releases a kernel update.

I have used System Roles quite heavily, so I want to use Image Builder, but I have not used it yet. All of our Ansible playbooks and roles focus on using System Roles first so that future iterations and updates to Red Hat Enterprise Linux (RHEL) 10 or Red Hat Enterprise Linux (RHEL) 11 will work going forward.

I have been using Red Hat Enterprise Linux (RHEL) for three years.

Regarding the stability and reliability of Red Hat Enterprise Linux (RHEL), I have experienced no downtime, crashes, or performance issues; it has been flawless. We have had no issues with it, and the only waiting period we experienced was for the two recent security issues because someone jumped the gun and published the exploits too early, but that is nothing Red Hat Enterprise Linux (RHEL) can control.

In terms of scalability, Red Hat Enterprise Linux (RHEL) scales wonderfully; we have about 400 VMs, and as I mentioned, we are converting all of our existing VMs over, whether that is a straight conversion using convert to Red Hat Enterprise Linux (RHEL) scripts or a rebuild. I have had both five Red Hat Enterprise Linux (RHEL) VMs and also had 200 Red Hat Enterprise Linux (RHEL) VMs, and honestly, it has been no different; when running reports, it just takes maybe a minute longer to grab everything.

My experience with customer service and technical support has been phenomenal; I have submitted multiple cases for various issues, and technical support has also been fantastic to work with. The longest I had to wait for a solution was about two days, and what they suggested fixed the issue for us long-term.

The factors that led me to consider a change to Red Hat Enterprise Linux (RHEL) included running an audit across all of our Linux servers and discovering that there were 42 different versions of operating system or operating system versions; we could maintain that with a bunch of Ansible playbooks, but we did not want to. Another product released by SUSE is similar to Satellite in that it provides an upstream RPM provider, but it did not work very well; it was adequate, but Satellite is by far the best. Standardizing everything has been a huge advantage for us.

I would describe the deployment process of Red Hat Enterprise Linux (RHEL) as straightforward, as I can go into Satellite and spin up a new VM; I have a fully functional VM within 10 to 15 minutes. This is provisioning VMs from nothing essentially, as we are not cloning a template. We initially tried cloning templates, and it only took minutes to have a new VM up and running.

We have not considered any other solutions in the time that we have been using Red Hat Enterprise Linux (RHEL), as we just purchased Red Hat Enterprise Linux (RHEL) three years ago. However, around that time, we contemplated Ubuntu's enterprise-level agreement, which includes support and extended release for updates; these were the two contenders we really compared, and Red Hat Enterprise Linux (RHEL) beat them by a significant margin.

While I have not used Red Hat Enterprise Linux (RHEL) in a traditional sense with AI workloads, we have a Red Hat Enterprise Linux (RHEL) VM that one of our Ames Technology Hub members logs into and runs AI workloads, though I do not know what they are using, and I doubt they are using Red Hat Enterprise Linux (RHEL) AI.

In our company implementation of the zero-trust model, Red Hat Enterprise Linux (RHEL) plays a role by using SE Linux and firewall D to configure everything and set it all up, although we have a different tool for managing Windows and micro-segmentation, and we have not implemented that on Linux since Linux is such a small portion of our company's business.

I have not done a major version upgrade with Ansible Automation Platform because we do not have it yet, but I have done major version upgrades from seven to eight and eight to nine with Satellite using the Leapp package provider. I have not done any nine to 10 upgrades because no applications really support it.

The transition from previous versions to Red Hat Enterprise Linux (RHEL) was smooth; we tried converting all of our existing VMs over to Red Hat, and that was hit or miss on whether it would work. This is through no fault of Red Hat's, as Oracle Linux does not migrate over to Red Hat smoothly, but the major version upgrades have been flawless and have worked every single time.

Our company's process for managing regulatory compliance does not involve Red Hat Enterprise Linux (RHEL) playing a role, as we are not a publicly traded company, and we also do not house any PII or credit card information, so we are not under any regulatory compliance. However, our auditing team checks what users have root access to these servers or super user privileges, and at the moment, we just run an active directory audit since they are all joined to our active directory. In the future, I am hoping to set up Red Hat Identity Manager to manage SSH keys and user access into Linux servers.

Overall, I have loved the experience with Red Hat Enterprise Linux (RHEL), as I have used Ansible for six years of the seven years I have been doing this professionally. We just hired a new Linux admin, and one of the first questions I asked was about their experience with Ansible. They had worked with it, so I asked about their experience in writing playbooks or roles, and they have written them extensively. I would rate this product a 9.5 out of 10.

As the DevOps engineer, my main use case for Red Hat Enterprise Linux (RHEL) today is as our OS. All our runners run on that, as well as Red Hat Enterprise Linux (RHEL) UBI containers, which is what we deliver to our customers. Red Hat Enterprise Linux (RHEL) runs our infrastructure and is what we deliver to the customers as well.

We use Red Hat Enterprise Linux (RHEL) all on-premises on Dell servers.

I have not tried doing AI workloads with any Red Hat AI product specifically, but we are running our AI model server with VLLM on Red Hat systems. We are using it on Red Hat Enterprise Linux (RHEL), but not with any Red Hat AI.

Red Hat Enterprise Linux (RHEL) helps us solve pain points by giving us security and trust. When we tell our customers we are using Red Hat Enterprise Linux (RHEL) images, it helps them trust us that we are using the security and we have all these controls. Red Hat Enterprise Linux (RHEL) gives us trust and security.

I value the management features of Red Hat Enterprise Linux (RHEL) the most, such as Red Hat Satellite, which allows us to tell and monitor our whole fleet about the status of every system and keep it up to date. The management interfaces are really effective.

For navigating our security risks in Red Hat Enterprise Linux (RHEL), it would probably be mostly Satellite. With Satellite, you can determine which of your systems are out of date. Containers might also show outdated packages. Satellite helps you find systems that have not been updated or systems with old packages.

Red Hat Enterprise Linux (RHEL) helps mitigate downtime and lower risks. Since Red Hat Enterprise Linux (RHEL) has all these Ansible and Kickstart and Satellite features, we have a good process of redeploying systems. If something did go down or break, we have all the automation to be able to bring it back up, and we have all that as code. This has been helpful.

I am not certain how Red Hat Enterprise Linux (RHEL) can be improved. We are still on Red Hat 8 mostly, and so I am not really certain about what features have already been released.

From a Red Hat 8 perspective, I think perhaps better container support for running them as services would be beneficial. Maybe Kubernetes support, such as something built-in for if you just want to use the system for running containers and keep them online as services would be valuable.

I have been using Red Hat Enterprise Linux (RHEL) for the whole time, since 2021, which is approximately five years.

I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL). We have had servers that are very stable for many years.

Red Hat Enterprise Linux (RHEL) has definitely scaled with the growing needs of my company. As we have grown as a company, we have expanded how many servers we have. It has been pretty smooth with Satellite managing it all. You can keep track of everything, so it has been good.

I would rate customer service and technical support of Red Hat Enterprise Linux (RHEL) an eight. It is really helpful to be able to open up tickets and get a technical person that can walk you through getting the logs and getting the information. In an ideal ten out of ten, it would be instantaneous support or much faster response times, but we do have a good response time and good support.

I am not certain if my company was using another solution to address our needs prior to using Red Hat Enterprise Linux (RHEL). There may have been some CentOS or Ubuntu used way back, but I am not certain.

I think we have seen a return on investment with Red Hat Enterprise Linux (RHEL) from a technical point of view. The investment comes from when we can deliver our software to customers and they can start immediately using it versus if we are delivering a different OS that someone might not be certain is secure. They trust in Red Hat Enterprise Linux (RHEL) and that we are using that. This allows us to keep delivering at a good pace and getting the software into our customers' hands.

My experience with pricing, setup cost, and licensing has been really good. I am not at the level to buy it, but I think we have a company-wide Red Hat license. We can have as many Red Hat Enterprise Linux (RHEL) machines as we want, including all the packages and the containers. It has been positive and good.

We have also looked at Ubuntu while using Red Hat Enterprise Linux (RHEL). Their management platform is Landscape, and it just does not seem as reliable for us. We have had much more issues with Ubuntu from deploying it and hardening it. It does not really seem to work the same for us as Red Hat.

The business value of Red Hat Enterprise Linux (RHEL) compares favorably to the other Linux distributions we have evaluated, such as Ubuntu. Red Hat definitely has more value. We invest much more time in that because we have so many more Red Hat Enterprise Linux (RHEL) systems, and it has been a much smoother experience. If any project tries to come to us wanting Ubuntu, we try to steer them away and see if Red Hat will work first, because it seems to work better and is more comfortable.

I have tried Red Hat Enterprise Linux (RHEL) Image Builder, but only as testing. We are not using that in production, but I have used it and created a few images.

The testing with the Image Builder went really well. There were some limitations with what versions of Red Hat the Image Builder supported versus what we were currently using, so I could not really continue testing, but it worked for the walk-through I was following.

I do not know anything in particular in Red Hat Enterprise Linux (RHEL) that has helped me with my AI workloads overall yet. We are still just getting into the space, so I do not know if there is really anything about Red Hat specifically, because we are just running open source tools on Red Hat. However, it is still making us secure from a foundation with a secure OS.

We are not really doing a full zero-trust setup with Red Hat Enterprise Linux (RHEL), not yet. Having all our devices, such as all our Red Hat devices registered in Satellite, helps you keep tracking them. This is moving towards it, having a management system for everything, but nothing really other than that.

We have not done a major version upgrade with Red Hat Enterprise Linux (RHEL) and Ansible Automation Platform, such as moving from Red Hat 8 to Red Hat 9. Whenever we have done that, we just reloaded the system. We use Ansible Automation a lot, but never for a full upgrade.

My experience with the Ansible Automation Platform has been really good. We transitioned to it heavily. Before, we were just using each developer who were running the playbooks themselves. Now we can put them in the platform. The access is really good, so we can have students who can only run certain playbooks or not edit them, which is helpful. Full-timers can set up something that works and then the students can run it as they need. This has been really helpful for us for automating things.

From an OS level, when we are deploying Red Hat Enterprise Linux (RHEL), we can pick the DISA STIG profiles, and that gives us a good starting point for all our systems to be hardened a certain amount. Then we use the Ansible Automation Platform running Ansible playbooks that can finish the job and finish the rest of the STIG controls. This makes them compliant. We can also run Ansible playbooks that can verify all our systems are at that certain level. Red Hat Enterprise Linux (RHEL) does a major part, and we use Red Hat for pretty much everything for our compliance.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is really good. Many times I am searching for questions and it will pop up as one of the first few results showing how to solve it. A few weeks ago it helped me solve an issue for a customer. The knowledge base has been really helpful.

The deployment process with Red Hat Enterprise Linux (RHEL) has been pretty straightforward. We use the Kickstart process, and then Ansible to finish the deployment. My overall review rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.

Red Hat Enterprise Linux (RHEL) basically runs the bank's apps as my main use case.

I like the feature Satellite the most because it has services to manage my multiple Linux servers.

Satellite has no parallel in the Linux distro world, especially for an enterprise, enabling me to manage my servers, patch them, create content, get them binaries, updated security updates, and all that. It makes it easier for admins and reduces the need for a lot of manpower, especially with Ansible that enables me to do configuration management of 20,000 Linux servers.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk because the servers can run for more than 300 days of uptime. I do have to reboot them for patching, but otherwise, they are a very stable operating system that doesn't crash for no reason. If I experience kernel panics, it often involves EDRs or agents such as CrowdStrike, but otherwise, it's very stable with proactive features. We had issues with CrowdStrike; they identified the issue with their kernel drivers that used to crash my OS and provided a patch to address it, so they take care of us.

The implementation had challenges like whenever we bring out new products, there's always one issue: Red Hat Enterprise Linux (RHEL)'s documentation is not complete. I have to really have an enterprise account because I get access to their support, which sorts me out since every environment is unique. It's not a cookie cutter; I would deploy RHEL 8 in a way different compared to a retail store. So when it gets to those niche deployments, they don't have anything documented. I really have to get hold of the support, saying, "Hey, I'm trying to do this. It's not working," and then they will give me a solution, but I would expect that a document would have solved that issue without raising a ticket. That's my only complaint.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation. I don't have any other suggestions. I think it's just the documentation that needs improvement. Otherwise, technically, I don't have anything to suggest.

I have been using Red Hat Enterprise Linux (RHEL) for ten years.

I have experienced downtime or security incidents as a result of the solution when proper practices are not followed, especially if I am using any third-party security. You have to manage kernel options; otherwise, the base OS itself is very stable.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

I would evaluate customer service and technical support based on my experience. I felt naive about being a small enterprise versus a big enterprise, but the response time of tickets is consistent. I haven't seen a difference; I thought I would have a slower response being on a small account, but the speed of our calls is the same.

Positive

I considered other solutions before choosing Red Hat Enterprise Linux (RHEL), but it was a default choice for us. I see that they have expanded; earlier, it was just a bare-metal OS and not an ecosystem, but now they are in OpenShift, providing Kubernetes and everything.

I wasn't using another solution to address my needs prior to adopting it.

The upgrade or migration is straightforward if I have applications that depend less on what the OS is, but in our case, it was not that simple. We had a business requirement, so we had to shut down the older one, provision a new one, and move everything.

I have seen ROI from using Red Hat Enterprise Linux (RHEL) in terms of uptime itself.

My experience with pricing, setup, and cost of the solution is that it's a service based on how many cores, not sockets.

My deployment model for Red Hat Enterprise Linux (RHEL) is on-premises, but I am just starting off with cloud.

For security requirements in the cloud, I don't do SELinux; I just depend on my ACLs because my servers are not internet-facing. We trust Red Hat Enterprise Linux (RHEL) with the binaries, with nothing on the base OS such as firewalls or SELinux.

I use AWS and Azure as my cloud providers.

I manage my Red Hat Enterprise Linux (RHEL) systems for security, updates, and patches with Red Hat Satellite, which makes it very easy.

I have been involved in upgrades from RHEL 6 to 7 and from 7 to 8.

My assessment of Red Hat Enterprise Linux (RHEL)'s FIPS and security compliance features is that it's the best in the industry. They have FIPS, which I think is more for federal clients, and although I haven't used it, I know they offer it by default on their Linux.

My upgrade and migration plans are to always try to stay on the current version all the time, unless there's a legacy application. Any apps I manage are always on the latest Red Hat release, and we keep migrating them as Red Hat provides the first-ever release out, which is a requirement for our Satellite to support the latest version.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as paywalled, so if you don't pay for it, you wouldn't be able to access their system. The KB is pretty good, but you need to have a Red Hat account.

My advice to a company considering this solution is to go for it. It is supported by enterprise support from Red Hat, which I don't think any other enterprise can offer. While I know Canonical does it for Ubuntu, SUSE is another good option; however, the adoption is not there, and you don't have a lot of sysadmins. Red Hat Enterprise Linux (RHEL) is a bible due to the abundance of resources in the market. I would rate this solution a 10.

Red Hat Enterprise Linux (RHEL) serves as the operating system for our enterprise infrastructure. We use it to host applications, Kubernetes and OpenShift clusters, and other critical services that we perform day-to-day operations on.

One project I relied heavily on Red Hat Enterprise Linux (RHEL) was deploying a Red Hat OpenShift cluster. I used RHEL to prepare the bastion host, configure networking, DNS, HAProxy, storage, and install the required packages. After deployment, I also performed troubleshooting and day-to-day operations such as system updates, log analysis, and resolving service issues, as RHEL provided a stable and secure platform throughout the project.

We also use Red Hat Enterprise Linux (RHEL) as the standard operating system across our servers because of its reliability and enterprise support. It integrates well with tools such as OpenShift, Ansible, and VMware, making it easier to manage and maintain our infrastructure consistently.

The features that stand out the most in Red Hat Enterprise Linux (RHEL) are its stability, security, and long-term support. I also value SELinux for built-in security, DNF or Yum for package management, systemd for service management, and the performance and reliability it provides for enterprise workloads. Another strong point is the seamless integration with Red Hat tools such as OpenShift, Ansible, and Satellite, which makes infrastructure management much easier.

The feature I rely on the most in Red Hat Enterprise Linux (RHEL) is its stability. Since we manage production servers and OpenShift environments, having an operating system that runs reliably with minimal downtime is very important. It allows us to focus on deployments and troubleshooting without worrying about OS-level issues, making day-to-day administration much more efficient.

I would also mention the excellent documentation and large enterprise community around Red Hat Enterprise Linux (RHEL). It makes troubleshooting and learning much easier, and because it is widely used in enterprise environments, finding best practices and support resources is straightforward.

Red Hat Enterprise Linux (RHEL) has improved the stability and reliability of our infrastructure. Since adopting it as our standard operating system, we have experienced fewer system-related issues, better uptime, and a consistent environment for deploying applications and OpenShift clusters. It has also simplified server administration and troubleshooting, helping the team resolve issues more quickly and maintain a secure, stable platform.

We did not track formal KPIs, but we did notice practical improvements since adopting Red Hat Enterprise Linux (RHEL). For example, server provisioning that used to take a few hours became much faster because of standardized RHEL configurations and automation. Troubleshooting time also reduced since the environment was consistent across servers, and we have experienced very few OS-related outages. Overall, it has helped improve operational efficiency and system reliability.

Red Hat Enterprise Linux (RHEL) is a very mature platform, but I think it could improve in a few areas. The subscription and licensing model can be a bit complex for new users, and some enterprise features have a steep learning curve. Simplifying subscription management and providing more built-in automation and monitoring tools would make the overall experience even better.

While the documentation is very comprehensive, it can sometimes be overwhelming for beginners. More practical, real-world examples and troubleshooting guides would be helpful. Apart from that, Red Hat Enterprise Linux (RHEL) is a very reliable and well-supported enterprise operating system.

I have been working in this field for the last 1.8 years.

Red Hat Enterprise Linux (RHEL) has been very stable in my experience. We use it to run production servers and support OpenShift environments, and it has consistently provided reliable performance with minimal operating system issues. With regular updates and proper maintenance, we have experienced very few unexpected outages, making it a dependable platform for enterprise workflows.

Red Hat Enterprise Linux (RHEL) scales well for enterprise environments. In my experience, it has supported everything from individual servers to larger infrastructure running OpenShift clusters without any issues. It handles increasing workloads reliably, and its integration with enterprise management and automation tools makes it easier to manage systems as the environment grows.

Since I did not interact directly with Red Hat support very often because most issues were handled internally by our team, I can say that whenever we referred to Red Hat's knowledge base and official documentation, they were comprehensive and very helpful for troubleshooting.

Red Hat Enterprise Linux (RHEL) has been the standard operating system for our enterprise infrastructure since I joined my organization. I have not worked with a different enterprise Linux distribution in this environment, so there was not a migration or switch during my time there.

We manage our Red Hat Enterprise Linux (RHEL) systems using standard Red Hat tools such as DNF or Yum for package management and system updates, along with automation where needed. For provisioning, we follow standardized server configurations to ensure consistency across environments. Overall, I am very satisfied with the management experience because patching is straightforward, the tools are reliable, and maintaining multiple servers is efficient.

I have not used Red Hat Enterprise Linux (RHEL) Image Builder extensively in production. However, I have used Red Hat system roles along with Ansible to standardize servers, configurations, and automate common administration tasks. They were helpful in maintaining consistency across multiple RHEL servers, reducing manual configuration, and saving time during deployments.

We have seen a return on investment mainly through improved operational efficiency rather than reducing headcount. Red Hat Enterprise Linux (RHEL) stability and standardized management have reduced the time spent on troubleshooting and routine maintenance. For example, server provisioning and patching are more streamlined, and we have experienced fewer OS-related issues. Overall, it has helped save time, improve uptime, and allow the team to focus on higher-value tasks instead of resolving operating system issues.

From my perspective, the licensing of Red Hat Enterprise Linux (RHEL) is well-suited for enterprise environments because it includes access to updates, security patches, and Red Hat support. The initial subscription cost is higher than community Linux distributions, but the stability, long-term support, and enterprise features provide good value overall. I think the pricing is justified for organizations that require a reliable production-grade operating system.

I have used other enterprise Linux distributions extensively in a production environment, so I cannot make a direct comparison based on hands-on experience. However, from my experience with Red Hat Enterprise Linux (RHEL), its enterprise support, long-term stability, SELinux, and integration tools such as OpenShift and Red Hat Insights provide strong business value.

I rate Red Hat Enterprise Linux (RHEL) a nine out of ten. It is a highly stable, secure, and enterprise-grade operating system with excellent long-term support and seamless integration with tools such as OpenShift and Ansible.

The only reason I would not give Red Hat Enterprise Linux (RHEL) a ten is that the subscription model can be a bit complex, and the learning curve is steeper for beginners. Overall, it is one of the best enterprise Linux platforms.

From my experience, the AI capabilities around Red Hat Enterprise Linux (RHEL) are more focused on assisting system administration rather than replacing it. Features such as Red Hat Insights use predictive analytics to identify security risks, configuration issues, and potential vulnerabilities before they become a problem. This helps improve governance by keeping systems compliant and makes security management more proactive while still allowing administrators to review and control any recommended actions.

In my experience, the recommendations from Red Hat Insights are generally accurate and reliable. They help identify configuration issues, security vulnerabilities, and performance recommendations based on Red Hat's knowledge base. We still review the recommendations before applying them in production, but overall, they have been useful for proactive maintenance and reducing potential issues.

I would recommend Red Hat Enterprise Linux (RHEL) to organizations that need a secure, stable, and enterprise-grade operating system for production workloads. It is especially valuable if you are using technologies such as OpenShift, Ansible, or other Red Hat products because of the strong integration. My advice is to plan your subscription and licensing requirements in advance, follow Red Hat best practices, and make good use of the official documentation and knowledge base to get the most out of the platform. I rate this product nine out of ten overall.

Over the period of my career, I have been using Red Hat Enterprise Linux (RHEL) initially in my first job at a research center, where we used it as a base operating system. Different variants of Red Hat, including CERN certified Linux and Red Hat, were used extensively at that time as a base OS for our organization. We have used it for running various infrastructure services. In my current office, we are using it to run an OpenShift cluster, so the base operating system is Red Hat Enterprise Linux (RHEL).

We have performed a couple of migrations from cloud to on-prem with Red Hat Enterprise Linux (RHEL), and they were smooth. They did not cause us much trouble.

The security requirements when deploying Red Hat Enterprise Linux (RHEL) are essential, and you have to perform certain steps to harden the core OS, which we have been following over the years. We have developed a regime on how to secure the OS when putting it into production, and for any OS, whether it be Windows or Red Hat Enterprise Linux (RHEL) or any other variant of Linux, we have a process of hardening the OS, performing some basic security checks before putting it into production. That has been the key throughout my career. There are no particular security requirements for Red Hat Enterprise Linux (RHEL), but as a general rule, when you put an operating system into production, you perform a set of processes to harden the OS. Obviously, patching is one of them; you patch it up to the latest level to keep clear of known vulnerabilities. Then, you harden the OS in your own environment, ensuring certain services are up and running, avoiding any extra accounts on the machine, shutting down unnecessary services, and making kernel configurations for hardening. There is a long list that is common for any Linux operating system we use in our production environment, and we harden it before we put it into production.

The most reliable function I find in Red Hat Enterprise Linux (RHEL) is the stability of the platform. The stability of the operating system is crucial when you are running mission-critical services; you want to keep them running 24/7/365 with no downtime for the services. Unlike other operating systems, for example, with Windows, you have patches after which you need to reboot the OS. If you are not running your services in a cluster, you have to afford downtime for that service. What I really appreciate about Linux, particularly the latest versions and other variants like Oracle Enterprise Linux (OEL), is that they have developed mechanisms where you can patch even the kernel vulnerabilities without rebooting the OS. That is a key feature for me because we have been running some mission-critical services over the years, and I have kept my servers up and running for almost four years in a row with not a single second of downtime.

The main benefit that Red Hat Enterprise Linux (RHEL) provides for me is the stability of the environment in which I am running it. When running mission-critical services, I need a reliable operating system, and Red Hat Enterprise Linux (RHEL) provides the maximum stability of the infrastructure. It also offers scalability, which saves money when things are scalable, and there are no issues running the system without downtime, as that also costs money. Stability and scalability are key benefits.

Red Hat Enterprise Linux (RHEL) helps to mitigate downtime and lower risk because mostly, the infrastructure runs in the form of clusters. With OpenShift, I do not run a single node; we have underlying operating systems, and then we deploy clusters. When running clusters, there is very little chance of downtime. Whenever there is a problem in a node or a service, especially in today's microservices architecture, the nodes run on different hosts, and the application remains up and running in no time with no downtime for the service.

Red Hat Enterprise Linux (RHEL) can improve the pricing a little bit, but nothing else comes to mind.

I have been working with Red Hat Enterprise Linux (RHEL) for about twenty plus years, and my overall experience with Linux is extensive.

Red Hat Enterprise Linux (RHEL) helps to mitigate downtime and lower risk because mostly, the infrastructure runs in the form of clusters. With OpenShift, I do not run a single node; we have underlying operating systems, and then we deploy clusters. When running clusters, there is very little chance of downtime. Whenever there is a problem in a node or a service, especially in today's microservices architecture, the nodes run on different hosts, and the application remains up and running in no time with no downtime for the service.

The scalability process with Red Hat Enterprise Linux (RHEL) is pretty much scalable. The servers support a lot of resources, and as long as you have resources at the hardware level, the operating systems are scalable. There has never been any issue regarding scalability or supporting the resources which are required for applications to run smoothly. Red Hat Enterprise Linux (RHEL) has never been a bottleneck in that regard.

I would rate technical support from Red Hat Enterprise Linux (RHEL) somewhere between eight and nine because they have been very good in providing support. I never had any issue with the support; whenever we raised a ticket, we got a satisfactory answer and reply from the support, with a timely response. That is a key feature of Red Hat Enterprise Linux (RHEL), and it makes a significant difference compared to using a community edition of a Linux variant. Red Hat Enterprise Linux (RHEL) is a company that supports you, and they are there with the support and all the other services they provide.

When running a community edition, you have to put in an effort and rely on the community for any issues or help needed. When you buy Red Hat Enterprise Linux (RHEL), a company sits behind your operating system, providing support. The same goes for Oracle Enterprise Linux, which is binary compatible with Red Hat Enterprise Linux (RHEL); Oracle is there to support at the backend. With these kinds of operating systems, knowing that a full-fledged company is behind your operating system provides the required technical skill, manpower, and resources to support you in case you encounter any trouble.

Red Hat Enterprise Linux (RHEL) is simple to set up; the setup process is very straightforward and not complex at all.

I would rate the price for Red Hat Enterprise Linux (RHEL) quite high because in my part of the world, payments are made in dollars, and buying Red Hat Enterprise Linux (RHEL) comes at a significant cost. If 1 is high and 10 is low, I would rate the price somewhere around 2.

Red Hat Enterprise Linux (RHEL) can improve the pricing a little bit, but nothing else comes to mind.

In terms of technical aspects, I find Red Hat Enterprise Linux (RHEL) and Oracle Enterprise Linux (OEL) mostly the same as they are binary compatible. It does not matter to a service whether I am running it on Red Hat Enterprise Linux (RHEL) or Oracle Enterprise Linux. The final decision point for me comes down to pricing; Oracle sometimes offers very good discounts due to their various services such as databases and Oracle Cloud. Red Hat Enterprise Linux (RHEL) has similar pricing models, but cost can often be a concern for me because Red Hat Enterprise Linux (RHEL) tends to be a bit more expensive compared to Oracle Enterprise Linux, though technically they are quite similar with no issues.

I am pretty much satisfied with managing my Red Hat Enterprise Linux (RHEL) system. There has never been an issue when it comes to provisioning or patching. When you are running an environment with a lot of servers, you can now use configuration manager tools to keep your cluster up and running in no time. You can manage your configurations across the clusters to be similar, down to a dot in the config file, and that is not a problem. Red Hat Enterprise Linux (RHEL) supports these tools, and provisioning has always been a pleasant experience without any issues causing us much trouble.

I have experience with the knowledge base and it has always been very helpful. We have utilized the documentation extensively because when deploying new services, they have comprehensive and detailed documentation which is very helpful.

I can recommend Red Hat Enterprise Linux (RHEL) to other users without hesitation. My overall rating for this product is 9.5.

My main use case for Red Hat Enterprise Linux (RHEL) is virtual machines for web server hosting, and mostly web hosting and application hosting.

The feature of Red Hat Enterprise Linux (RHEL) that I like the most is the integration with the cloud, the cloud.redhat.com integrations, and the Insights portal.

Red Hat Enterprise Linux (RHEL) helps us solve the need for a supported Linux platform that we can dependably deploy all of our applications on, with an easy to patch process, very interconnected with Ansible, and very interconnected with Red Hat Satellite. It provides easy deployment and automation capabilities that are where it performs best.

Red Hat Satellite helps us manage and maintain our hybrid cloud environment by being the backbone of our automation. Without Satellite, we would not be able to do version matching, and we would not be able to ensure all the packages are the same between our on-premises and Azure environment. When we do new deployments, we are able to make sure our new deployments match what we have existing, whether it is on-premises or more nodes in the cloud or more nodes on-premises. That is where we use the versioning.

I do not have much experience with the pricing, the setup cost, and the licensing of Red Hat Enterprise Linux (RHEL). I know we have it; somebody pays for it, but we have enough licenses and they make sure of it.

One of the biggest improvements I see for Red Hat Enterprise Linux (RHEL) is Red Hat Enterprise Linux (RHEL) AI that is on Red Hat Enterprise Linux (RHEL) 10 now. We have not had the chance to try that one yet, but I have seen demos of it, and it appears to be a very good tool that might be very useful in the future.

I have been in my area of expertise for thirteen years.

I have not experienced any downtime, crashing, or performance issues with Red Hat Enterprise Linux (RHEL). It has been solid, particularly Red Hat Enterprise Linux (RHEL) 8.

We find Red Hat Enterprise Linux (RHEL) scalability good; we have clustered databases that we use Red Hat Enterprise Linux (RHEL) for, and it has been solid. When you give it network access to the other nodes, it will perform its function.

My experience with the customer service and technical support of Red Hat Enterprise Linux (RHEL) has been very good. When you open a case, you get somebody pretty quickly, and they are very knowledgeable, so I am very happy with the support.

I would rate the customer service and technical support a nine, because nobody gets a ten.

Prior to adopting Red Hat Enterprise Linux (RHEL), we were using CentOS 7.

We decided to switch because we wanted support. We were always looking at containers and thought Red Hat offered the best solution to containerization, so it was a natural progression to get Red Hat Enterprise Linux (RHEL) as well. We used to run the open-source version of Satellite, AWX, but it was falling apart and hard to maintain due to issues and a lack of solutions in the open-source forums. It made sense to switch to Satellite and get Red Hat Enterprise Linux (RHEL) since we were adopting all the other Red Hat ecosystem platform offerings.

I would describe my experience with the deployment process of Red Hat Enterprise Linux (RHEL) as initially complicated due to the licensing model of Azure, which was a little confusing. However, afterwards, we created some Terraform configurations to deploy Red Hat Enterprise Linux (RHEL) in Azure, and since then, it has been one enter button.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL), from my point of view, is the support and the integration with Red Hat's cloud features. The documentation is really good, and before, when I searched for something about a fix, Red Hat documentation would often come up, and I would not have access to it. Now that I have access to it, the solutions given are usually straight to the point, such as "Run this command and we fix the problem." That has definitely been a lifesaver.

I have not considered other solutions while using Red Hat Enterprise Linux (RHEL).

We have been using Red Hat Enterprise Linux (RHEL) for four years now.

We use Red Hat Enterprise Linux (RHEL) both on-premises and in the cloud, specifically on Microsoft Azure cloud and on-premises.

Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy by enabling us to host our applications in a hybrid deployment, half on-premises and half in the cloud, while using load balancers in the front. With Red Hat Enterprise Linux (RHEL), we are able to deploy the applications that we need to support our strategy on both sides, including the databases and the caching system with synchronization between on-premises and the cloud. It allows us to install anything we need, and with the automation tools around it, it lets us quickly deploy and automate everything and have it running.

Red Hat Enterprise Linux (RHEL) plays a role in our company's implementation of a zero-trust model mostly with workloads, as it works with workloads and the integrated firewall. With Red Hat Enterprise Linux (RHEL), we are able to secure access to the various ports that are running in our application, regardless of whether we decide to use a Unix socket or something VIP-based, to host them.

We use the Ansible Automation Platform.

Our experience with the Ansible Automation Platform has been great; it is one of our favorite tools. It started small and then it became one of the most important tools within our organization. Everybody uses it, and everybody has been creating Ansible playbooks for it. We are now pushing to have all of our applications deployed using Ansible Automation Platform, so it has become a major tool that has been integral to the success of our team.

I cannot say I have used a lot of the available knowledge base from Red Hat Enterprise Linux (RHEL) directly, but it is very good. Red Hat documentation is very good in general.

I would rate this review a nine overall.

My main use cases for Red Hat Enterprise Linux (RHEL) include day-to-day operations and a lot of production systems. That is mainly what we do.

When it comes to pain points, Red Hat Enterprise Linux (RHEL) helps us solve various issues. A lot of our systems are proprietary, so we develop on the Red Hat Enterprise Linux (RHEL) system, making it hard to answer what Red Hat Enterprise Linux (RHEL) does that we couldn't do without it, because we build on top of it, and if we can't find a solution, we reach out to support for help.

I do appreciate the OpenShift product in Red Hat Enterprise Linux (RHEL), and I am interested in the new feature, the MCP, which I found fascinating after seeing it yesterday.

We definitely use the Identity Management features in Red Hat Enterprise Linux (RHEL) a lot, especially the rollback features and primarily the RBAC features, which are the brains of the system right now, even though the projects I work on are locked down significantly, so we cannot use all the tools in the toolbox.

In my company's implementation of the zero-trust model, Red Hat Enterprise Linux (RHEL) plays a role mainly in the identification process, along with other tools we embed with it, focusing on identification and scaling, including a lot of tokens.

I love the knowledge base offered by Red Hat Enterprise Linux (RHEL), which I use all the time because there is always something in there that can serve as a reference, guiding me or providing solutions to solve my problems. I often encounter the same solutions for issues I have seen before.

I have not tried either Red Hat Enterprise Linux (RHEL) Image Builder or System Roles, but I plan on working with Image Builder as I think I signed up for it, though I am not certain if that is today or tomorrow.

I have not tried to work with AI workloads using Red Hat Enterprise Linux (RHEL), but I recently attended a talk about that with the Agent AI, which was new to me, and I took snapshots and pictures, planning to introduce it to the team sometime this week.

Mitigating downtime with Red Hat Enterprise Linux (RHEL) is tough to assess because of patching, which is inconsistent sometimes. Other systems installed on top can sometimes break systems, but we resolve those issues as they arise.

I do not know how Red Hat Enterprise Linux (RHEL) can be improved because I have not played with Red Hat Enterprise Linux (RHEL) 10 yet. I am still learning as I go, having downloaded it and staged it, but I have not really tinkered with it yet.

I do not want any improvements in my workflow because new features are always coming out, which I appreciate. Each new release brings along something new that we work on implementing into our current pipeline.

I have been using Red Hat Enterprise Linux (RHEL) for at least 15 years.

I have not experienced downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL). If there were any, they would likely be due to some type of tool installed on top that was not compatible with updated patches, but overall, out of the box, there are no problems.

Red Hat Enterprise Linux (RHEL) scales well with the growing needs of my company. We have upgraded from version 7 to 9 without problems, and the migration has been straightforward, although I think version 10 might have some features that are not compatible, but I am not completely certain.

My experience with Red Hat Enterprise Linux (RHEL)'s customer service and technical support has been excellent. I love them and have no complaints.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the support. I love the support because when I put in a ticket or reach out, it is always excellent, and they never leave me waiting for days, providing feedback promptly.

Before choosing Red Hat Enterprise Linux (RHEL), I think my company was using another solution, possibly something like AIX or another Unix flavor, but I am not entirely certain what it was.

I do not know why they migrated to Red Hat Enterprise Linux (RHEL), as that was before I started. I just know there are still some legacy systems out there.

The deployment experience with Red Hat Enterprise Linux (RHEL) depends on your knowledge or experience. We do a lot of kickstarts, making deployment easy, but if something needs to be done manually, it might take a while. However, so far, it has been pretty much streamlined, so we are happy.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the support. I love the support because when I put in a ticket or reach out, it is always excellent, and they never leave me waiting for days, providing feedback promptly.

We have considered other solutions like Ubuntu, but right now, we are still using Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) wins because currently, everybody is familiar with it and they are happy with it. We prefer not to fix what is not broken, so we are content and happy with what we have.

I have not done a major version upgrade with Red Hat Enterprise Linux (RHEL) and Ansible Automation Platform, but that is in the pipeline, likely next quarter.

My experience using Ansible overall is good so far. I am used to doing it the old way, but now that we finally have an Ansible platform, it is better than when I was running playbooks manually from my workstation.

I have been using Red Hat Enterprise Linux (RHEL) since version 4, having used it for a long time with my current baseline systems ranging from version 7 to 9, as we try to migrate over to version 10.

I have used Ansible as well.

I know OpenShift is expensive and while I just put in requests, if they fill their budget, I am happy because that is above me.

My overall review rating for Red Hat Enterprise Linux (RHEL) is 9 out of 10.

Red Hat Enterprise Linux (RHEL) is used primarily from a server perspective, running numerous applications on top of the Enterprise Linux server. This includes in-house applications, client-based applications, and integrations with Active Directory, LDAP, and databases that sit outside but are integrated with the Enterprise Linux servers. Over 8000 Linux machines are running across VMware, physical servers, and AWS instances.

Red Hat Enterprise Linux (RHEL) operates in a complete hybrid environment with machines running on physical servers, VMware, and Azure instances. Red Hat OpenShift serves as the private cloud product and runs on production and QA environments with a 32-node cluster and a 16-node cluster containing 16 worker nodes running Red Hat CoreOS, which is a customized operating system provided by Red Hat.

My experience is primarily on the Red Hat side, though I also work with multiple integrations including Active Directory, LDAP, Grafana, Dynatrace, and Prometheus. I use DataDog and Dynatrace for log monitoring. I currently work with several cloud platforms including GCP, AWS, Azure, and IBM, running Enterprise Linux and OpenShift on IBM cloud, Azure, and AWS where they offer managed services such as Red Hat OpenShift on AWS (ROSA) and Azure Red Hat OpenShift (ARO).

Compared to other technologies and products, I have not identified any cons for Red Hat Enterprise Linux (RHEL), but I see many advantages. By using Red Hat OpenShift, resource consumption has been reduced significantly compared to what was consumed on Red Hat Enterprise Linux servers. Previously, a few applications ran on one RHEL server, but after moving to OpenShift, those applications were containerized and now run as containers on the OpenShift environment, reducing resource consumption by more than 80%.

Regarding time-saving aspects, using the Ansible configuration management automation tool saves considerable time. It allows me to automate multiple repetitive tasks instead of deploying everything manually, which can be quite repetitive.

To mitigate downtime and lower risks, changes are made during off-business hours to minimize business impact, often working during weekends or outside business hours. New upgrades are tested first in development and QA environments before being applied to production after receiving feedback.

Over more than a decade, I have found many improvements in Red Hat Enterprise Linux (RHEL), especially in the last 10 years. Red Hat enterprise services continually introduce new features such as Broadcom host cover for VMware. Red Hat recently introduced OpenShift migration, allowing existing servers to be migrated from VMware or elsewhere directly to the Red Hat platform or OpenShift through virtualization, which is a unique technology that Red Hat has provided to the industry.

From a security standpoint, the most important security features in Red Hat Enterprise Linux (RHEL) are the built-in security features already in place. Red Hat has recently introduced the Lightweight feature, which is in high demand in the market because it allows for customizable security options.

I have tried both Leapp and Red Hat Insights depending on client demand. Sometimes I prefer one, but if the client is not ready for that option, I must proceed with what they prefer.

Red Hat Enterprise Linux (RHEL) Image Builder is my primary tool for this work. Most clients want to customize their images rather than use standard ones provided with the ISO. When clients prefer certain elements to remain while requesting the removal of others, the Image Builder is used to meet their specifications.

One improvement I would like to see in technical support and customer service is that sometimes the technical team asks random questions. When a priority ticket has been raised and immediate responses are needed, they keep asking for repeated information, which feels like a strategy to buy time and can be quite frustrating.

Aside from support improvements, I currently do not have anything else in mind that I would like to see enhanced in Red Hat. One crucial missing feature regarding security is something I would like to see enhanced. Red Hat has great potential in this area, and they recently presented the Lightwell tool, which I am currently exploring and look forward to sharing my experience with.

I have been working with Red Hat Enterprise Linux for 18 years.

In terms of stability and reliability, Red Hat Enterprise Linux (RHEL) is stable.

Red Hat Enterprise Linux (RHEL) is scalable. Specifically, in the OpenShift area where I have worked for the last ten years, the environment can be scaled up and down at any time.

I would rate the knowledge base offered by Red Hat at 9 out of 10. The Red Hat knowledge base contains all the information needed for newcomers looking to explore their career in Red Hat. All documentation is available, and if you are good at reading or connecting the dots, you can utilize it without help from third parties.

My use of Red Hat in a hybrid environment is supported by the premium model, which provides all kinds of support. Most of my clients run Enterprise Linux servers in production environments, so the premium support option is typically used.

Red Hat helps solve many specific pain points, especially when stuck on a production issue and unable to find the root cause. In those moments, reaching out to Red Hat with a priority one support case results in immediate response and assistance.

I would rate the technical support team a 7 out of 10.

The initial setup process with Red Hat is not overly complex unless customized applications are involved, which Red Hat does not support directly. This is the only challenge encountered, as their support is limited to their own products rather than customized ones.

In terms of cost-effectiveness, this completely depends on what is being used and what the business needs are. Red Hat Enterprise Linux (RHEL) does bring a return on investment, but it varies based on those factors.

It depends on the client and the relationship they have with Red Hat. Sometimes, Red Hat offers significant discounts to clients running extensive environments with hundreds of Enterprise Linux servers and services such as Ansible and OpenShift.

Most of the time, Red Hat Enterprise Linux (RHEL) is procured directly from Red Hat rather than from other marketplaces.

When comparing the business value of Red Hat Enterprise Linux (RHEL) against other Linux distributions I have used, RHEL is prioritized for running business applications. Although some customers choose to use SUSE or Fedora, for production applications, Red Hat Enterprise Linux is the preferred choice.

I currently represent a Center of Excellence (COE) for Red Hat OpenShift, maintaining a business relationship with Red Hat.

For others looking to implement Red Hat technologies, my recommendation is significant. Since the Broadcom takeover, companies seem to be moving away from VMware virtualization to Red Hat OpenShift or Red Hat Virtualization, with many preferring OpenShift for migrating existing workloads to containerized formats.

My main use case for Red Hat Enterprise Linux (RHEL) involves server deployments and managing Python applications, including running ETL pipelines. I deploy Python applications while managing product data engineering workloads, server operations, troubleshooting, and automation.

A specific example of how I use RHEL for my workloads includes running my production PySpark ETL pipeline that processes millions of customer records. I manage all the Python environments, configure Spark jobs, monitor resource utilization, troubleshoot logs, and optimize batch processing in the backend processes. Using RHEL ensures reliable data ingestion and transformation for our backend.

Apart from running ETL pipelines, I also use RHEL for server administration, shell scripting, process monitoring, dependency management, and troubleshooting production issues. Tools such as SSH, Cron jobs, and supervisorctl help me manage and automate application deployments and background services, including systemd.

Red Hat Enterprise Linux (RHEL) is deployed on-premises at our organization. However, we have also utilized it as part of a hybrid infrastructure that combines on-premises servers with cloud-based environments, providing flexibility and security for sensitive production data.

We use Google Cloud Platform alongside our on-premises infrastructure for cloud-based workloads and data processing. I utilize RHEL in a hybrid environment with Google Cloud Platform, offering a consistent operating environment across both platforms that simplifies deployments, manages applications, and maintains security policies and configurations.

Red Hat Enterprise Linux (RHEL) has positively impacted my organization, which manages around 260 million customers. It has improved our production environment by providing better system scalability, security, reliability, and simplifying server management, which ensures our Python and PySpark workloads run consistently, ultimately enhancing our operational efficiency and reducing troubleshooting time.

Our overall operational efficiency has improved by more than fifty percent. Before using RHEL, we spent around seven to eight hours troubleshooting issues daily. Now, we save approximately twenty to thirty percent of that time, and troubleshooting server and deployment issues is around twenty to thirty percent faster due to better system monitoring capabilities.

We do not currently rely on Red Hat Satellite or Red Hat Lightspeed, focusing on RHEL's inbuilt tools. RHEL resolves pain points related to production stability, security management, dependency issues, server configuration consistency, and troubleshooting in our hybrid environment with Google Cloud Platform and on-premises servers.

The best features of Red Hat Enterprise Linux (RHEL) that I have seen include stability, security, enterprise-grade performance, long-term support, and reliable package management. SELinux security, system monitoring tools, automation capabilities, and compatibility with cloud and container platforms make it reliable for running production applications and large-scale data engineering workloads.

Regarding SELinux security, it provides an additional layer of security through mandatory access controls, which helps me restrict applications and processes from accessing unauthorized files or resources, even if compromised. This feature is particularly useful in my daily work for running Python applications and PySpark jobs in production, as it reduces security risks without requiring constant manual monitoring, saving a lot of time.

Another feature I appreciate in RHEL is its integration, particularly with Podman and container technologies. Its system management and automation capabilities through tools such as DNF, systemd, and Cockpit make package management, service monitoring, and troubleshooting much easier, providing a secure, stable, and consistent environment for managing production workloads.

Regarding RHEL's capabilities in governance and security, especially with AI, I believe they are paramount. Protecting sensitive data, controlling access to AI workloads, and maintaining audit trails are essential in enterprise environments. Features such as SELinux, role-based access control, and secure container environments provide a strong foundation for RHEL's use.

To navigate security risks, I primarily use SELinux for user and role-based access controls, along with SSH security and regular security patching through package management. SELinux is particularly effective in restricting unauthorized access between applications and system resources, helping me protect production data efficiently.

RHEL supports our compliance efforts through system-level security controls, access management, audit logging, and SELinux policies. I track user activities, monitor privileged access, and maintain visibility of system changes. I see post-quantum cryptography as an important future requirement and am interested in adopting quantum-resistant encryption as organizational standards evolve.

I primarily manage CVEs through regular security updates and system patching using DNF and RHEL security advisories. I monitor relevant CVEs, assess their severity and impact, and prioritize critical vulnerabilities for immediate patching, reducing our exposure to vulnerabilities and maintaining secure, stable production environments.

I have some exposure to system roles in RHEL, which are particularly useful for automating server configurations. I use Image Builder to create standard system images with predefined packages and configurations, reducing manual effort and minimizing configuration errors for more repeatable deployments.

RHEL supports our zero-trust approach primarily through access controls, SELinux policies, file permissions, and encryption. This ensures that all applications and users only access the data they are authorized to use while protecting sensitive customer information through secure data transfers, restricted database access, and audit logging.

RHEL has helped me run AI and machine learning workloads in a stable environment, with SELinux protecting my AI applications and model-serving processes by restricting unauthorized access. Container technologies such as Podman help isolate workloads, while Python support and system monitoring simplify development and deployments for managing pipelines and AI services in production.

I use Ansible Automation Platform with RHEL. My experience with Ansible involves package installation, service management, and environment configuration, allowing for consistent deployments across servers while minimizing manual intervention and reducing configuration errors.

I have one suggestion for improving Red Hat Enterprise Linux (RHEL). While it is reliable, I believe package dependency management and major version upgrades could be simplified with better compatibility handling. Additionally, I would like to see more user-friendly troubleshooting tools, such as clear error messages and easier integration with modern Python and data engineering environments.

I would like to see more practical real-world documentation, especially for production deployments, performance tuning, and troubleshooting, as well as faster resolution of support tickets, which could greatly benefit developers such as myself.

Accuracy and reliability are critical for enterprise AI workloads. While RHEL offers a stable and secure environment, actual output accuracy depends largely on the models, data quality, and configurations used. I would like to see stronger built-in model validation and monitoring capabilities to ensure consistent, reliable outputs in production.

I have been using Red Hat Enterprise Linux (RHEL) since around four years ago.

RHEL is very stable and reliable, making it suitable for production workloads. Its updates and enterprise support minimize downtime.

RHEL supports our scalability needs for growing workloads, particularly for Python applications, PySpark jobs, and large-scale ETL pipelines, enabling scaling across physical servers, virtual machines, cloud environments, and containers.

I rate the RHEL knowledge base as good overall, with comprehensive official documentation that covers system administration and security troubleshooting. However, I believe it could be enhanced with more practical real-world examples and better coverage of modern technologies such as Kubernetes, Docker, and AI workloads.

Customer support is good, with helpful technical documentation and access to expert assistance for production issues. However, I believe the response time for complex technical issues could improve significantly.

I would rate customer support a seven out of ten.

Since we began using RHEL, we have not switched to any other enterprise Linux solution. RHEL has been part of our infrastructure for four years, providing us with scalability, security, and enterprise support.

We have experienced operational benefits, including reduced troubleshooting efforts and consistent deployments, estimating around a twenty to thirty percent decrease in time spent resolving routine infrastructure issues while improving production stability without reducing headcount.

Licensing and setup costs are managed by the company. RHEL has a higher licensing cost than free distributions such as Ubuntu and Debian, but I believe the cost is justified for enterprise environments due to official support, security updates, and long-term maintenance.

RHEL offers stronger business value in enterprise environments compared to general-purpose distributions such as Ubuntu, particularly in terms of enterprise-grade security, SELinux, long-term support, predictable updates, and centralized management capabilities. While Ubuntu is simpler and flexible for development, RHEL provides greater confidence for production workloads and stability.

Beyond Ubuntu, I have experience with Debian, which is lightweight and flexible. While Ubuntu offers a developer-friendly ecosystem, RHEL stands out with its strong enterprise-focused capabilities, including SELinux security, lifecycle management, predictable updates, enterprise support, and Ansible integration that reduces operational risks and simplifies infrastructure management.

Before choosing Red Hat Enterprise Linux (RHEL), we evaluated Ubuntu, Debian, and CentOS, comparing them based on security, stability, support, and licensing cost. RHEL stood out for its enterprise-grade security, predictable lifecycle, and vendor support.

I would rate Red Hat Enterprise Linux (RHEL) a ten out of ten overall.

I choose a perfect score for RHEL because it significantly reduces the troubleshooting nightmare that developers face, enhancing its overall efficiency.

While I have not independently managed a complete RHEL version upgrade using Ansible Automation Platform, I have observed that Ansible is useful for automating pre-upgrade checks, validating configurations, and managing dependencies, significantly reducing manual efforts while ensuring consistency.

My advice for others considering Red Hat Enterprise Linux (RHEL) is that it is a secure, stable, and enterprise-ready Linux distribution, particularly useful for production environments and large-scale data workloads, where the long-term support and automation capabilities justify the licensing cost.

My use cases for Red Hat Enterprise Linux (RHEL) at my company include application servers, infrastructure servers, web servers, and virtually every server type.

The features of Red Hat Enterprise Linux (RHEL) that I appreciate most are ease of automation and ease of deployment, particularly because we also use Satellite for deployment management. It scales well.

These features benefit my company by resulting in less time spent working on servers and issues and more uptime.

I have not identified any immediate areas for improvement in Red Hat Enterprise Linux (RHEL), as I cannot think of anything that there is not already a product for.

We have encountered some issues with the high availability clustering lately, and it seems that could use some refinement.

The deployment process for Red Hat Enterprise Linux (RHEL) has been somewhat rough around the edges to get it up and running with Kickstart, but once I have it dialed in, it is fantastic. The documentation for Kickstart can leave something to be desired sometimes, so that may be an area of improvement.

I have been using Red Hat Enterprise Linux (RHEL) for almost ten years.

I have not experienced any downtime, crashes, or performance issues with the platform that were not caused by some kind of misconfiguration. The platform itself is solid.

I have been able to scale and expand usage as my needs have grown.

I assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as outstanding. The Red Hat Learning Subscription is great, and usually when we enter a ticket with Red Hat support, we can get a subject matter expert to help us resolve our issues.

I would rate the customer service and technical support as probably an eight out of ten. Sometimes when we enter a ticket, it takes some time to get to the level of technical resource we need, but once we get that resource, they almost always help us get a problem solved.

When I came in, our department was already heavily using Red Hat Enterprise Linux (RHEL).

The deployment process for Red Hat Enterprise Linux (RHEL) has been somewhat rough around the edges to get it up and running with Kickstart.

From a technical point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the stability and uptime.

I have worked with Ubuntu and CentOS in the past while using Red Hat Enterprise Linux (RHEL), but I do not particularly care for Ubuntu. I prefer Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) wins over Ubuntu for me by being a more stable enterprise platform and more mature.

Red Hat Enterprise Linux (RHEL) helps me solve pain points by being more reliable and easier to work on than Windows. It is simply good at what it does.

The features in Red Hat Enterprise Linux (RHEL) that I use to navigate my security risks include Satellite, which helps us keep everything patched and up to date and keep package-related CVEs down. We are looking at doing OpenSCAP scanning with Satellite, and we use Ansible for automation, deploying configurations and packages. We are also looking at implementing OpenShift, as our department has OpenShift.

I have worked with System Roles and have used Image Builder before, finding it useful for tightening a gold image and standardizing deployments.

I use Red Hat Enterprise Linux (RHEL) only on-premises in my department. Some other departments might use it in the cloud. I do not know that my department has a cloud strategy yet, but I know we are exploring alternatives to VMware, so that could happen in the near future.

My department does not have a hybrid cloud yet, but as far as on-premises is concerned, Satellite helps us with patch management and controlling what packages we present through content views. We build systems through Kickstart, so it helps with deploying systems.

I have worked a little with Lightspeed for AI workloads with Red Hat Enterprise Linux (RHEL) but have not really scratched the surface too much yet.

Red Hat Enterprise Linux (RHEL) plays a critical role in my company's implementation of zero trust by tightening down configurations when we join a system to Active Directory through SSSD, locking down what users and groups can touch a given system.

We have used Leapp to do a major version upgrade using Red Hat Enterprise Linux (RHEL), but we have not coupled that with Ansible Automation Platform yet.

I have been using Ansible Automation Platform almost as long as I have been using Red Hat Enterprise Linux (RHEL); I used Tower before it was Ansible Automation Platform, and it is incredibly useful. It is invaluable for deploying systems, standardizing server builds, deploying compliance, and hardening. I have not found a use case it is not useful for.

We are working toward using or building Ansible jobs to help with our regulatory audits and evidence collection, and Red Hat Enterprise Linux (RHEL) plays a significant role in our compliance and auditing workflows.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk with capabilities such as its stability. If you standardize and deploy a system and have it tightened, you tend not to have unexpected issues, or the issues you do have are ones that you would have seen many times and can easily remediate.

I rate my overall experience with Red Hat Enterprise Linux (RHEL) as a nine out of ten.