- converting images to webp

- Adding new words to spell checker
- adding timin date for the troublehsooting module

.spelling

@@ -124,4 +124,7 @@ weaveworks
 nirmal
 mehta
 sheetal
-joshi
+joshi
+Ishikawa
+deprioritized
+scattergun

website/docs/troubleshooting/Scenarios/alb/alb_fix.md

@@ -5,7 +5,7 @@ sidebar_position: 30
 
 The task for you in this troubleshooting scenario is to investigate the deployment for AWS Load Balancer Controller as well as the ingress object created by following the prompts with the script. At the end of this session, you should be able to see the ui app on your EKS cluster using ALB ingress through the browsers as depicted in the image.
 
-![ingress](./assets/ingress.png)
+![ingress](./assets/ingress.webp)
 
 ## Let's start the troubleshooting
 
@@ -255,7 +255,7 @@ Also, feel free to go to CloudTrail again and verify the API call for CreateLoad
 
 Even though the ingress creation succeeded, when you try accessing the app in browser there is an error stating, "Backend service does not exist".
 
-![ALb-Backend-DoesNotExist](./assets/alb-does-not-exist.png)
+![ALb-Backend-DoesNotExist](./assets/alb-does-not-exist.webp)
 
 Since ingress is created, that would mean that there is an issue with communication from the Kubernetes ingress to the service. Check the deployment and service using:
 
@@ -365,7 +365,7 @@ Try accessing the ALB again using the domain name shared in the get ingress outp
 
 Now we observe a 503 error when accessing the ALB:
 
-![ALb-503-ERROR](./assets/alb-503.png)
+![ALb-503-ERROR](./assets/alb-503.webp)
 
 503 would suggest a server-side issue, specifically with the service being unavailable. But we ensured that the service was running on the cluster when we ran get service command in _Step 7_.
 
@@ -479,7 +479,7 @@ $ kubectl apply -k ~/environment/eks-workshop/modules/troubleshooting/alb/creati
 
 Now refresh the browsers and you should see the ui application:
 
-![ALB-UI-APP](./assets/alb-working.png)
+![ALB-UI-APP](./assets/alb-working.webp)
 
 **Go ahead and enjoy a break, you’ve earned it!!**
 

website/docs/troubleshooting/Scenarios/index.md

@@ -8,5 +8,5 @@ Even with careful planning and preparation, unexpected issues can sometimes aris
 These are the scenarios covered:
 
 - AWS Load Balancer Controller
-- Node not ready
+- Node not ready (Coming soon)
 - others..

website/lab-timing-data.json

@@ -250,5 +250,11 @@
         "directory": "security/cluster-access-management",
         "file": "security/cluster-access-management/index.md",
         "executionTimeSeconds": 207
+    },
+    "troubleshooting/scenarios/alb/index.md": {
+        "title": "Troubleshooting Module",
+        "directory": "troubleshooting/scenarios/alb",
+        "file": "troubleshooting/scenarios/alb/index.md",
+        "executionTimeSeconds": 780
     }
 }