updated design images

Signed-off-by: Aswin A <[email protected]>

083-stretch-cluster.md

@@ -29,10 +29,10 @@ The cluster operator will be deployed in all Kubernetes clusters and will manage
 This approach will allow users to specify/manage the definition of stretch Kafka cluster in a single location. The operators will then create necessary resources in target Kubernetes clusters, which can then be reconciled/managed by operators on those clusters.
 
 ### Reconciling Kafka and KafkaNodePool resources
-<img width="1321" alt="image" src="https://media.github.ibm.com/user/473362/files/0a1a4e7f-8227-47da-86b1-4b27a83fdb9d">
+![Reconciling Kafka and KafkaNodePool resources](./images/083-reconciling-kafka-knp.png)
 
 ### Reconciling StrimziPodSet resources
-<img width="1317" alt="image" src="https://media.github.ibm.com/user/473362/files/f4524847-3c9c-4a8c-a5fd-4a76b6ec0bf4">
+![Reconciling SPS](./images/083-reconciling-sps.png)
 
 #### KafkaNodePool changes
 A new optional field (`target`) will be introduced in the KafkaNodePool resource specification, to allow users to specify the details of the Kubernetes cluster where the node pool should be deployed. This section will include the target cluster's URL (Kubernetes cluster where resources for this node pool will be created) and the secret containing the kubeconfig data for that cluster. 
@@ -135,7 +135,7 @@ This proposal only impacts strimzi-kafka-operator project.
 - Use network technologies like skupper, submariner etc to allow internal services to be visible on other clusters
   -  introduces additional dependencies and complexity to the Strimzi project
 
-<img width="1057" alt="image" src="https://media.github.ibm.com/user/473362/files/9a9720f9-9ccf-4d4f-a56c-9a35917af711">
+![Synchronized ClusterOperator](./images/083-synchronized-clusteroperator.png)
 
 
 An alternative approach considered was setting up a stretch Kafka cluster with synchronized `KafkaStretchCluster` and `Kafka` custom resources (CRs). The idea was to introduce a new CR called `KafkaStretchCluster`, which would contain details of all the clusters involved in the stretch Kafka deployment. The spec would include information such as cluster names, secrets for connecting to each Kubernetes cluster, and a list of node pools across the entire stretch cluster.