Summary

This chapter's main objective was to compile the Operator code that we have been building throughout this book and deploy it in a cluster. To do this, we followed steps designed for local development environments. These included building the Operator as a local binary and building a container image to deploy in an ephemeral test cluster (created using kind). This lightweight process is helpful for development and rapid testing, but it lacks the full workflow benefits needed for publishing an Operator with the intent of deploying in production.

In the next chapter, we will explore the final pillars of the Operator Framework: OperatorHub and the Operator Lifecycle Manager. Learning how to prepare and submit an Operator to OperatorHub will be a key part of offering any Operator available for public use. With that, the Operator Lifecycle Manager is a much more elegant solution for deploying Operators (both publicly available on OperatorHub or privately deployed). Compared...