Complying with Kubernetes standards for changes
Kubernetes defines a standard set of policies for deprecation (and other breaking changes) that all core projects must abide by. This policy is available at https://kubernetes.io/docs/reference/using-api/deprecation-policy/. It's not necessary to read and understand the whole policy for the purposes of Operator development, as we will highlight some of the relevant bits here. It primarily defines the standards for deprecating parts of the Kubernetes API, with many of the same (or similar) guidelines being applied to other types of deprecation as well (such as user-facing features that are not directly part of the API). It does this by enumerating a list of explicit rules for deprecating changes, some of which we will cover in this section.
As a third-party component, your Operator is under no obligation to follow the Kubernetes deprecation policy. But, in a practical sense, there are benefits to working within the constraints...
