v1.1.1

What's Changed

• Change operator image baseimage to Red Hat's minimal UBI 8 by @pmacik in #1166
• Chart updated for version 1.1.0 by @Kartikey-star in #1169
• Bumped version for golang.org/x/text in order to fix CVE-2021-38561 security vulnerability by @Kartikey-star in #1170
• Add GH action for security scan. by @pmacik in #1171
• Print subject access review error to logs. by @pmacik in #1174
• Add missing cluster role and binding for reading ClusterWorkloadResourceMapping for any authenticated subject by @pmacik in #1175
• Bump version to v1.1.1 by @pmacik in #1173

Full Changelog: v1.1.0...v1.1.1

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

after that install the operator:

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

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

v1.1.0

What's Changed

• Re-enable Cloud Native Postgres operator scenario for openshift 4.10 and switch catalog source to Operatorhub.io by @pmacik in #1119
• Tag acceptance testing scenarios that are a result of external users' feedback by @pmacik in #1112
• Disable scenarios for architectures other then amd64 by @pmacik in #1109
• Add check to verfiy that PR has not more than a single commit by @pmacik in #1120
• Remove the last usage of obsolete package by @baijum in #1102
• Add instruction to run tests by @baijum in #1121
• Fix CI by @sadlerap in #1127
• Update additional resources:Added Service Binding Operator Blog and Drag&Drop JAR and Service Binding by @Kartikey-star in #1128
• Upgrade codecov-action from deprecated v1 to v3 by @pmacik in #1129
• Workload resource mapping by @sadlerap in #1086
• Upgrade codecov-action from deprecated v1 to v3 for merge-to-master by @pmacik in #1133
• Pin Crunchy PostgreSQL Operator version to v5.0.5 for acceptance tests with Minikube by @pmacik in #1134
• Create non-admin user for acceptance tests for OpenShift only if it does not exist by @pmacik in #1131
• Fix 'Service Binding is ready' step assertions by @pmacik in #1136
• Add sample application for binding with Elasticsearch by @pmacik in #1126
• Updating the readme file with the link to the latest blog on SBO by @fbm3307 in #1137
• Add missing manifest and make targets for MySQL Cluster Sample by @growi in #1125
• Add performance testing framework by @pmacik in #1138
• bind labeled workloads created after sb reconcile by @sadlerap in #1130
• Install pre-built latest version of sandbox for the performance test. by @pmacik in #1143
• docs: publish different version of the docs by @HarshCasper in #1144
• Service Binding Operator Helm chart by @Kartikey-star in #1132
• Enable site generation using GitHub sources to enable multi-version docs in gh-pages by @pmacik in #1145
• Fix catalog source name and resource counts for performance test by @pmacik in #1147
• Added docs for chart readme and installation guide as per review by @Kartikey-star in #1146
• Re-organize Makefile into smaller managable pieces by @pmacik in #1148
• Updates to upstream to sync with downstream content by @Srivaralakshmi in #1142
• Skip running acceptance tests in GH workflows for PR that does not change SBO nor the testing framework by @pmacik in #1150
• Update CI docs. by @pmacik in #1152
• Add SBO icon to chart metadata by @Kartikey-star in #1154
• Add support for servicebinding.io API for performance testing by @pmacik in #1153
• Switch release versions of docs to vX.Y.Z-docs branches by @pmacik in #1156
• docs: remove duplicate documentation directory by @sadlerap in #1159
• Fix generated filenames for controller role and rolebinding to follow naming convention in bundle by @pmacik in #1158
• Add/Remove acceptance-tests-skipped label for PRs by @pmacik in #1155
• docs: fixups for label selection by @sadlerap in #1149
• owners: add @shruthihub as approver & reviewer by @sadlerap in #1160
• Bump version to v1.1.0 by @shruthihub in #1162
• Add description and displayName to ClusterWorkloadResourceMapping in CSV by @pmacik in #1163
• docs: document workload resource mapping by @sadlerap in #1139
• webhooks: validate workload resource mapping resources by @sadlerap in #1164
• docs: use workload terminology for spec API by @sadlerap in #1165

New Contributors

• @fbm3307 made their first contribution in #1137
• @growi made their first contribution in #1125
• @HarshCasper made their first contribution in #1144
• @Srivaralakshmi made their first contribution in #1142
• @shruthihub made their first contribution in #1162

Full Changelog: v1.0.1...v1.1.0

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

after that install the operator:

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

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

v1.0.1

Bug-fix release of Service Binding Operator

Fixed bugs

