Access Prometheus queries using the Prometheus HTTP API

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.

Monitor your custom operator with Prometheus

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.

Add a conversion webhook to an operator to convert API versions

In that blog post we will add a webhook to our existing operator project Multi Tenancy Frontend Operator in the branch update-operator were we created the v2alpha2 API version for the operator in the last blog post "Add a new API version to an existing operator". The final implementation for the current blog post you find in the webhook-gen-operator branch. (details about conversion webhook) Yes, that … Continue reading Add a conversion webhook to an operator to convert API versions

How to extend a Custom Resource Definition for a GO Operator?

That blog post is about some basics how to extend a Custom Resource Definition in a GO Operator. For an Operator implementation you need a Custom Resource Definition and a controller implementation. The Custom Resource Definition for an operator is the basic first step to extend the Kubernetes API with your own functionalities. Usually you create a Custom Resource Definition before you write the controller for your operator.

How to delete services, secrets, and deployments related to a¬†Custom Resource Object¬†in a GO Operator?

This blog post is related to the blog post DEVELOP A SIMPLE OPERATOR TO DEPLOY A WEB APPLICATION USING THE GO OPERATOR SDK. In that last blog post we addressed the topic get a web frontend application running on Kubernetes using a GO Operator. An important part in that scenario is also, how to manage the clean-up for an application instance and it’s related Kubernetes resources and objects created by the operator based on the Custom Resource Object, or: How to delete services, secrets, and deployments related to a Custom Resource Object in a GO Operator?