Releases: operator-framework/operator-sdk
Releases · operator-framework/operator-sdk
v1.38.0
v1.38.0
Changes
- For Go-based, Helm-based and Ansible-based operators this release moves to Kubernetes 1.30 API's and Kubebuilder v4 Scaffolding,
specifically utilizing the v4.1.1 version. The update to Kubebuiler results in some scaffolding changes which more information can be found below:- Discontinue usage of kube-rbac-proxy in the default scaffolding of new projects. For further information,
see: Action Required: Ensure that you no longer use gcr.io/kubebuilder images - The
go/v2
orgo/v3
layouts have been removed, you must upgrade togo/v4
to be compatible with this release and future updates.
To know how to upgrade,check the migration documentation. - Re-introduces authn/authz protection for the metrics endpoint using
WithAuthenticationAndAuthorization
provided by controller-runtime instead of kube-rbac-proxy; which usage was discontinued in the project. Please, ensure that you no longer use the imagegcr.io/kubebuilder/kube-rbac-proxy
. Images provided undergcr.io/kubebuilder/
will be unavailable from March 18, 2025. To learn more about any of the metrics changes please look at the Kubebuilder book metrics page. ForHelm-based
andAnsible-based
operators, a new flag calledmetrics-require-rbac
was introduced into the runtime/binary, to control addingWithAuthenticationAndAuthorization
toMetrics.FilterProvider
of controller-runtime. This was done to ensure forwards and backwards compatibility of the binary and images with any scaffolded content. (#6862)
- Discontinue usage of kube-rbac-proxy in the default scaffolding of new projects. For further information,
Bug Fixes
- An additional condition is included for matching
apiVersion
of example CRs with CRDversion
when searching for the CRD in the CSV. Previously, Theolm-spec-descriptors
scorecard test failed when multiple versions of CRD is included in the CSV. The CR specified inalm-examples
annotations are validated only against the first matched CRD (by name), which is incorrect. This ensures the correct CRD version is selected for validations. (#6784) - Fix naive YAML split in
run bundle
command. (#6829)
v1.37.0
v1.36.1
v1.36.1
No changes for this release!
v1.36.0
v1.35.0
v1.34.2
v1.34.2
No changes for this release!
v1.34.1
v1.34.0
v1.34.0
🚨 WARNING: This release is broken. Please upgrade to 1.34.1 to resolve any issues. 🚨
Changes
- Bump supported Kubernetes version to 1.28. (#6554)
- Bump go to 1.21 (#6685)
- Updated the supported OLM versions to 0.25.0, 0.26.0, and 0.27.0 (#6688)
Bug Fixes
make install
: fix a bug where the command would silently fail if GOBIN wasn't set. (#6629)
v1.33.0
v1.33.0
Changes
- Bump supported Kubernetes version to 1.27. (#6613)
- Breaking change: (go/v4-alpha): go/v4 is now stable and is the default version used when scaffolding a Go based operator. (#6613)
- Breaking change: (kustomize/v2-alpha): kustomize/v2 is now stable and is the default version used in the plugin chain when using go/v4, ansible/v1, helm/v1, and hybrid/v1-alpha plugins. (#6613)
- Updated the supported OLM versions to 0.24.0, 0.25.0, and 0.26.0. (#6613)
Deprecations
- (helm/v1): Deprecate the
--config
flag due to the controller-runtime ComponentConfig package being deprecated with the planned removal of support for loading manager options from a file. (#6613)
Bug Fixes
operator-sdk olm install
: fix a bug where the retry logic would not retry until the the command's timeout was reached, resulting in early exiting of the command before the specified timeout was reached. (#6613)
v1.32.0
v1.32.0
Additions
- For Helm-based operators, whenever the operator encounters an error during reconcilliation, it would attempt to rollback the changes with the
--force
option. This behavior could have undesired side effects in some scenario.
This change allows the users to change this behavior by adding the annotation,helm.sdk.operatorframework.io/rollback-force: false
to the custom resource. (#6546)