kubernetes-operator-orchestration-example

The project is a demonstration of how Kubernetes, can be leveraged as an orchestration engine for managing applications and workloads. This project showcases the implementation of Kubernetes Operators, a Kubernetes-native pattern, as the driving force behind streamlining and automating the management of applications and services within a Kubernetes cluster.

Description

The Operator automates the process of tracking coin flips and identifying when three consecutive tails appear. When the condition of three consecutive tails is met, the Operator interacts with a message queue system to send a notification.

Getting Started

You’ll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster. Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Running on the cluster

1. Install Instances of Custom Resources:

kubectl apply -k config/samples/

2. Build and push your image to the location specified by IMG:

make docker-build docker-push IMG=<some-registry>/kubernetes-operator-orchestration-example:tag

3. Deploy the controller to the cluster with the image specified by IMG:

make deploy IMG=<some-registry>/kubernetes-operator-orchestration-example:tag

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Undeploy controller

UnDeploy the controller from the cluster:

make undeploy

How it works

This project aims to follow the Kubernetes Operator pattern.

It uses Controllers, which provide a reconcile function responsible for synchronizing resources until the desired state is reached on the cluster.

Test It Out

1. Install the CRDs into the cluster:

make install

2. Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):

make run

NOTE: You can also run this in one step by running: make install run

Modifying the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation