That blog post is about the situation that the Prometheus Operator installed from the Community Catalog doesn't work anymore on a Kubernetes 1.23.6_1527 cluster version.
Maybe you will get the following error when you try to work with a go operator-sdk project you cloned from GitHub. MAKE: *** [GENERATE] ERROR 127
That blog post does focus on a basic installation of the Grafana operator to get an understanding how that operator basically works in the context to the two blog posts I made before
In the last long blog post we covered the topic Monitor your custom operator with Prometheus. That means we did a setup of a Prometheus operator and we created a Prometheus service instance. In our operator we registered an example counter called goobers_total at the Prometheus server to monitor the invocations for our controller inside the operator application. Now we want to access the counter information goobers_total by using the Prometheus HTTP API from a local Golang application.
This blog post provides an overview of various topics related to Red Hat OpenShift on IBM Cloud in a virtual private cloud environment I created. I have organized this overview into three main topics.
hat blog post does focus on a customized monitoring with Prometheus for a custom operator implementation build with the golang Operator SDK. For the monitoring we will use the Prometheus operator. Alain Arom and I inspected that topic and here we show you one example hands-on journey how to get the technical job done. There are a lot of materials out there, but in that blog post we follow an end-to-end scenario for a beginner to intermediate level (without any stop in the middle 😉 of the road). We will only focus on:how it basically works and not why or what we should do in monitoring.