redhat-developer/service-binding-operator v0.11.0

on GitHub

Breaking Changes

• #1035 - Remove 'mountPath' support (@sadlerap)
  Use .spec.name if you need to control the name of the folder where bindings are projected (#1037)
• #1027 - Support servicebinding.io/v1alpha3 API (@pedjak)
  Specification apiVersion got update recently to servicebinding.io/v1alpha3. If you were using previous service.binding/v1alpha2, you need to update service binding instances accordingly.

Improvements

• #1037 - Add optional .spec.name to ServiceBinding to binding.operators.coreos.com/v1alpha1 API (@pedjak)
• #1036 - Detect bindable kinds and expose them for client discovery (@pedjak)
• #1021 - Remove unused .status.applications field (@pedjak)

Bugfixes

• #1032 - handle panics occurring in reconsile pipeline gracefuly (@pedjak)
• #1031 - Do not bind if there is no binding item collected from the service (@pmacik)
• #1029 - Remove duplicate setting of SERVICE_BINDING_ROOT env while projecting files (@pmacik)
• #1028 - Allow binding to OpenShift deployment configs out of the box (@pedjak)
• #1023 - Treat invalid "elementType" and "objectType" annotations as errors, not panics (@sadlerap)

Testing

• #1033 - [acceptance-tests] Use patch instead of apply for IDP setup to avoid braking cluster's IDPs (@pmacik)

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.1.0/cert-manager.yaml

after that install the operator:

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

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