docs(connect): updates the deployment instructions for kafka connect (#11301)

Signed-off-by: prmellor <[email protected]>

Author: PaulRMellor

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

@@ -167,8 +167,9 @@ In this example, JSON convertors are specified.
 A replication factor of 3 is set for the internal topics used by Kafka Connect (minimum requirement for production environment).
 Changing the replication factor after the topics have been created has no effect.
 <6> Requests for reservation of supported resources, currently `cpu` and `memory`, and limits to specify the maximum resources that can be consumed.
-<7> Authentication for the Kafka Connect cluster, specified as mTLS, token-based OAuth, SASL-based SCRAM-SHA-256/SCRAM-SHA-512, or PLAIN.
-By default, Kafka Connect connects to Kafka brokers using a plain text connection.
+<7> Authentication for the Kafka Connect cluster, specified as `tls`, `scram-sha-256`, `scram-sha-512`, `plain`, or `oauth`.
+By default, Kafka Connect connects to Kafka brokers using a plaintext connection.
+For details on configuring authentication, see the link:{BookURLConfiguring}#type-KafkaConnectSpec-schema-reference[`KafkaConnectSpec` schema properties^].
 <8> TLS configuration for encrypted connections to the Kafka cluster, with trusted certificates stored in X.509 format within the specified secrets.
 <9> Build configuration properties for building a container image with connector plugins automatically.
 <10> (Required) Configuration of the container registry where new images are pushed.

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

@@ -8,7 +8,7 @@
 [role="_abstract"]
 This procedure shows how to deploy a Kafka Connect cluster to your Kubernetes cluster using the Cluster Operator.
 
-A Kafka Connect cluster deployment is implemented with a configurable number of nodes (also called _workers_) that distribute the workload of connectors as _tasks_ so that the message flow is highly scalable and reliable.
+A Kafka Connect cluster deployment is implemented with a configurable number of nodes (also called _workers_) that distribute the workload of connectors as _tasks_, ensuring a scalable and reliable message flow.
 
 The deployment uses a YAML file to provide the specification to create a `KafkaConnect` resource.
 
@@ -17,45 +17,62 @@ In this procedure, we use the following example file:
 
 * `examples/connect/kafka-connect.yaml`
 
-IMPORTANT: If deploying Kafka Connect clusters to run in parallel, each instance must use unique names for internal Kafka Connect topics. 
-To do this, xref:con-config-kafka-connect-multiple-instances-{context}[configure each Kafka Connect instance to replace the defaults].  
-
 .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/connect/kafka-connect.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-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.
+
+. Configure the deployment for multiple Kafka Connect clusters (if required).
++ 
+If you plan to run more than one Kafka Connect cluster in the same environment, each instance must use unique internal topic names and a unique group ID.
++ 
+Update the `spec.config` properties in `kafka-connect.yaml` to replace the default values.
++
+See xref:con-config-kafka-connect-multiple-instances-{context}[Configuring multiple Kafka Connect clusters] for details.
+
 . Deploy Kafka Connect to your Kubernetes cluster.
 Use the `examples/connect/kafka-connect.yaml` file to deploy Kafka Connect.
 +
-[source,shell,subs="attributes+"]
+[source,shell]
 ----
 kubectl apply -f examples/connect/kafka-connect.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-connect-cluster-connect-<pod_id>  1/1    Running  0
 ----
 +
-`my-connect-cluster` is the name of the Kafka Connect cluster.
-+
-A pod ID identifies each pod created.
-+
-With the default deployment, you create a single Kafka Connect 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-connect-cluster` is the name of the Kafka Connect cluster. 
+A pod ID identifies each created pod. 
+By default, the deployment creates a single Kafka Connect pod. 
+`READY` shows the number of ready versus expected replicas. 
+The deployment is successful when the `STATUS` is `Running`.
 
 [role="_additional-resources"]
 .Additional resources