My organization has different departments. In my department, we mostly work with containerization. I am using Red Hat Enterprise Linux as a part of OpenShift. I use the basic package and base image of Red Hat Enterprise Linux.

For scale-up in our platform, we use CoreOS as the master, and for the workers, we use the Red Hat Enterprise Linux service. From OpenShift version 4.10 onwards, we cannot use Red Hat Enterprise Linux 7 worker nodes. We were using Red Hat Enterprise Linux 7 worker nodes, so we upgraded to Red Hat Enterprise Linux 8. 

For OpenShift, there are some recommendations from Red Hat in terms of what needs to be used for the control plane and what needs to be used for the worker nodes. When you are using CoreOS and Red Hat Enterprise Linux worker nodes, there are some difficulties in managing them. For example, when you upgrade OpenShift, you need to upgrade two times. The control plane is upgraded separately because it uses CoreOS. The control plane has a lot of certificate updates that will in turn be updated on the worker nodes, so you have one restart of all worker nodes, and then when you need to upgrade your worker nodes, there will be one more restart. 

Overall, you have two reboots in your production environment, which is an issue, but it is related to your choice of product in your environment. We have this issue because we opted to use Red Hat Enterprise Linux 7 or Red Hat Enterprise Linux 8 worker machines, whereas Red Hat recommends using CoreOS because it is pretty fast in terms of rebooting and functionality. When you upgrade the control plane, that itself will update the worker nodes, so you are done in one shot. When you need to upgrade your Red Hat Enterprise Linux machines, you need to use the Ansible Playbook. You can then upgrade to Red Hat Enterprise Linux 7, 8, or any other version. Regardless of the versions, you can upgrade the operating system and the OpenShift version. For this purpose and for some ad-hoc activities, we are using Ansible Playbooks.

For us, its security, management, stability, and hardening are most valuable. All of these features are better in Red Hat Enterprise Linux as compared to Microsoft Windows.

Red Hat Enterprise Linux is very good in terms of risk assessment. It is also good for maintaining compliance. It is better than Microsoft Windows.

From the administration perspective, I do not have any issues with Red Hat Enterprise Linux. For me, it is more convenient than Microsoft Windows.

My organization has been using Red Hat Enterprise Linux for a long time. They have been using it before I joined the organization.

It is pretty good in terms of stability. It is a stable product. I would rate it a nine out of ten in terms of stability because sometimes the packages can have bugs.

Its scalability is good. I would rate it a nine out of ten in terms of scalability.

We never encountered any issues while using OpenShift.

I have mostly been working with Red Hat Enterprise Linux. 

I have been involved in the deployment of OpenShift. It is pretty straightforward. We just need to get the licensing, and we just need to create a pool for our containers session in Red Hat Satellite. We can do the configuration from there. It does not take long because we are adding the nodes to OpenShift. During the scale-up process, we only need to subscribe to the nodes with the Red Hat subscription. It does not take much time. If we have a good spec, the scale-up would not take much time. It would take less than twenty minutes. It is pretty fast.

In terms of maintenance, when we have the bug report, we need to do the security assessments. Over time, there might be some bugs related to some packages. At that time, if it is critical, we will be scheduling a maintenance activity on our platform. 

Red Hat provides high availability from the application perspective. You get high availability when you are using OpenShift, so when you are doing a maintenance activity on the OpenShift side, there would not be any downtime. The high availability is very good. For the end-users, there would not be any application outages if you configure your application with proper replicas. They would not even realize that there is a maintenance activity happening to the underlying workers.

It was implemented in-house.

We did not evaluate other solutions. Red Hat Enterprise Linux is the choice of most of the companies.

If you want to integrate with OpenShift or build an OpenShift cluster with the master Red Hat Enterprise Linux and worker Red Hat Enterprise Linux, you can do that, but you need to plan your upgrade or maintenance activities. It would be better if you choose CoreOS for both. CoreOS would be a better choice in terms of maintenance activities or upgrade activities in the future. If you cannot afford that, you can go with the Red Hat Enterprise Linux operating system, but you need to do two upgrades. You first need to upgrade the control plane and then you need to separately update your worker nodes. That is the only thing you need to keep in mind.

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

We use Red Hat Enterprise Linux mostly for development.

We use Red Hat Enterprise Linux with Git apps in our closed environment to develop and run scenarios.

Red Hat Enterprise Linux's documentation could be improved. Sometimes when you call up support to have that Red Hat answer, they send you back a Reddit or Google link. I can Google or go to Reddit, but I want an answer from Red Hat.

I have been using Red Hat Enterprise Linux since it started back in the 1980s.

I rate Red Hat Enterprise Linux a ten out of ten for stability.

I rate Red Hat Enterprise Linux a ten out of ten for scalability.

I rarely call Red Hat Enterprise Linux's support, but when I do, they send me a Google link.

Neutral

Since I've been deploying Red Hat Enterprise Linux for so long, it's not complex for me. Once we configure our kick start, we power up a new system, attach it, and it builds it.

We implemented Red Hat Enterprise Linux directly through Red Hat.

We have seen a return on investment with Red Hat Enterprise Linux concerning the ability to develop what we need, what we do, and our scenarios. The solution saves us man-hours, and man-hours equals money.

We cannot use Red Hat Enterprise Linux on the cloud because I work as a contractor for the government, and all our development is in a classified area where we can't touch the internet at all.

In the last quarter, Red Hat Enterprise Linux products like Satellite Server and OpenShift stood out because of their ease of administration. I do system administration. When my customers need something, assisting them with these products is easier than giving a long configuration of YAML.

I like Red Hat Enterprise Linux's built-in security features. We use their SCAP features when we do our kickstart and build it.

We were using Docker, and the Docker swarm was trying to get all the containment. We're now switching to Podman and getting our developers to learn that more so we can give them the ability to kick off containers.

Overall, I rate Red Hat Enterprise Linux a ten out of ten.

We deployed Red Hat Enterprise Linux on-prem and in the cloud as a fallback.

We are a private cloud provider and we host Linux ourselves because they are tough to manage.

We offer our customers the option to host their Red Hat Enterprise Linux on Azure or on our private cloud.

Red Hat Enterprise Linux's built-in security features help simplify risk reduction. Red Hat offers a subscription service that provides critical security updates within 24 hours. The service also includes an excellent database of known security vulnerabilities. If a CVE identifier is known for a vulnerability, it can be entered into the web interface. The web interface will then indicate whether Red Hat Enterprise Linux is affected by the vulnerability and what steps need to be taken to fix it. The fix will be included in the next security update. This is a valuable security feature that helps organizations to stay up-to-date on security patches and mitigate risk.

The portability of applications and containers built on Red Hat Enterprise Linux is beneficial for keeping our organization agile. Red Hat Enterprise Linux 8 and 9 include Podman, a newer software similar to Docker. Podman was built to address the problems that Docker had with creating and running containers, and it also includes the support of Red Hat. There is a good synergy between Red Hat and Podman.

Red Hat Enterprise Linux has helped improve our organization. We provide a service to our clients, which they pay for each month. This service includes our support. Red Hat Enterprise Linux is a stable operating system, so we do not have to provide much support. When we do need to provide support, it is usually for an application, not for the operating system.

I can build with confidence and ensure availability across physical and virtual cloud infrastructures using Red Hat Enterprise Linux. I have been using Red Hat Enterprise Linux on-premises since 2008 without any problems. It is easy to automate. Virtualization is always present, so I work with virtual machines. Red Hat Enterprise Linux is very easy to deploy on a virtual machine. We can create a virtual machine, and if we are working with VMware, we can create a template to use for new systems. There is no need for a classic installation.

The updates are the most valuable feature. In the past, we had 800 or 900 Linux systems with Red Hat, and all of the systems were updated every night. In the 14 years, we have only had ten issues with the updates.

Red Hat Enterprise Linux has a good configuration.

Red Hat Enterprise Linux is secure but the security always has room for improvement.

Scaling can be complicated and has room for improvement.

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

Red Hat Enterprise Linux is stable.

I give the stability an eight out of ten.

I give Red Hat Enterprise Linux a seven out of ten. 

Updating Red Hat Enterprise Linux from version 8 to 9 is a complex and time-consuming process. It is often easier to install a new server with Red Hat Enterprise Linux nine and migrate our data and applications. However, if we only need to resize the CPU or memory of our existing server, we can do so using the hypervisor without having to reboot.

Red Hat support is fast, and they are capable of answering 90 percent of our questions.

Positive

We previously used Debian, Ubuntu, and SUSE Linux. In our case, if we wanted a conservative Linux system that did not have the newest version, these were perfect systems. However, if we wanted to install them on our laptops or on our clients, they were the wrong solution. We switched to Red Hat Enterprise Linux for the Red Hat support. Debian also offers its own support. Ubuntu does not offer direct support, so we were required to order it through another company. SUSE had other problems that we did not want to deal with. Red Hat Enterprise Linux support has been very helpful to our back-end admins.

The initial setup is complicated, but with Red Hat Enterprise Linux nine, there is a graphical web interface where we can create a new image every week. We have created a golden template that enables us to update the image every month and upload it to both our private and public clouds for usage. 

The deployment time depends on whether we have a template or not. With a template, deployment can take between five and ten minutes. If we have to install the software, the time it takes depends on our internet bandwidth. Ten gigabits of bandwidth can take around 15 minutes to install.

The implementation was completed in-house.

As a provider, we must follow a different licensing model. We charge €2,000 per system for three years. Each month, we provide Red Hat with a number of new and old systems. Red Hat then invoices us based on the number of systems in use that month. This only applies to our cloud customers.

I give Red Hat Enterprise Linux a ten out of ten. Red Hat Enterprise Linux is the best thing I have.

We always install a minimized Red Hat Enterprise Linux system for our customers. If they require more features, we provide them as requested.

Red Hat Enterprise Linux is the most perfect OS I have ever worked with. It is nice knowing when we have to use the OS and when we don't.

All Linux solutions are open source, but Red Hat Enterprise Linux is a commercial product that includes support and frequent updates. Red Hat Enterprise Linux can be downloaded for free, but it is not recommended to use it without a subscription, as it will not receive security updates or bug fixes. Red Hat reinvests a portion of the subscription revenue back into open-source projects, making it possible for other organizations to use these technologies for free.

Maintenance requirements depend on our needs. If we only want to have a server and install updates every night, no additional maintenance is required. Red Hat Enterprise Linux does not require any special support. However, if we want to ensure that the system time is always correct, that all updates are installed within a month, and that the system reboots after updates are installed, we will need to perform some additional maintenance tasks. These tasks can be automated to ensure that our system is always running smoothly. We currently have three people for the maintenance. We currently have 900 systems.

I recommend evaluating multiple Linux solutions and conducting a proof of concept because, although Red Hat Enterprise Linux is a great operating system, it may not be the best choice for every organization. I do not recommend using Red Hat Enterprise Linux on a new laptop because the versions included in Red Hat Enterprise Linux are typically two to four years old. This is because Red Hat Enterprise Linux is designed to be a stable OS, and newer versions may not have been fully tested and may have issues. If we have a server or software that is certified for Red Hat, then I would always recommend using Red Hat Enterprise Linux.