We are currently in the midst of a POC phase with a standalone cluster. This cluster consists of both coordinator and worker nodes, with a metadata store for storing various metadata. The entire setup is deployed on Red Hat Enterprise Linux 8, and we have established a connection to the OpenShift UI.

While using it, we encountered far fewer complexities, and the entire process is much smoother and streamlined. For patching purposes, we simply need to communicate with our system administrator. They take care of the patching process, so we don't have to get involved and we can easily connect to the artifact repository and download the necessary artifacts to install in our system.

We have a set of JSON files containing YAML configurations where all the required image details are documented and this setup makes it very straightforward for us.As for the Web Console, if you're talking about the user interface for tasks like creating ports, deploying applications, managing secrets, and other functions, I haven't encountered any significant issues.

The process is generally straightforward and quick, taking just a few minutes. OpenShift offers two types of interfaces: one where you can edit YAML files for more advanced customization, and the other where you can use forms for faster deployment, though with fewer features.

Continuous improvement is essential to enhance user experiences and address evolving needs.

I have been working with it for approximately six months.

Our experience with its customer support is very good. Whenever we encounter any issues, we receive prompt and comprehensive assistance. There's no need to wait or take any additional steps to get the help we require, which is highly appreciated. I would rate it nine out of ten.

In the past, our work primarily involved Hadoop, and we also dealt with Solid Cloud for security and other purposes, but we found that this setup was slow and not open source. On the other hand, the DLP solution we're currently using is not only cost-effective but also significantly faster.

I also used a Linux browser, specifically the KCL browser which required me to go through the process of installing packages and various components, while in the current setup, everything is seamlessly connected. We simply use the OC command with a private key to connect to OpenShift. There are no extra or additional steps required, making the whole process exceptionally fast and efficient. It's quite remarkable and makes the workflow truly hassle-free.

The initial setup was easy.

The deployment process is straightforward. I simply had to deploy the images using OC commands, and the process of connecting to OpenShift was remarkably fast and smooth.

Overall, I would rate it nine out of ten.

Our use case for Red Hat Enterprise Linux is for production applications.

We are a Managed Service Provider. Red Hat Enterprise Linux enables us not to be worried about vulnerabilities, security, and patching.

The most valuable features are the subscriptions and upgrades.

We need to have more flexibility on the developed versions. Not everybody is ready to subscribe to enterprise versions. They would like to test the tool without subscriptions.

We chose Red Hat Enterprise Linux because of its security.

We use Red Hat Enterprise Linux with AWS. We started our practice with AWS, and most customers use it instead of GCP or Azure. We use the product in a hybrid environment, mostly when shifting the containers or existing workloads from legacy systems.

Most of the customers use Red Hat Enterprise Linux because it is the only approved OS. The tool's knowledge base is good but is limited to subscriptions.

The upgrade migration is straightforward. For the initial projects, we used to execute CLI scripts. We plan to upgrade the system if everything works well in the lower environment.

I have used the image builder feature. I rate the overall product a nine out of ten.

We use Red Hat Enterprise Linux for VMs and physical servers.

The containerized platform will help us use ROSA.

The tool's most valuable feature is OpenShift. We plan to move all our applications to microservices. The container platform is integrated into one.

I opened a few cases, and the tool's support responded quickly.

Deployment is simple if you have been using the solution for a long time. However, it can be complex if you are new to it.

We use RHEL 7 and RHEL 8 on on-premises. RHEL 8 is on the AWS. There is a security policy like CIS when deploying the solution. You can embed it on the image. I am not sure if there is HIPAA compliance yet.

Migration from RHEL 8 to RHEL 9 is easy. Upgrade depends on the application that is running on each instance. You need to check if it is compatible with the kernel. We need to plan things before migrating to the latest version. We need to stay current to ensure compliance. We plan to move from RHEL 7 to RHEL 9 and use RHEL 8 and RHEL 9.

We use Red Hat insights but do not utilize them. It helps with the remediation. I use Image Builder to build AWS and GCP images. I haven't deployed them.

I rate the product a nine out of ten.

We have over a thousand VMs or physical machines running on Red Hat Enterprise Linux. We have various applications, and we also run the OpenShift Container Platform on-prem, so we have a lot of containers. They are migrating a lot of apps from the mainframe over to Spring Boot type of app. It fits well in the container.

Red Hat Enterprise Linux gave us stability. There is somebody to call when we have issues.

Red Hat Enterprise Linux has affected our system's uptime or security.

Red Hat Enterprise Linux has not yet enabled us to achieve security standards certification because we do not go after any of those. There are some products that we will have to do once we get there, but so far, we have not had to certify anything.

Red Hat Insights gives a lot of insights into known issues that we do not think about unless we call support. It tells us to proactively fix something.

I have used Image Builder and System Roles mainly for Red Hat Enterprise Linux for Edge. It builds out the OS tree build for us, which is very helpful. I do not like to do that myself.

I use the Red Hat console every now and then, but I do not use it heavily. I am old school.

The security updates and the support that comes along with it for applications are valuable.

Red Hat Insights was a nice feature to discover. I did not know about Ansible until probably eight years ago. I learned that language, and that was a void or something that was missing for over 25 years.

I like the SCAP Workbench interface that I can use to build some security around. I use Ansible to go out and do configuration management checks as well. Overall, I feel it is very easy to get the data I need.

We finally started doing Red Hat Enterprise Linux for Edge. That one definitely is an improvement. One piece that is missing is that we are required to use moby-engine, but currently, Red Hat Enterprise Linux for Edge forces Podman, so we have to work around it.