• Fix Percona XtraDB Cluster (mysql) annotations by @pmacik in #1105
• Fix Percona XtraDB Cluster (mysql) annotations for k8s and test actual connection by @pmacik in #1106
• Project certificates together with other Crunchy Postgres bindings by @pedjak in #1084
• Fixed exposed host binding item for databases provisioned by Cloud Native Postgres Operator by @pedjak in #1081
• Make sure to return nil value when there was an error by @kadel in #1079

What's Changed

• Update Readme with spec alignment by @jasperchui in #1064
• Include operator package in existing subscription detection in install.sh by @pmacik in #1066
• [acceptance-tests] Fix oc version compare in before_all hook by @pmacik in #1067
• Add links to relevant articles/blog posts by @sadlerap in #1068
• Add architecture document by @pedjak in #1069
• test(acceptance): remove obsolete scenario by @pmacik in #1070
• test(acceptance): add annotations with nested attributes into scenario for CRD annotations by @pmacik in #1072
• Use mutil-arch generic test app image by @yselkowitz in #1075
• Use $scenario_id in acceptance tests when possible by @sadlerap in #1074
• build: add recipe for generating mocks by @sadlerap in #1076
• Introduce sample application (spring-petclinic + postgresql) to be used in quickstart by @pmacik in #1080
• Upgrade cert manager from v1.1.0 to v1.6.0 by @sadlerap in #1089
• Temporarily disable Cloud Native Postgres operator scenario for openshift 4.10 by @pmacik in #1090
• Update contribution guide and pull request template by @pedjak in #1091
• Update obsoleted release instructions by @pedjak in #1092
• Avoid expression evaluation in the script by @baijum in #1093
• Use certified-operators catalog source for Crunchy Postgres Operator in acceptance tests by @pmacik in #1096
• Update to OperatorSDK 1.16 by @pedjak in #1094
• Set channels to 'stable' for Operatorhub.io PR metadata by @pmacik in #1095
• Refactor getting started guide to use the sample spring-petclinic by @pmacik in #1085
• Fix operator-sdk version in merge-to-master GH action by @pmacik in #1099
• Switch log format back to JSON by @pmacik in #1101
• Remove unused CRDs and mock objects by @baijum in #1100
• Include pod logs while collecting kube resources in GitHub actions by @pmacik in #1108
• Bump version to v1.0.1 by @sadlerap in #1104
• Added Spring Petclinic Application Deployment yaml compatible with MySQL and custom resource yaml for creating instance of PerconaXtraDB cluster by @Kartikey-star in #1107

New Contributors

• @kadel made their first contribution in #1079
• @Kartikey-star made their first contribution in #1107

Full Changelog: v1.0.0...v1.0.1

Installing

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

after that install the operator:

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

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

v1.0.0

This release delivers fully reworked user guide documentation available at the new web-site and adds support for binding services provisioned by the following operators:

• OpsTree Redis
• CrunchyData Postgres
• Cloud Native
  PostgreSQL
• Percona XtraDB
  Cluster
• Percona
  MongoDB
• RabbitMQ Cluster

Improvements

• #1053 - Add Ready/Reason print columns (@pedjak)
• #1048 - Add support for Percona Mysql operator backed-services (@pedjak)
• #1005 - A name and selector MUST NOT be defined together (@baijum)
• #1050 - registry: add support for percona mongodb clusters (@sadlerap)
• #1043 - Add support for CrunchyData Postgres operator (@pedjak)
• #1040 - Add support for Opstree Redis operator-backed services (@pedjak)
• #1045 - Support Cloud Native PostgreSQL operator (@baijum)
• #1051 - add support for RabbitMQ operator backed-services (@pedjak)

Documentation Changes

• #1062 - Fix misformatted paragraph in user guide's intro (@sadlerap)
• #1061 - Improve asciidoc styling (@pedjak)
• #1060 - Fix doc Edit Page urls (@pedjak)
• #1059 - Update documentation on exposing binding data with annotations (@pedjak)
• #1058 - Document registry in README.md (@sadlerap)
• #1057 - Remove BindableKinds CR from samples (@pmacik)
• #1056 - Document RBAC requirements (@baijum)
• #1055 - [docs] Fix cross-reference links/anchors (@pmacik)
• #1054 - add publish-website GitHub job (@pedjak)
• #1052 - Move annotation registry into dedicated package (@pedjak)
• #1049 - Improve CSV description (@pedjak)
• #1047 - Update google meet link (@baijum)
• #1044 - Remove references to removed examples (@pmacik)
• #1039 - fix compile error when using SBO as library with newer controller-runtime (@pedjak)
• #1038 - Fix CSV manifests to reflect v1alpha3 version of spec API and recent addition of BindableKinds CRD (@pmacik)
• #1034 - Remove obsolete examples in favour of SBO docs (@pmacik)
• #1019 - Service Binding Operator documentation (@baijum)

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/v1.0.0/release.yaml

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

