On the 19th of December, Lungelo Sikobi and I delivered a workshop on OperatorHub on Red Hat OpenShift as part of the IBM Developer Series.
In the workshop, we gave an overview of Operators and OperatorHub then we moved on to the code lab where we demonstrated the OpenShift Serverless Operator.
In this blog, I’m sharing an overview of the workshop which you can also watch the replay of here.
What are Operators and what is OperatorHub?
A Kubernetes operator is a method of packaging, deploying, and managing a Kubernetes application. This application is both deployed on Kubernetes and managed using the Kubernetes API and kubectl tooling.[1]
Red Hat OpenShift uses Kubernetes operators to run the entire platform autonomously and as part of OpenShift, you can use these operators through OperatorHub where you can install a library of operators that have been packaged for easy lifecycle management and you can use them in your cluster.
What is OpenShift Serverless Operator?
Serverless is a deployment model where you can scale up and down your applications on-demand based on event triggers, this way the developers can focus more on their code without worrying much about the underlying infrastructure.
OpenShift Serverless is based on the Knative project which allows the deployment of its serverless components on top of Kubernetes, which means that your code only runs when it needs to with Knative starting and stopping automatically.
What did we build in the code lab?
The goal of the lab was to demonstrate the Serverless Operator in action. We built a sample application using a CouchDB database to demonstrate the scaling up and down of applications when we make changes or deletions to the database.
In the code lab, we used Knative Serving (to run stateless serverless service) and Knative Eventing (to subscribe to event sources).
You can watch the replay of the workshop and follow along here on IBM Developer Crowdcast and view the resources in this GitHub repo.
