Future trends in the Operator Framework
This section refers to the future maintenance of your own Operator, as well as the alignment with ongoing work in the upstream Kubernetes community and how that relates to third-party Operator development. These topics are from Chapter 8, Preparing for Ongoing Maintenance of Your Operator.
How do you release a new version of an Operator?
Releasing a new version of an Operator is mostly dependent on your organization's release methods regarding timing and delivery infrastructure. But, the Operator Framework provides ways to denote your Operator's version in the form of the version field in the Operator's CSV (which is shown on OperatorHub), new API versions, and release channels.
When is it appropriate to add a new API version?
The most common time to add a new API version is when you are introducing a breaking change to the existing API. It can also be appropriate to increase the API's version as an indicator of...