Merge pull request #50036 from Srivaralakshmi/SBO-v1beta1-downstream

Update references to servicebinding.io/v1alpha3 with servicebinding.io/v1beta1

Author: rolfedh

applications/connecting_applications_to_services/understanding-service-binding-operator.adoc

@@ -31,26 +31,18 @@ The {servicebinding-title} consists of a controller and an accompanying custom r
 
 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.
 
-
 [id="making-an-operator-managed-backing-service-bindable"]
 === Making an Operator-managed backing service bindable
 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.
 
-
 [id="binding-a-workload-together-with-a-backing-service"]
 === Binding a workload together with a backing service
 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.
 
 The CRD of the {servicebinding-title} supports the following APIs:
 
 * *Service Binding* with the `binding.operators.coreos.com` API group.
-* *Service Binding (Spec API Tech Preview)* with the `servicebinding.io` API group.
-+
-[IMPORTANT]
-====
-*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.
-For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
-====
+* *Service Binding (Spec API)* with the `servicebinding.io` API group.
 
 With {servicebinding-title}, you can:
 
@@ -59,7 +51,6 @@ With {servicebinding-title}, you can:
 * Provide service operators a low-touch administrative experience to provision and manage access to services.
 * Enrich development lifecycle with a consistent and declarative service binding method that eliminates discrepancies in cluster environments.
 
-
 [id="sbo-key-features"]
 == Key features
 
@@ -78,6 +69,5 @@ With {servicebinding-title}, you can:
 * Security
 ** Support for role-based access control (RBAC).
 
-
 == Additional resources
 * xref:../../applications/connecting_applications_to_services/getting-started-with-service-binding.adoc#getting-started-with-service-binding[Getting started with service binding].

modules/sbo-advanced-binding-options.adoc

@@ -155,7 +155,7 @@ spec:
 .Example `ServiceBinding` CR in the `servicebinding.io` API
 [source,yaml]
 ----
-apiVersion: servicebindings.io/v1alpha3
+apiVersion: servicebindings.io/v1beta1
 kind: ServiceBinding
 metadata:
   name: multi-application-binding

modules/sbo-binding-workloads-that-are-not-compliant-with-PodSpec.adoc

@@ -177,7 +177,7 @@ The following example shows how to define a mapping for the `CronJob.batch/v1` r
 .Example: Mapping for `CronJob.batch/v1` resources
 [source,yaml]
 ----
-apiVersion: servicebinding.io/v1alpha3
+apiVersion: servicebinding.io/v1beta1
 kind: ClusterWorkloadResourceMapping
 metadata:
  name: cronjobs.batch <1>

modules/sbo-methods-of-exposing-binding-data.adoc

@@ -83,16 +83,10 @@ spec:
     resource: deployments
 ----
 
-[IMPORTANT]
-====
-*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.
-For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
-====
-
 .Example: `ServiceBinding` resource in Specification API
 [source,yaml]
 ----
-apiVersion: servicebinding.io/v1alpha3
+apiVersion: servicebinding.io/v1beta1
 kind: ServiceBinding
 metadata:
   name: account-service
@@ -133,7 +127,7 @@ spec:
 .Example: Specification that is compliant with the `servicebinding.io` API
 [source,yaml]
 ----
-apiVersion: servicebinding.io/v1alpha3
+apiVersion: servicebinding.io/v1beta1
 kind: ServiceBinding
 metadata:
   name: account-service