v0.11.0

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.

v0.10.0

This release delivers two security-related improvements that might break user experience. in certain environments.

• Service account used by the operator pod requires a way less permissions than before. Prior to this change, the service account
  had all rights to all APIs, even those deployed by 3rd-party operators. With the work in #1002, the service account rights are reduced significantly, so that the operator gets installed with the following permissions:
  • read/modify for deployments, deamonsets, replicasets, and statefulsets
  • read for pods, confgimaps, endpoints, services, crds, and csvs
  • read/modify/create for secrets and servicebindings

In order to enable the operator to perform binding to custom service resource, an additional cluster role must be added to the cluster. For example, if an operator manages backends.foo.com resources, then the following cluster role enables the operator to access them and read the available bindings:

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: backends-view
  labels:
    service.binding/controller: "true"
rules:
  - apiGroups:
      - foo.com
    resources:
      - backends
    verbs:
      - get
      - list

service.binding/controller: "true" label is mandatory, so that the aggregated cluster role associated to the service account can pick it up.

• The operator now checks if service binding submitter has rights to read service and modify application resource. Without having the proper rights, binding requests are going to fail. Prior to merging #784, malicious users could create service bindings against services they do not have rights to talk to, and get access to them. Also they could injecting malicious services into applications.

In order to allow a user to perform service bindings, cluster role bindings or role bindings needs to be associated to that user, allowing:

• reading service resources
• modifying application resource

Improvements

• #1002 - Adjusted access for resources and apiversions (@bamachrn)
• #784 - Bind only if user submitting request can read services and update application resource (@pedjak)
• #1020 - Apply CSV best practices (@pedjak)
• #1018 - Set default operator channel to 'candidate' (@pedjak)
• #1012 - Fix markdown format in User_Guide.md (@dgolovin)
• #1009 - Set display name for spec CRD (@baijum)
• #1008 - Improve documentation used by 'kubectl explain' (@sadlerap)
• #999 - Add v1alpha2 CRD meta-data into CSV (@pmacik)

Bugfixes

• #1015 - Fix crash when annotation's sourceValue is invalid (@sadlerap)

Testing/CI

• #1010 - [acceptance-tests] Update CRD api version to v1 to support OpenShift v4.9 (@pmacik)
• #1011 - Include cluster-wide resources to be collected by GH Actions. (@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.10.0/release.yaml

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

v0.9.1

Bugfixes

• #997 - Allow metadata updates on Ready bindings (@pedjak)

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.9.1/release.yaml

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

v0.9.0

This release introduces the support for Service Binding Specification. The new API is added along the existing API, to enable easy migration.

Improvements

• #985 - add support for Spec API (@pedjak)
• #984 - Add support for Direct Secret reference (@baijum)
• #977 - Drop support for empty application binding (@baijum)
• #964 - Support for selection of array element in paths (@feloy)
• #913 - Successful Service Binding Resource should be Immutable (@Avni-Sharma)

Testing/CI

• #989 - Include missed directories for python linters (@pmacik)
• #986 - Upgrade CI minikube/olm versions (@pedjak)
• #980 - [acceptance-tests] Collect kube resources as well as SBO logs in GH workflows (@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.9.0/release.yaml

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

v0.8.0

Improvements

• #978 - Add provisioned service support (@pedjak)

Bugfixes

• #975 - Fix Service.OwnedResources() to return correct result (@pedjak)
• #971 - Fix support for label selectors (@baijum)
• #959 - Check if unready binding can be removed (@pedjak)
• #955 - Regression fix: refer multiple services in custom mapping templates (@pedjak)

Testing/CI

• #976 - Optimize acceptance testing jobs on OpenShift CI (@pmacik)
• #973 - Fix SBO base image conflict with local registry in GH Actions (@pmacik)
• #972 - Add GHA workflow to push operator images for PRs (@pmacik)
• #957 - [acceptance-tests] Add checks for removal of intermediate secret when SB is removed (@pmacik)

Check OperatorHub page for installation instructions. Alternatively, you can install the operator by applying the published release.yaml file:

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

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

v0.7.1

Bugfix release.

Changes

• #950 - Fix: Remove volume and volumemount from app resource when unbinding (@pedjak)
• #949 - regression fix: when binding as files use 'none' naming strategy by default (@pedjak)
• #943 - Introduce SBO logo (@pmacik)
• #941 - Change the support provider to SBO Community (@baijum)
• #912 - Add check for the presence of conflict into linters (@pmacik)
• #902 - Add bug report template (@DhritiShikhar)
• #871 - [acceptance-tests] Update acceptance testing docs. (@pmacik)

Check OperatorHub page for installation instructions. Alternatively, you can install the operator by applying the published release.yaml file:

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

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