Merge pull request #58597 from gabriel-rh/SRVKE-1421-renaming-kafka-broker-2

SRVKE-1421 rename Knative Kafka

Author: gabriel-rh

_topic_maps/_topic_map.yml

@@ -3846,7 +3846,7 @@ Topics:
     File: installing-knative-serving
   - Name: Installing Knative Eventing
     File: installing-knative-eventing
-  - Name: Configuring Knative Kafka
+  - Name: Configuring Knative for Apache Kafka
     File: serverless-kafka-admin
   - Name: Configuring Serverless Functions
     File: configuring-serverless-functions
@@ -3976,7 +3976,7 @@ Topics:
       File: serverless-apiserversource
     - Name: Creating a ping source
       File: serverless-pingsource
-    - Name: Kafka source
+    - Name: Source for Apache Kafka
       File: serverless-kafka-developer-source
     - Name: Custom event sources
       File: serverless-custom-event-sources
@@ -3989,7 +3989,7 @@ Topics:
       File: serverless-event-sinks
     - Name: Creating event sinks
       File: serverless-creating-sinks
-    - Name: Kafka sink
+    - Name: Sink for Apache Kafka
       File: serverless-kafka-developer-sink
   - Name: Brokers
     Dir: brokers
@@ -4004,7 +4004,7 @@ Topics:
       File: serverless-broker-backing-channel-default
     - Name: Configuring the default broker class
       File: serverless-global-config-broker-class-default
-    - Name: Kafka broker
+    - Name: Knative broker for Apache Kafka
       File: kafka-broker
     - Name: Managing brokers
       File: serverless-using-brokers-managing-brokers
@@ -4040,7 +4040,7 @@ Topics:
       File: connecting-channels-sinks
     - Name: Default channel implementation
       File: serverless-channel-default
-    - Name: Security configuration for Knative Kafka channels
+    - Name: Security configuration for channels
       File: serverless-kafka-admin-security-channels
   - Name: Subscriptions
     Dir: subscriptions

_topic_maps/_topic_map_osd.yml

@@ -399,7 +399,7 @@ Topics:
     File: installing-knative-serving
   - Name: Installing Knative Eventing
     File: installing-knative-eventing
-  - Name: Configuring Knative Kafka
+  - Name: Configuring Knative for Apache Kafka
     File: serverless-kafka-admin
   - Name: Configuring Serverless Functions
     File: configuring-serverless-functions
@@ -529,7 +529,7 @@ Topics:
       File: serverless-apiserversource
     - Name: Creating a ping source
       File: serverless-pingsource
-    - Name: Kafka source
+    - Name: Source for Apache Kafka
       File: serverless-kafka-developer-source
     - Name: Custom event sources
       File: serverless-custom-event-sources
@@ -542,7 +542,7 @@ Topics:
       File: serverless-event-sinks
     - Name: Creating event sinks
       File: serverless-creating-sinks
-    - Name: Kafka sink
+    - Name: Sink for Apache Kafka
       File: serverless-kafka-developer-sink
   - Name: Brokers
     Dir: brokers
@@ -557,7 +557,7 @@ Topics:
       File: serverless-broker-backing-channel-default
     - Name: Configuring the default broker class
       File: serverless-global-config-broker-class-default
-    - Name: Kafka broker
+    - Name: Knative broker for Apache Kafka
       File: kafka-broker
     - Name: Managing brokers
       File: serverless-using-brokers-managing-brokers
@@ -593,7 +593,7 @@ Topics:
       File: connecting-channels-sinks
     - Name: Default channel implementation
       File: serverless-channel-default
-    - Name: Security configuration for Knative Kafka channels
+    - Name: Security configuration for channels
       File: serverless-kafka-admin-security-channels
   - Name: Subscriptions
     Dir: subscriptions

_topic_maps/_topic_map_rosa.yml

@@ -594,7 +594,7 @@ Topics:
     File: installing-knative-serving
   - Name: Installing Knative Eventing
     File: installing-knative-eventing
-  - Name: Configuring Knative Kafka
+  - Name: Configuring Knative for Apache Kafka
     File: serverless-kafka-admin
   - Name: Configuring Serverless Functions
     File: configuring-serverless-functions
@@ -724,7 +724,7 @@ Topics:
       File: serverless-apiserversource
     - Name: Creating a ping source
       File: serverless-pingsource
-    - Name: Kafka source
+    - Name: Source for Apache Kafka
       File: serverless-kafka-developer-source
     - Name: Custom event sources
       File: serverless-custom-event-sources
@@ -737,7 +737,7 @@ Topics:
       File: serverless-event-sinks
     - Name: Creating event sinks
       File: serverless-creating-sinks
-    - Name: Kafka sink
+    - Name: Sink for Apache Kafka
       File: serverless-kafka-developer-sink
   - Name: Brokers
     Dir: brokers
@@ -752,7 +752,7 @@ Topics:
       File: serverless-broker-backing-channel-default
     - Name: Configuring the default broker class
       File: serverless-global-config-broker-class-default
-    - Name: Kafka broker
+    - Name: Knative broker for Apache Kafka
       File: kafka-broker
     - Name: Managing brokers
       File: serverless-using-brokers-managing-brokers
@@ -788,7 +788,7 @@ Topics:
       File: connecting-channels-sinks
     - Name: Default channel implementation
       File: serverless-channel-default
-    - Name: Security configuration for Knative Kafka channels
+    - Name: Security configuration for channels
       File: serverless-kafka-admin-security-channels
   - Name: Subscriptions
     Dir: subscriptions

modules/serverless-channel-default.adoc

