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?
In this blog post I want to share how to debug a GO Operator on your local machine on macOS. Adam de Leeuw and I verified it in different GO operator projects. Sometimes you find on Google information which uses the older Operator SDK. The following instructions worked for us in March 2022. 😉
This blog post is just a list or let me say this is an addition to my last blog post Let’s get started with the development of operators using the GO SDK "one additional road" to get started with operator development from a more technical perspective.
This blog post is a bigger cheat sheet about how to start with an operator implementation with the GO Operator SDK and also contains some details how to define Kubernetes deployments, secrets, and services.
That new blog post is related to start with development of operators using the GO API. I want to point to some resources which are from my personal perspective are an incredible combination to start and I want to highlight some major points which are relevant in that context.