I have been using Red Hat Enterprise Linux for a decade in my current organization, but overall, I have been using Red Hat for over 25 years.

Early on, support was closer to a six, but now, it is a nine out of ten.

I have used them all back from the early nineties. I have used CentOS and others. The reasons for companies switching from those to Red Hat Enterprise Linux are that most of it is open source, and they get more product features. There is a market. If other companies are doing it, they tend to switch over. Containerization is a major reason as well.

I was involved in the OpenShift deployments. We are also directly involved in every version of Red Hat Enterprise Linux. We are involved in the proof of concept. Its deployment is straightforward.

We used Red Hat with the OpenShift deployments to make sure we were doing it right, and then a lot of other things, such as Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 9, we just did ourselves.

In terms of our upgrade and/or migration plans to stay current, we are upgrading everything to Red Hat Enterprise Linux 8, and we are going to Red Hat Enterprise Linux 9 already. We are making that a product feature. We are using Red Hat Enterprise Linux for Edge for our remote deployments.

In terms of provisioning and patching, we deploy the base image, and then we use Ansible for the configuration behind it. For Red Hat Enterprise Linux for Edge, we use the OS builders to build out that same image. I use Kickstart to build the base image before the configuration.

I do not track that in the company, but I am sure we have seen an ROI.

It seems to be fair. It is not overpriced. I went to the simple model, and that makes it easier for us to deploy.

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

We host our applications and database servers on Red Hat Enterprise Linux.

We mostly have an on-premises setup. We also have Red Hat Enterprise Linux running on a virtual machine.

Compared to our previous Unix distro, it is pretty easy and less time-consuming to do patching and maintenance. It saves a lot of time during maintenance.

I started with Solaris 10, and then we migrated to Red Hat Enterprise Linux. Apart from local zones and a few other things, its features are similar to Solaris 10. It is getting our job done. It is hardware-independent. We can use Dell, HPE, or any other hardware. It is also more reasonable than the other operating systems.

It integrates closely with other products of Red Hat, such as Ansible, which makes it more efficient.

I have been using Red Hat Enterprise Linux since 2010.

We are getting all the support that we need on a timely basis. In the case of any issue, we are getting all the support needed to bring the production back online. I would rate them a nine out of ten.

We were using Solaris 10. We moved to Red Hat Enterprise Linux because it is cost-efficient and hardware-independent.

I am a part of the team that does the OS deployment. Its initial deployment is straightforward. We use automation for deployment. We have a kickstart to deploy the OS. Once we create that kickstart configuration file, the deployment is straightforward.

In terms of our upgrade and migration plans to stay current, we upgrade it before the OS is end of life. It is pretty straightforward. We are pretty satisfied with Red Hat Enterprise Linux systems when it comes to provisioning and patching.

We deployed it on our own.

It is cost-effective.

There were not many options available.

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

We predominantly use Red Hat CoreOS we use it to connect to different types of OpenShift clusters. Whenever I work with RHEL, it's always been with the CLI.

Previously, when we were using other distributions, we weren't getting a lot of support for the operating system itself. However, Red Hat has mainly focused on the operating system, so we get more support.

AWS has its own version of Linux for its instances. All these cloud providers provide more support for the infrastructure and services, but they don't focus on the operating system itself. But Red Hat, with its customer portal, provides better support if something goes down. That's what differentiates RHEL from other products.

One great thing about RHEL is that it has a big community of users. There's a huge community that uses CentOS. If you need some help or have a question online, you get more resources for RHEL compared to other products.

It's a really good operating system by itself. It's more versatile, integrating with tools like Ansible for automation.

There are amazing resources online, and because we are an enterprise, we have enterprise support. We can always create a support case, and we have some resources to help. The knowledge offered by Red Hat is great.

Another feature I tried was RedHat Insights because they offer it for other RedHat products as well. I've used it for OpenShift. It was helpful. It provides a good, in-depth understanding of what's going on in the actual infrastructure. It gave us good insights into the level at which we can run the containers and if you can scale the infrastructure vertically or horizontally and how to manage it better.

There is room for improvement in integration with different cloud platforms. There should be better integration because right now, a lot of cloud platforms have their own versions of Linux, which runs better on them, and they have better integration with the services. RHEL is great, but RHEL is more of a generic form of what Red Hat provides.

I've been using RHEL for about four years now.

There were certain times when I encountered issues. There are certain problems with integrations.

For example, we had an issue once where the operating system had issues accessing the data server on our VMware infrastructure. So we did have a couple of engineers help us out with that, but that's one area where it can improve. But that's nitpicking.

It's been great so far, but that's one thing I would like to see that would make RHEL a little better product.

We prominently use RHEL, but we've also used Ubuntu. We also have used PCF. I use Ubuntu Xenial and have worked with Amazon Linux for a while.

One pro is that at the operating system layer, RHEL has better support from Red Hat, and if something goes down, I found many resources for troubleshooting online.

For example, we predominantly use Amazon Linux if I'm using AWS. There aren't a lot of resources if I run into an issue. RHEL has way more documentation on Linux. It has a bigger community, from an operating system perspective.

One of our deployment models is on-premise, and the other is on the cloud. It's a hybrid. We have a big footprint on the cloud.

We use Azure because a lot of resources are already deployed on it. We can use all the features I build on RHEL, but you can scale up the infrastructure, depending on the demand. That's the reason why we use Azure.

For the upgrade process, we mainly use Ansible automation. Whenever we want an upgrade, we just go into the Ansible Tower, change the version, and make sure we are applying that to the right environments so that there's no outage.

Overall, I would rate the solution an eight out of ten.