Let’s look at step by step how to enable resource monitoring on OpenShift. Container application resources monitoring is simplified with Operator Hub, Prometheus Operator and OpenShift. With the built-in resource monitoring on OpenShift, your application team will just need to focus on application development and at the same being able to get performance feedback from Prometheus on OpenShift.
Creating your own version of container image for Kafka Connect for OpenShift is pretty straightforward with simple few steps as outlined in this article.
Red Hat Fuse is base on Apache Camel, an open source project to allow developers to implement integration services quickly and easily. This article and the demo asset demonstrate one possible way of how to implement the integration service using Red Hat Fuse. With the enriched list of technology and components brought by Camel, you may find a different way to implement the same solution. This is where the EIP (Enterprise Integration Pattern) is in placed to ensure however the developer is implementing the integration, it will be ensured the developers are following the best practices outlined by the EIP. With the nature and flexibility of Camel integration approaches, we also see how easy it is for us to implement endpoints integration, message marshalling and unmarshalling, and most importantly how we can embrace reusability allowing us to bring our solution to market faster.
In this article, we look at how to deploy Apache Kafka on Red Hat OpenShift 4, using reasonable sample microservice applications to showcase the endless possibility of innovation brought by OpenShift and Kafka.
Many people have done continuous integration and continuous delivery (CI/CD) for .NET Core, but they still may wonder how to implement this process in Red Hat OpenShift Container Platform (OCP). The information is out there, but it has not been structurally documented. In this article, we’ll walk through the process.