You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* xref:../../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#binding-a-workload-together-with-a-backing-service[Binding a workload together with a backing service].
47
+
* xref:../../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#binding-a-workload-together-with-a-backing-service_understanding-service-binding-operator[Binding a workload together with a backing service].
48
48
* xref:../../applications/connecting_applications_to_services/getting-started-with-service-binding.adoc#connecting-the-spring-petclinic-sample-application-to-the-postgresql-database-service[Connecting the Spring PetClinic sample application to the PostgreSQL database service].
49
49
* xref:../../operators/understanding/crds/crd-managing-resources-from-crds.adoc#crd-creating-custom-resources-from-file_crd-managing-resources-from-crds[Creating custom resources from a file]
50
50
* link:https://redhat-developer.github.io/service-binding-operator/userguide/binding-workloads-using-sbo/custom-path-injection.html#_workload_resource_mapping[Example schema of the ClusterWorkloadResourceMapping resource].
Application developers need access to backing services to build and connect workloads. Connecting workloads to backing services is always a challenge because each service provider suggests a different way to access their secrets and consume them in a workload. In addition, manual configuration and maintenance of this binding together of workloads and backing services make the process tedious, inefficient, and error-prone.
13
12
14
13
The {servicebinding-title} enables application developers to easily bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection.
15
14
16
-
[id="service-binding-terminology"]
17
-
== Service Binding terminology
18
-
This section summarizes the basic terms used in Service Binding.
19
-
20
-
[horizontal]
21
-
Service binding:: The representation of the action of providing information about a service to a workload. Examples include establishing the exchange of credentials between a Java application and a database that it requires.
22
-
Backing service:: Any service or software that the application consumes over the network as part of its normal operation. Examples include a database, a message broker, an application with REST endpoints, an event stream, an Application Performance Monitor (APM), or a Hardware Security Module (HSM).
23
-
Workload (application):: Any process, running within a container. Examples include a Spring Boot application, a NodeJS Express application, or a Ruby on Rails application.
24
-
Binding data:: Information about a service that you use to configure the behavior of other resources within the cluster. Examples include credentials, connection details, volume mounts, or secrets.
25
-
Binding connection:: Any connection that establishes an interaction between the connected components such as a bindable backing service and an application requiring that backing service.
26
-
27
-
28
-
[id="about-service-binding-operator"]
29
-
== About {servicebinding-title}
30
-
The {servicebinding-title} consists of a controller and an accompanying custom resource definition (CRD) for service binding. It manages the data plane for workloads and backing services. The Service Binding Controller reads the data made available by the control plane of backing services. Then, it projects this data to workloads according to the rules specified through the `ServiceBinding` resource.
31
-
32
-
As a result, the {servicebinding-title} enables workloads to use backing services or external services by automatically collecting and sharing binding data with the workloads. The process involves making the backing service bindable and binding the workload and the service together.
=== Making an Operator-managed backing service bindable
36
-
To make a service bindable, as an Operator provider you need to expose the binding data required by workloads to bind with the services provided by the Operator. You can provide the binding data either as annotations or as descriptors in the CRD of the Operator that manages the backing service.
=== Binding a workload together with a backing service
40
-
By using the {servicebinding-title}, as an application developer, you need to declare the intent of establishing a binding connection. You must create a `Service Binding` CR that references the backing service. This action triggers the {servicebinding-title} to project the exposed binding data into the workload. The {servicebinding-title} receives the declared intent and binds the workload together with the backing service.
41
-
42
-
The CRD of the {servicebinding-title} supports the following APIs:
43
-
44
-
* *Service Binding* with the `binding.operators.coreos.com` API group.
45
-
* *Service Binding (Spec API)* with the `servicebinding.io` API group.
46
-
47
-
With {servicebinding-title}, you can:
48
-
49
-
* Bind your workloads to Operator-managed backing services.
50
-
* Automate configuration of binding data.
51
-
* Provide service operators a low-touch administrative experience to provision and manage access to services.
52
-
* Enrich development lifecycle with a consistent and declarative service binding method that eliminates discrepancies in cluster environments.
53
-
54
-
[id="sbo-key-features"]
55
-
== Key features
56
-
57
-
* Exposal of binding data from services
58
-
** Based on annotations present in CRD, custom resources (CRs), or resources.
59
-
** Based on descriptors present in Operator Lifecycle Manager (OLM) descriptors.
60
-
* Workload projection
61
-
** Projection of binding data as files, with volume mounts.
62
-
** Projection of binding data as environment variables.
63
-
* Service Binding Options
64
-
** Bind backing services in a namespace that is different from the workload namespace.
65
-
** Project binding data into the specific container workloads.
66
-
** Auto-detection of the binding data from resources owned by the backing service CR.
67
-
** Compose custom binding data from the exposed binding data.
68
-
** Support for non-`PodSpec` compliant workload resources.
* xref:../../applications/connecting_applications_to_services/getting-started-with-service-binding.adoc#getting-started-with-service-binding[Getting started with service binding].
The {servicebinding-title} consists of a controller and an accompanying custom resource definition (CRD) for service binding. It manages the data plane for workloads and backing services. The Service Binding Controller reads the data made available by the control plane of backing services. Then, it projects this data to workloads according to the rules specified through the `ServiceBinding` resource.
10
+
11
+
As a result, the {servicebinding-title} enables workloads to use backing services or external services by automatically collecting and sharing binding data with the workloads. The process involves making the backing service bindable and binding the workload and the service together.
== Making an Operator-managed backing service bindable
15
+
To make a service bindable, as an Operator provider, you need to expose the binding data required by workloads to bind with the services provided by the Operator. You can provide the binding data either as annotations or as descriptors in the CRD of the Operator that manages the backing service.
== Binding a workload together with a backing service
19
+
By using the {servicebinding-title}, as an application developer, you need to declare the intent of establishing a binding connection. You must create a `ServiceBinding` CR that references the backing service. This action triggers the {servicebinding-title} to project the exposed binding data into the workload. The {servicebinding-title} receives the declared intent and binds the workload together with the backing service.
20
+
21
+
The CRD of the {servicebinding-title} supports the following APIs:
22
+
23
+
* *Service Binding* with the `binding.operators.coreos.com` API group.
24
+
25
+
* *Service Binding (Spec API)* with the `servicebinding.io` API group.
26
+
27
+
With {servicebinding-title}, you can:
28
+
29
+
* Bind your workloads to Operator-managed backing services.
30
+
* Automate configuration of binding data.
31
+
* Provide service operators with a low-touch administrative experience to provision and manage access to services.
32
+
* Enrich the development lifecycle with a consistent and declarative service binding method that eliminates discrepancies in cluster environments.
The CRD of the {servicebinding-title} supports the following APIs:
10
+
11
+
* *Service Binding* with the `binding.operators.coreos.com` API group.
12
+
* *Service Binding (Spec API)* with the `servicebinding.io` API group.
13
+
14
+
Both of these API groups have similar features, but they are not completely identical. Here is the complete list of differences between these API groups:
15
+
16
+
[cols="1,1,1,1"]
17
+
|===
18
+
| Feature | Supported by the `binding.operators.coreos.com` API group | Supported by the `servicebinding.io` API group | Notes
19
+
20
+
| Binding to provisioned services
21
+
| Yes
22
+
| Yes
23
+
| Not applicable (N/A)
24
+
25
+
| Direct secret projection
26
+
| Yes
27
+
| Yes
28
+
| Not applicable (N/A)
29
+
30
+
| Bind as files
31
+
| Yes
32
+
| Yes
33
+
a| * Default behavior for the service bindings of the `servicebinding.io` API group
34
+
* Opt-in functionality for the service bindings of the `binding.operators.coreos.com` API group
35
+
36
+
| Bind as environment variables
37
+
| Yes
38
+
| Yes
39
+
a| * Default behavior for the service bindings of the `binding.operators.coreos.com` API group.
40
+
* Opt-in functionality for the service bindings of the `servicebinding.io` API group: Environment variables are created alongside files.
| The `servicebinding.io` API group has no equivalent feature.
51
+
52
+
| Naming strategies
53
+
| Yes
54
+
| No
55
+
| There is no current mechanism within the `servicebinding.io` API group to interpret the templates that naming strategies use.
56
+
57
+
| Container path
58
+
| Yes
59
+
| Partial
60
+
| Because a service binding of the `binding.operators.coreos.com` API group can specify mapping behavior within the `ServiceBinding` resource, the `servicebinding.io` API group cannot fully support an equivalent behavior without more information about the workload.
61
+
62
+
| Container name filtering
63
+
| No
64
+
| Yes
65
+
| The `binding.operators.coreos.com` API group has no equivalent feature.
66
+
67
+
| Secret path
68
+
| Yes
69
+
| No
70
+
| The `servicebinding.io` API group has no equivalent feature.
71
+
72
+
| Alternative binding sources (for example, binding data from annotations)
73
+
| Yes
74
+
| Allowed by {servicebinding-title}
75
+
| The specification requires support for getting binding data from provisioned services and secrets. However, a strict reading of the specification suggests that support for other binding data sources is allowed. Using this fact, {servicebinding-title} can pull the binding data from various sources (for example, pulling binding data from annotations). {servicebinding-title} supports these sources on both the API groups.
This section summarizes the basic terms used in Service Binding.
10
+
11
+
[horizontal]
12
+
Service binding:: The representation of the action of providing information about a service to a workload. Examples include establishing the exchange of credentials between a Java application and a database that it requires.
13
+
Backing service:: Any service or software that the application consumes over the network as part of its normal operation. Examples include a database, a message broker, an application with REST endpoints, an event stream, an Application Performance Monitor (APM), or a Hardware Security Module (HSM).
14
+
Workload (application):: Any process running within a container. Examples include a Spring Boot application, a NodeJS Express application, or a Ruby on Rails application.
15
+
Binding data:: Information about a service that you use to configure the behavior of other resources within the cluster. Examples include credentials, connection details, volume mounts, or secrets.
16
+
Binding connection:: Any connection that establishes an interaction between the connected components, such as a bindable backing service and an application requiring that backing service.
0 commit comments