Releasing new versions of your Operator
Now that your Operator is published, the fun has just begun. It's now time to start thinking about your next release! As with any software project, your Operator will evolve over time by introducing new features and adapting to changes in upstream Kubernetes. There are tomes of literature written on releasing software with recommendations on when and how to publish updates to a software product. Much of that information is out of the scope of this book. Instead, we will explain the technical steps required to create and publish a new version of your Operator with the Operator SDK, Operator Lifecycle Manager (OLM), and OperatorHub in mind. From there, methods and timing for your release are entirely up to your organization (though you may want to learn more about how other Kubernetes projects are released later in this chapter in the Aligning with the Kubernetes release timeline section).
Adding an API version to your Operator
While...