Skip to content

Commit cb86252

Browse files
JSticklerJStickler
authored
Merge pull request #46008 from Srivaralakshmi/SBO_RN_1.1
RHDEVDOCS-3777- Release Notes, New Features, and Known Issues for SBO 1.1
2 parents 87e381f + 4e7d052 commit cb86252

File tree

2 files changed

+105
-1
lines changed

2 files changed

+105
-1
lines changed

‎applications/connecting_applications_to_services/sbo-release-notes.adoc

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,16 +17,54 @@ With {servicebinding-title}, you can:
1717
* Provide service operators a low-touch administrative experience to provision and manage access to services.
1818
* Enrich development lifecycle with a consistent and declarative service binding method that eliminates discrepancies in cluster environments.
1919
20+
The custom resource definition (CRD) of the {servicebinding-title} supports the following APIs:
21+
22+
* *Service Binding* with the `binding.operators.coreos.com` API group.
23+
* *Service Binding (Spec API Tech Preview)* with the `servicebinding.io` API group.
24+
+
25+
[IMPORTANT]
26+
====
27+
*Service Binding (Spec API Tech Preview)* with the `servicebinding.io` API group is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
28+
29+
For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
30+
====
31+
32+
[id="support-matrix"]
33+
== Support matrix
34+
35+
Some features in this release are currently in link:https://access.redhat.com/support/offerings/techpreview[Technology Preview]. These experimental features are not intended for production use.
36+
37+
In the table, features are marked with the following statuses:
38+
39+
- *TP*: _Technology Preview_
40+
41+
- *GA*: _General Availability_
42+
43+
Note the following scope of support on the Red Hat Customer Portal for these features:
44+
45+
.Support matrix
46+
[options="header"]
47+
|===
48+
|*{servicebinding-title}* 2+|*API Group and Support Status*|*OpenShift Versions*
49+
50+
|*Version*|*`binding.operators.coreos.com`* |*`servicebinding.io`* |
51+
|1.1 |GA |TP |4.7-4.10
52+
|1.0.1 |GA |TP |4.7-4.9
53+
|1.0 |GA |TP |4.7-4.9
54+
55+
|===
2056

2157
[id="servicebinding-inclusive-language"]
2258
== Making open source more inclusive
2359

2460
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright's message].
2561

2662
// Modules included, most to least recent
63+
include::modules/sbo-release-notes-1-1.adoc[leveloffset=+1]
2764
include::modules/sbo-release-notes-1-0-1.adoc[leveloffset=+1]
2865
include::modules/sbo-release-notes-1-0.adoc[leveloffset=+1]
2966

30-
67+
[role="_additional-resources"]
68+
[id="additional-resources_release-notes-sbo"]
3169
== Additional resources
3270
* xref:../../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#understanding-service-binding-operator[Understanding Service Binding Operator].

‎modules/sbo-release-notes-1-1.adoc

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
[id="sbo-release-notes-1-1_{context}"]
2+
// Module included in the following assembly:
3+
//
4+
// * applications/connecting_applications_to_services/sbo-release-notes.adoc
5+
:_content-type: REFERENCE
6+
= Release notes for {servicebinding-title} 1.1
7+
8+
{servicebinding-title} is now available on {product-title} 4.7, 4.8, 4.9, and 4.10.
9+
10+
[id="new-features-1-1_{context}"]
11+
== New features
12+
This section highlights what is new in {servicebinding-title} 1.1:
13+
14+
* Service Binding Options
15+
** Workload resource mapping: Define exactly where binding data needs to be projected for the secondary workloads.
16+
** Bind new workloads using a label selector.
17+
18+
19+
[id="fixed-issues-1-1_{context}"]
20+
== Fixed issues
21+
* Before this update, service bindings that used label selectors to pick up workloads did not project service binding data into the new workloads that matched the given label selectors. As a result, the Service Binding Operator could not periodically bind such new workloads. With this update, service bindings now project service binding data into the new workloads that match the given label selector. The Service Binding Operator now periodically attempts to find and bind such new workloads. link:https://issues.redhat.com/browse/APPSVC-1083[APPSVC-1083]
22+
23+
24+
[id="known-issues-1-1_{context}"]
25+
== Known issues
26+
* There is currently a known issue with installing {servicebinding-title} in a 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 {servicebinding-title} can automatically detect and bind to. When this happens, it generates an error message similar to the following example:
27+
+
28+
.Example error message
29+
[source,text]
30+
----
31+
`postgresclusters.postgres-operator.crunchydata.com "hippo" is forbidden:
32+
User "system:serviceaccount:my-petclinic:service-binding-operator" cannot
33+
get resource "postgresclusters" in API group "postgres-operator.crunchydata.com"
34+
in the namespace "my-petclinic"`
35+
----
36+
+
37+
Workaround 1: Install the {servicebinding-title} in the `all namespaces` installation mode. As a result, the appropriate cluster-scoped RBAC rule now exists and the binding succeeds.
38+
+
39+
Workaround 2: If you cannot install the {servicebinding-title} in the `all namespaces` installation mode, install the following role binding into the namespace where the {servicebinding-title} is installed:
40+
+
41+
.Example: Role binding for Crunchy Postgres Operator
42+
[source,yaml]
43+
----
44+
kind: RoleBinding
45+
apiVersion: rbac.authorization.k8s.io/v1
46+
metadata:
47+
name: service-binding-crunchy-postgres-viewer
48+
subjects:
49+
- kind: ServiceAccount
50+
name: service-binding-operator
51+
roleRef:
52+
apiGroup: rbac.authorization.k8s.io
53+
kind: ClusterRole
54+
name: service-binding-crunchy-postgres-viewer-role
55+
----
56+
link:https://issues.redhat.com/browse/APPSVC-1062[APPSVC-1062]
57+
58+
* Currently, when you modify the `ClusterWorkloadResourceMapping` resources, the {servicebinding-title} does not implement correct behavior. As a workaround, perform the following steps:
59+
+
60+
--
61+
. Delete any `ServiceBinding` resources that use the corresponding `ClusterWorkloadResourceMapping` resource.
62+
. Modify the `ClusterWorkloadResourceMapping` resource.
63+
. Re-apply the `ServiceBinding` resources that you previously removed in step 1.
64+
--
65+
+
66+
link:https://issues.redhat.com/browse/APPSVC-1102[APPSVC-1102]

0 commit comments

Comments
 (0)