architectural visuals for migrate_to_eks content #1408 (#1440)

* architectural visuals for migrate_to_eks content #1408

* incorporated PR comments 1408

Author: kayalvizhi-kandasamy

content/intermediate/200_migrate_to_eks/configure-eks-cluster.md

@@ -9,7 +9,9 @@ If the Postgres pod moves availability zones data will still be available.
 If you'd like to do it manually you can follow the [EFS workshop here](https://www.eksworkshop.com/beginner/190_efs/).
 
 
-To let traffic cross between EKS and Cloud9 we need to create a VPC peer between our Cloud9 instance and our EKS cluster.
+To let traffic cross between EKS and Cloud9 we need to create a VPC peering between our Cloud9 instance and our EKS cluster as shown.
+![configure eks cluster vpc-peering](/images/migrate_to_eks/configure-eks-cluster-vpc-peering.png)
+
 
 ```bash
 export EKS_VPC=$(aws eks describe-cluster \

content/intermediate/200_migrate_to_eks/create-kind-cluster.md

@@ -3,7 +3,10 @@ title: "Create kind cluster"
 weight: 10
 ---
 
-While our EKS cluster is being created we can create a kind cluster locally.
+While our EKS cluster is being created we can create a kind cluster locally on the cloud9 instance.
+
+![kind cluster](/images/migrate_to_eks/create-kind-cluster.png)
+
 Before we create one lets make sure our network rules are set up
 
 {{% notice note %}}

content/intermediate/200_migrate_to_eks/deploy-counter-app-eks.md

@@ -6,9 +6,11 @@ weight: 50
 Now it's time to migrate our app to EKS.
 We're going to do this in two stages.
 
-First we'll move the frontend component but have it talk to the database in our old cluster.
-Then we'll set up the database in EKS, migrate the data, and configure the frontend to use it instead.
+Stage 1: First we'll move the frontend component but have it talk to the database in our old cluster.
+![front-end moved to eks](/images/migrate_to_eks/front-end-moved-to-eks.png)
 
+Stage 2: Then we'll set up the database in EKS, migrate the data, and configure the frontend to use it instead.
+![database moved to eks](/images/migrate_to_eks/database-moved-to-eks.png) 
 The counter app deployment and service is the same as it was in kind except we added two environment varibles for the `DB_HOST` and `DB_PORT` and the service type is LoadBalancer instead of NodePort.
 
 ```bash

content/intermediate/200_migrate_to_eks/deploy-counter-app-kind.md

@@ -8,6 +8,9 @@ Once the kind cluster is ready we can check it with
 ```bash
 kubectl --context kind-kind get nodes
 ```
+Let us deploy the counter app in the kind cluster as shown here.
+
+![counter app recording](/images/migrate_to_eks/counter-application-from-kind-cluster.png)
 
 Deploy our postgres database to the cluster.
 First create a ConfigMap to initialize an empty database and then create a PersistentVolume on hostPath to store the data.