docs(bridge): updates the deployment instructions for Kafka Bridge (#11382)

Signed-off-by: prmellor <pmellor@redhat.com>

Author: PaulRMellor

documentation/modules/configuring/con-config-kafka-bridge.adoc

@@ -116,8 +116,9 @@ spec:
 <4> CORS access specifying selected resources and access methods. Additional HTTP headers in requests describe the origins that are permitted access to the Kafka cluster.
 <5> Requests for reservation of supported resources, currently `cpu` and `memory`, and limits to specify the maximum resources that can be consumed.
 <6> TLS configuration for encrypted connections to the Kafka cluster, with trusted certificates stored in X.509 format within the specified secrets.
-<7> Authentication for the Kafka Bridge cluster, specified as mTLS, token-based OAuth, SASL-based SCRAM-SHA-256/SCRAM-SHA-512, or PLAIN.
+<7> Authentication for the Kafka Bridge cluster, specified as `tls`, `scram-sha-256`, `scram-sha-512`, `plain`, or `oauth`.
 By default, the Kafka Bridge connects to Kafka brokers without authentication.
+For details on configuring authentication, see the link:{BookURLConfiguring}#type-KafkaBridgeSpec-schema-reference[`KafkaBridgeSpec` schema properties^]
 <8> Consumer configuration options.
 <9> Producer configuration options.
 <10> Kafka Bridge loggers and log levels added directly (`inline`) or indirectly (`external`) through a `ConfigMap`. Custom Log4j configuration must be placed under the `log4j2.properties` key in the `ConfigMap`. You can set log levels to `INFO`, `ERROR`, `WARN`, `TRACE`, `DEBUG`, `FATAL` or `OFF`.

documentation/modules/deploying/proc-deploy-kafka-bridge.adoc

@@ -3,7 +3,7 @@
 // deploying/assembly_deploy-kafka-bridge.adoc
 
 [id='deploying-kafka-bridge-{context}']
-= Deploying Kafka Bridge to your Kubernetes cluster
+= Deploying Kafka Bridge
 
 [role="_abstract"]
 This procedure shows how to deploy a Kafka Bridge cluster to your Kubernetes cluster using the Cluster Operator.
@@ -17,39 +17,50 @@ In this procedure, we use the following example file:
 
 .Prerequisites
 
-* xref:deploying-cluster-operator-str[The Cluster Operator must be deployed.]
+* Cluster Operator is deployed.
+* Kafka cluster is running.
++
+This procedure assumes that the Kafka cluster was deployed using Strimzi.
 
 .Procedure
 
+. Edit the deployment file to configure connection details (if required). 
++ 
+In `examples/bridge/kafka-bridge.yaml`, add or update the following properties as needed: 
++
+* `spec.bootstrapServers` to specify the Kafka bootstrap address.
+* `spec.authentication` to specify the authentication type as `tls`, `scram-sha-256`, `scram-sha-512`, `plain`, or `oauth`. +
+See the link:{BookURLConfiguring}#type-KafkaBridgeSpec-schema-reference[`KafkaBridgeSpec` schema properties^] for configuration details.
+* `spec.tls.trustedCertificates` to configure the TLS certificate. +
+Use `[]` (an empty array) to trust the default Java CAs, or specify secrets containing trusted certificates. +
+See the link:{BookURLConfiguring}#con-common-configuration-trusted-certificates-reference[`trustedCertificates` properties^] for configuration details.
+
 . Deploy Kafka Bridge to your Kubernetes cluster:
 +
-[source,shell,subs="attributes+"]
+[source,shell]
 ----
 kubectl apply -f examples/bridge/kafka-bridge.yaml
 ----
 
 . Check the status of the deployment:
 +
-[source,shell,subs="+quotes"]
+[source,shell]
 ----
-kubectl get pods -n _<my_cluster_operator_namespace>_
+kubectl get pods -n <my_cluster_operator_namespace>
 ----
 +
 .Output shows the deployment name and readiness
-[source,shell,subs="+quotes"]
+[source,shell]
 ----
 NAME                       READY  STATUS   RESTARTS
 my-bridge-bridge-<pod_id>  1/1    Running  0
 ----
 +
-`my-bridge` is the name of the Kafka Bridge cluster.
-+
-A pod ID identifies each pod created.
-+
-With the default deployment, you install a single Kafka Bridge pod.
-+
-`READY` shows the number of replicas that are ready/expected.
-The deployment is successful when the `STATUS` displays as `Running`.
+In this example, `my-bridge` is the name of the Kafka Bridge cluster.
+A pod ID identifies each created pod.
+By default, the deployment creates a single Kafka Bridge pod.
+`READY` shows the number of ready versus expected replicas. 
+The deployment is successful when the `STATUS` is `Running`.
 
 [role="_additional-resources"]
 .Additional resources

documentation/modules/deploying/proc-deploy-kafka-connect.adoc

@@ -3,7 +3,7 @@
 // deploying/assembly_deploy-kafka-connect.adoc
 
 [id='deploying-kafka-connect-{context}']
-= Deploying Kafka Connect to your Kubernetes cluster
+= Deploying Kafka Connect
 
 [role="_abstract"]
 This procedure shows how to deploy a Kafka Connect cluster to your Kubernetes cluster using the Cluster Operator.
@@ -36,7 +36,7 @@ In `examples/connect/kafka-connect.yaml`, add or update the following properties
 See the link:{BookURLConfiguring}#type-KafkaConnectSpec-schema-reference[`KafkaConnectSpec` schema properties^] for configuration details.
 * `spec.tls.trustedCertificates` to configure the TLS certificate. +
 Use `[]` (an empty array) to trust the default Java CAs, or specify secrets containing trusted certificates. +
-See link:{BookURLConfiguring}#con-common-configuration-trusted-certificates-reference[`trustedCertificates` properties^] for configuration details.
+See the link:{BookURLConfiguring}#con-common-configuration-trusted-certificates-reference[`trustedCertificates` properties^] for configuration details.
 
 . Configure the deployment for multiple Kafka Connect clusters (if required).
 + 

documentation/modules/deploying/proc-deploy-kafka-mirror-maker.adoc

@@ -3,7 +3,7 @@
 // deploying/assembly_deploy-kafka-mirror-maker.adoc
 
 [id='deploying-kafka-mirror-maker-{context}']
-= Deploying Kafka MirrorMaker to your Kubernetes cluster
+= Deploying Kafka MirrorMaker
 
 [role="_abstract"]
 This procedure shows how to deploy a Kafka MirrorMaker 2 cluster to your Kubernetes cluster using the Cluster Operator.
@@ -35,7 +35,7 @@ In `examples/mirror-maker/kafka-mirror-maker-2.yaml`, add or update the followin
 See the link:{BookURLConfiguring}#type-KafkaMirrorMaker2ClusterSpec-schema-reference[`KafkaMirrorMaker2Spec` schema properties^] for configuration details.
 * `spec.clusters[].tls.trustedCertificates` to configure the TLS certificate for each cluster. +
 Use `[]` (an empty array) to trust the default Java CAs, or specify secrets containing trusted certificates. +
-See link:{BookURLConfiguring}#con-common-configuration-trusted-certificates-reference[`trustedCertificates` properties^] for configuration details.
+See the link:{BookURLConfiguring}#con-common-configuration-trusted-certificates-reference[`trustedCertificates` properties^] for configuration details.
 
 . Configure the deployment for multiple MirrorMaker 2 clusters (if required).
 +