Release notes for service Binding Operator

TP: Technology Preview

GA: General Availability

Before this update, binding the data values from a Cluster custom resource (CR) of the postgresql.k8s.enterpriesedb.io/v1 API collected the host binding value from the .metadata.name field of the CR. The collected binding value is an incorrect hostname and the correct hostname is available at the .status.writeservice field. With this update, the annotations that the service Binding Operator uses to expose the binding data values from the backing service CR are now modified to collect the host binding value from the .status.writeservice field. The service Binding Operator uses these modified annotations to project the correct hostname in the host and provider bindings. APPSVC-1040

Before this update, when you would bind a PostgresCluster CR of the postgres-operator.crunchydata.com/v1beta1 API, the binding data values did not include the values for the database certificates. As a result, the application failed to connect to the database. With this update, modifications to the annotations that the service Binding Operator uses to expose the binding data from the backing service CR now include the database certificates. The service Binding Operator uses these modified annotations to project the correct ca.crt, tls.crt, and tls.key certificate files. APPSVC-1045

Before this update, when you would bind a PerconaXtraDBCluster custom resource (CR) of the pxc.percona.com API, the binding data values did not include the port and database values. These binding values along with the others already projected are necessary for an application to successfully connect to the database service. With this update, the annotations that the service Binding Operator uses to expose the binding data values from the backing service CR are now modified to project the additional port and database binding values. The service Binding Operator uses these modified annotations to project the complete set of binding values that the application can use to successfully connect to the database service. APPSVC-1073

Currently, when you install the service Binding Operator in the single namespace installation mode, the absence of an appropriate namespace-scoped role-based access control (RBAC) rule prevents the successful binding of an application to a few known Operator-backed services that the service Binding Operator can automatically detect and bind to. In addition, the following error message is generated:

`postgresclusters.postgres-operator.crunchydata.com "hippo" is forbidden:
        User "system:serviceaccount:my-petclinic:service-binding-operator" cannot
        get resource "postgresclusters" in API group "postgres-operator.crunchydata.com"
        in the namespace "my-petclinic"`

kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: service-binding-crunchy-postgres-viewer
subjects:
  - kind: serviceAccount
    name: service-binding-operator
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: service-binding-crunchy-postgres-viewer-role

TP: Technology Preview

GA: General Availability

IBM Power Systems

IBM Z and LinuxONE

Exposal of binding data from services

Workload projection

service Binding Options

Security