447a51f08b
* feat: kubesphere 4.0 Signed-off-by: ci-bot <ci-bot@kubesphere.io> * feat: kubesphere 4.0 Signed-off-by: ci-bot <ci-bot@kubesphere.io> --------- Signed-off-by: ci-bot <ci-bot@kubesphere.io> Co-authored-by: ks-ci-bot <ks-ci-bot@example.com> Co-authored-by: joyceliu <joyceliu@yunify.com>
1.2 KiB
Versioning and Branching in controller-runtime
We follow the common KubeBuilder versioning guidelines, and use the corresponding tooling.
For the purposes of the aforementioned guidelines, controller-runtime counts as a "library project", but otherwise follows the guidelines exactly.
Compatibility and Release Support
For release branches, we generally tend to support backporting one (1)
major release (release-{X-1} or release-0.{Y-1}), but may go back
further if the need arises and is very pressing (e.g. security updates).
Dependency Support
Note the guidelines on dependency versions. Particularly:
-
We DO guarantee Kubernetes REST API compatibility -- if a given version of controller-runtime stops working with what should be a supported version of Kubernetes, this is almost certainly a bug.
-
We DO NOT guarantee any particular compatibility matrix between kubernetes library dependencies (client-go, apimachinery, etc); Such compatibility is infeasible due to the way those libraries are versioned.