Chapter 8: Preparing for Ongoing Maintenance of Your Operator
In this book, we have shown the steps for creating a new Kubernetes Operator. We've covered the full range of processes from conception to design, to coding, deployment, and finally, release. But, very few software projects end their life cycle after the initial release, Operators included. In fact, for many Operators, the majority of work will eventually be done after release on a long enough timescale. So, it's valuable to prepare for the future maintenance of your Operator by understanding the expectations of your users and the Operator community at large.
As a Kubernetes-based project, it can be very helpful to rely on the established conventions from Kubernetes and its subprojects for your own ongoing development. While you are free to form your own guidelines for future releases, it is likely that your Operator will depend on at least some library or aspect of the core Kubernetes platform simply by virtue...