Summary

This chapter concluded the primary development and publication of an Operator. If you have been following along up until this point while developing your own Operator, then congratulations! Your Operator is now published and accessible to new users thanks to the reach of OperatorHub. Starting from the early chapters of this book, we have shown the steps to design an Operator, develop its basic and advanced functionality with Go, build and deploy it for local testing, and finally, package and publish it for public distribution. However, very few Operator project life cycles will end at this point.

It is likely that most Operators will eventually need to evolve, change their provided features, and release new versions. Doing so in a consistent and predictable way benefits both your users and your maintainers by establishing expected release standards. These standards include policies for deprecation and timelines for new releases. In the next chapter, we will explain some...