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 →
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.
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).
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).
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.
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.
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).
This blog post is about: How to run the example Multi Tenancy Frontend Operator as a deployment on a Kubernetes cluster.
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.
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?