@@ -10,7 +10,7 @@
 
 * You have administrator permissions on {product-title}.
 * You have installed the {ServerlessOperatorName} and Knative Eventing on your cluster.
-* If you want to use Kafka channels as the default channel implementation, you must also install the `KnativeKafka` CR on your cluster.
+* If you want to use Knative channels for Apache Kafka as the default channel implementation, you must also install the `KnativeKafka` CR on your cluster.
 
 .Procedure
 

modules/serverless-config-replicas-kafka.adoc

@@ -4,9 +4,9 @@
 
 :_content-type: PROCEDURE
 [id="serverless-config-replicas-kafka_{context}"]
-= Configuring high availability replicas for Knative Kafka
+= Configuring high availability replicas for the Knative broker implementation for Apache Kafka
 
-High availability (HA) is available by default for the Knative Kafka `kafka-controller` and `kafka-webhook-eventing` components, which are configured to have two each replicas by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeKafka` custom resource (CR).
+High availability (HA) is available by default for the Knative broker implementation for Apache Kafka components `kafka-controller` and `kafka-webhook-eventing`, which are configured to have two each replicas by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeKafka` custom resource (CR).
 
 .Prerequisites
 
@@ -18,7 +18,7 @@ ifdef::openshift-dedicated,openshift-rosa[]
 * You have access to an {product-title} account with cluster administrator or dedicated administrator access.
 endif::[]
 
-* The {ServerlessOperatorName} and Knative Kafka are installed on your cluster.
+* The {ServerlessOperatorName} and Knative broker for Apache Kafka are installed on your cluster.
 
 .Procedure
 

modules/serverless-create-kafka-channel-yaml.adoc

@@ -5,7 +5,7 @@
 
 :_content-type: PROCEDURE
 [id="serverless-create-kafka-channel-yaml_{context}"]
-= Creating a Kafka channel by using YAML
+= Creating a channel for Apache Kafka by using YAML
 
 Creating Knative resources by using YAML files uses a declarative API, which enables you to describe channels declaratively and in a reproducible manner. You can create a Knative Eventing channel that is backed by Kafka topics by creating a Kafka channel. To create a Kafka channel by using YAML, you must create a YAML file that defines a `KafkaChannel` object, then apply it by using the `oc apply` command.
 

modules/serverless-creating-a-kafka-event-sink.adoc

@@ -4,13 +4,16 @@
 
 :_content-type: PROCEDURE
 [id="serverless-creating-a-kafka-event-sink_{context}"]
-= Creating a Kafka sink by using the {product-title} web console
+= Creating an event sink for Apache Kafka by using the {product-title} web console
 
 You can create a Kafka sink that sends events to a Kafka topic by using the *Developer* perspective in the {product-title} web console. By default, a Kafka sink uses the binary content mode, which is more efficient than the structured mode.
 
+
+As a developer, you can create an event sink to receive events from a particular source and send them to a Kafka topic. 
+
 .Prerequisites
 
-* You have installed the {ServerlessOperatorName}, with Knative Serving, Knative Eventing, and Knative Kafka APIs, from the OperatorHub.
+* You have installed the {ServerlessOperatorName}, with Knative Serving, Knative Eventing, and Knative broker for Apache Kafka APIs, from the OperatorHub.
 * You have created a Kafka topic in your Kafka environment.
 
 .Procedure

modules/serverless-creating-channel-admin-web-console.adoc

@@ -30,6 +30,6 @@ endif::[]
 +
 [NOTE]
 ====
-Currently only `InMemoryChannel` channel objects are supported by default. Kafka channels are available if you have installed Knative Kafka on {ServerlessProductName}.
+Currently only `InMemoryChannel` channel objects are supported by default. Knative channels for Apache Kafka are available if you have installed the Knative broker implementation for Apache Kafka on {ServerlessProductName}.
 ====
 . Click *Create*.

modules/serverless-creating-subscriptions-kn.adoc

@@ -25,7 +25,7 @@ $ kn subscription create <subscription_name> \
   --sink <sink_prefix>:<sink_name> \ <2>
   --sink-dead-letter <sink_prefix>:<sink_name> <3>
 ----
-<1> `--channel` specifies the source for cloud events that should be processed. You must provide the channel name. If you are not using the default `InMemoryChannel` channel that is backed by the `Channel` custom resource, you must prefix the channel name with the `<group:version:kind>` for the specified channel type. For example, this will be `messaging.knative.dev:v1beta1:KafkaChannel` for a Kafka backed channel.
+<1> `--channel` specifies the source for cloud events that should be processed. You must provide the channel name. If you are not using the default `InMemoryChannel` channel that is backed by the `Channel` custom resource, you must prefix the channel name with the `<group:version:kind>` for the specified channel type. For example, this will be `messaging.knative.dev:v1beta1:KafkaChannel` for an Apache Kafka backed channel.
 <2> `--sink` specifies the target destination to which the event should be delivered. By default, the `<sink_name>` is interpreted as a Knative service of this name, in the same namespace as the subscription. You can specify the type of the sink by using one of the following prefixes:
 `ksvc`:: A Knative service.
 `channel`:: A channel that should be used as destination. Only default channel types can be referenced here.

modules/serverless-event-delivery-component-behaviors.adoc

@@ -9,7 +9,7 @@
 Different channel and broker types have their own behavior patterns that are followed for event delivery.
 
 [id="serverless-event-delivery-component-behaviors-kafka_{context}"]
-== Knative Kafka channels and brokers
+== Knative channels and brokers for Apache Kafka
 
 If an event is successfully delivered to a Kafka channel or broker receiver, the receiver responds with a `202` status code, which means that the event has been safely stored inside a Kafka topic and is not lost.