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?

Write your first simple Kubernetes Operator

Even a student with minimal knowledge of Kubernetes should be able to install a highly complex container-based application on top of Kubernetes or OpenShift. Eliminate the manual interaction effort as much as possible to deploy, run, and maintain your containerized application on Kubernetes or OpenShift with your Operator implementation.

Blog at WordPress.com.

Up ↑