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.
Overview of blog posts I made related to Red Hat OpenShift on IBM Cloud in a Virtual Private Cloud
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.
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 →
A simple GO operator development learning journey
This is about a personal GO operator development learning journey you can follow along the different blog posts I made about the GO operator development using an own (mostly ;-)) simple example called Multi Tenancy Frontend Operator.
Add a new API version to an existing operator
This is my next blog post related to operators. That blog post is about adding a new API version to our existing example Multi Tenancy Frontend Operator. When we have added the new API version we will deploy the changed operator to a Kubernetes cluster using the Operator Lifecycle Manager (OLM).
Deploy an operator without the Operator SDK
That is the next blog post related to operators. Now it’s about deploy an operator without the Operator SDK. In the last blog post we used the operator-sdk run bundle command which created for us all needed specifications and images to run the bundle. Therefor we need to take a closer look into the Operator Lifecycle Manager (OLM).
Setup an Operator SDK on Ubuntu in a Virtual Server Instance
That blog post is about a partly automated setup of an Operator SDK on an Ubuntu Virtual Server Instance on IBM Cloud. The setup is automatically verified by cloning and building an operator bundle.
Run an operator using a bundle with an Operator Lifecycle Manager (OLM)
In that blog post we focus on get the operator installed using the bundle running on a Kubernetes cluster with an Operator Lifecycle Manager (OLM) installed. Surely, the Go Lang tutorial and Getting started OLM can be useful in that context.
How to create a bundle for an operator?
In that blog post we will focus on: Creating a bundle for the example operator. That bundle will be used to install the example frontend operator using an Operator Lifecycle Manager (OLM).
