V1.3.3

What's Changed

• cherry-pick(release-v1.3.x): bump version to v1.3.2 for helm chart by @service-binding-operator-bot in #1322
• cherry-pick(release-v1.3.x): Add displayName and description to older versions of owned CRDs in CSV by @service-binding-operator-bot in #1324
• cherry-pick(release-v1.3.x): Update Crunchy Postgres Operator to v5.3.0 in acceptance tests by @service-binding-operator-bot in #1333
• cherry-pick(release-v1.3.x): Test upgrade SBO with OLM by @pmacik in #1359
• cherry-pick(release-v1.3.x): Remove v1beta1 CRD by @pmacik in #1358
• cherry-pick(release-v1.3.x): Detect bindable resource based on status attribute by @pmacik in #1357
• cherry-pick(release-v1.3.x): Bump version to v1.3.3 by @service-binding-operator-bot in #1362

Full Changelog: v1.3.2...v1.3.3

Installing Service Binding Operator

Check OperatorHub page for installation instructions.

Alternatively, you can install the operator by applying the published release.yaml file. If not installed through OLM, the operator requires that cert-manager is available on the cluster. It can be installed by:

kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.9.1/cert-manager.yaml

after that install the operator:

kubectl apply -f https://github.com/redhat-developer/service-binding-operator/releases/download/v1.3.3/release.yaml

The operator will be deployed in service-binding-operator namespace.