Our use of RHEL has been orthogonal to our exploration of OpenShift and Kubernetes. We have experimented with using minimal footprint RHEL instances inside containers to minimize the total size of our containers.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
It's probably less appropriate for databases. I don't know anybody else's doing a lot of databases to have databases on with RHEL, but everything else it does well from applications to now AI with AI models does it all in my opinion.
Virtualization, like the operating system level task. I see this product is very good and it blends very well with the middleware components like all the JBoss and other things. And other than that, either you install it or a virtual machine or physical servers, it works seamlessly anywhere. And if you want to go further, like Red Hat OpenShift or those things also work very nice with it.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Well, one of the things, this ties right back to my previous answer from what it sounds like, the cloud platform for Insights doesn't currently have an easy way to generate CVE compliance reports, or do scans for where you have remediations required, but it does not currently produce those reports in a way that I could just hand off to our security team and be like, here's our compliance, here's where all the things are specifically because Red Hat does backporting of patches and a lot of security tools don't know how to handle that and think that we're vulnerable when we're not. So from everything I've heard, it's possible. That's why I'm excited for it. But it's not easily pushed button generated report yet. So we're working with them to get that in there.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
The Red Hat Enterprise Linux (RHEL) distro is the simplest enterprise version of Red Hat that is enterprise supported and when you deploy as many VMs as we do, it is vital to have that enterprise support. On top of the enterprise support, having access to a commercially supported backbone for updates and upgrades is a huge plus.
Red Hat support has really come a long way in the last 10 years, The general support is great, and the specialized product support teams are extremely knowledgeable about their specific products. Response time is good and you never need to escalate.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
So we in our company have used Ubuntu as well. Sometimes we have to use that because a certain application installer requires that we use that operating system, but we really don't prefer it just because it doesn't come with the same Add-on features that make Red Hat Enterprise Linux (RHEL) really great, like Red Hat Insights or Red Hat satellite, things like that. They come package with it. So that would be the main one. I've also used things like FreeBSD, but I think that's just too old at this point to care.
