Various small upgrade fixes

Author: niallthomson

website/docs/fundamentals/exposing/ingress/adding-ingress.md

@@ -105,16 +105,16 @@ You can also inspect the ALB and its target groups in the console by clicking th
 Get the URL from the Ingress resource:
 
 ```bash
-$ ADDRESS=$(kubectl get ingress -n ui ui -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+$ ADDRESS=$(kubectl get ingress -n ui ui -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 $ echo "http://${ADDRESS}"
-http://k8s-ui-uinlb-a9797f0f61.elb.us-west-2.amazonaws.com
+http://k8s-ui-ui-a9797f0f61.elb.us-west-2.amazonaws.com
 ```
 
 To wait until the load balancer has finished provisioning you can run this command:
 
 ```bash
 $ curl --head -X GET --retry 30 --retry-all-errors --retry-delay 15 --connect-timeout 30 --max-time 60 \
-  -k $(kubectl get ingress -n ui ui -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+  -k $(kubectl get ingress -n ui ui -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 ```
 
 And access it in your web browser. You will see the UI from the web store displayed and will be able to navigate around the site as a user.

website/docs/fundamentals/exposing/ingress/multiple-ingress.md

@@ -61,21 +61,21 @@ To wait until the load balancer has finished provisioning you can run this comma
 
 ```bash timeout=180
 $ curl --head -X GET --retry 30 --retry-all-errors --retry-delay 15 --connect-timeout 30 --max-time 60 \
-  -k $(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+  -k $(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 ```
 
 Try accessing the new Ingress URL in the browser as before to check the web UI still works:
 
 ```bash
-$ ADDRESS=$(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+$ ADDRESS=$(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 $ echo "http://${ADDRESS}"
 http://k8s-retailappgroup-2c24c1c4bc-17962260.us-west-2.elb.amazonaws.com
 ```
 
 Now try accessing a path we directed to the catalog service:
 
 ```bash
-$ ADDRESS=$(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+$ ADDRESS=$(kubectl get ingress -n catalog catalog-multi -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 $ curl $ADDRESS/catalog/products | jq .
 ```
 

website/docs/fundamentals/exposing/loadbalancer/adding-lb.md

@@ -122,14 +122,16 @@ You can also inspect the NLB in the console by clicking this link:
 Get the URL from the Service resource:
 
 ```bash
-$ kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}"
-k8s-ui-uinlb-a9797f0f61.elb.us-west-2.amazonaws.com
+$ ADDRESS=$(kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}}")
+$ echo "http://${ADDRESS}"
+http://k8s-ui-uinlb-a9797f0f61.elb.us-west-2.amazonaws.com
 ```
 
 To wait until the load balancer has finished provisioning you can run this command:
 
 ```bash
-$ wait-for-lb $(kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+$ curl --head -X GET --retry 30 --retry-all-errors --retry-delay 15 --connect-timeout 30 --max-time 60 \
+  -k $(kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 ```
 
 Now that our application is exposed to the outside world, lets try to access it by pasting that URL in your web browser. You will see the UI from the web store displayed and will be able to navigate around the site as a user.

website/docs/fundamentals/exposing/loadbalancer/ip-mode.md

@@ -143,5 +143,6 @@ As expected we now have 3 targets, matching the number of replicas in the ui Dep
 If you want to wait to make sure the application still functions the same, run the following command. Otherwise you can proceed to the next module.
 
 ```bash timeout=240
-$ wait-for-lb $(kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}{'\n'}")
+$ curl --head -X GET --retry 30 --retry-all-errors --retry-delay 15 --connect-timeout 30 --max-time 60 \
+  -k $(kubectl get service -n ui ui-nlb -o jsonpath="{.status.loadBalancer.ingress[*].hostname}")
 ```

website/docs/observability/high-availability/02-pod-failure.md

@@ -22,7 +22,7 @@ manifests/modules/observability/resiliency/scripts/pod-failure.sh
 
 ## Running the Experiment
 
-## Step 1: Check Initial Pod Status
+### Step 1: Check Initial Pod Status
 
 First, let's check the initial status of the pods in the `ui` namespace:
 

website/docs/observability/high-availability/04-node-failure-partial-fis.md

@@ -93,7 +93,6 @@ $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/comp
 $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/component=dynamodb
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=redis
-$ kubectl delete pod --grace-period=0 --force -n assets -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=mysql
 $ kubectl delete pod --grace-period=0 --force -n ui -l app.kubernetes.io/component=service

website/docs/observability/high-availability/05-node-failure-complete-fis.md

@@ -66,7 +66,6 @@ $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/comp
 $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/component=dynamodb
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=redis
-$ kubectl delete pod --grace-period=0 --force -n assets -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=mysql
 $ kubectl delete pod --grace-period=0 --force -n ui -l app.kubernetes.io/component=service

website/docs/observability/high-availability/07-az-failure.md

@@ -68,7 +68,6 @@ $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/comp
 $ kubectl delete pod --grace-period=0 --force -n carts -l app.kubernetes.io/component=dynamodb
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n checkout -l app.kubernetes.io/component=redis
-$ kubectl delete pod --grace-period=0 --force -n assets -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=service
 $ kubectl delete pod --grace-period=0 --force -n orders -l app.kubernetes.io/component=mysql
 $ kubectl delete pod --grace-period=0 --force -n ui -l app.kubernetes.io/component=service

website/docs/observability/opensearch/pod-logs.md

@@ -59,24 +59,23 @@ Now we can check that our `ui` component is creating logs by directly using `kub
 
 ```bash
 $ kubectl logs -n ui deployment/ui
-Picked up JAVA_TOOL_OPTIONS: -javaagent:/opt/aws-opentelemetry-agent.jar
-OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
-[otel.javaagent 2023-11-07 02:05:03:383 +0000] [main] INFO io.opentelemetry.javaagent.tooling.VersionLogger - opentelemetry-javaagent - version: 1.24.0-aws
+Picked up JAVA_TOOL_OPTIONS:
 
   .   ____          _            __ _ _
  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
   '  |____| .__|_| |_|_| |_\__, | / / / /
  =========|_|==============|___/=/_/_/_/
- :: Spring Boot ::                (v3.0.6)
-
-2023-11-07T02:05:05.512Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : Starting UiApplication v0.0.1-SNAPSHOT using Java 17.0.7 with PID 1 (/app/app.jar started by appuser in /app)
-2023-11-07T02:05:05.524Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : No active profile set, falling back to 1 default profile: "default"
-2023-11-07T02:05:09.906Z  WARN 1 --- [           main] o.s.b.a.e.EndpointId                     : Endpoint ID 'fail-cart' contains invalid characters, please migrate to a valid format.
-2023-11-07T02:05:10.060Z  INFO 1 --- [           main] o.s.b.a.e.w.EndpointLinksResolver        : Exposing 15 endpoint(s) beneath base path '/actuator'
-2023-11-07T02:05:10.590Z  INFO 1 --- [           main] o.s.b.w.e.n.NettyWebServer               : Netty started on port 8080
-2023-11-07T02:05:10.616Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : Started UiApplication in 5.917 seconds (process running for 7.541)
+ :: Spring Boot ::                (v3.4.4)
+
+2025-07-26T10:38:05.763Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : Starting UiApplication v0.0.1-SNAPSHOT using Java 21.0.7 with PID 1 (/app/app.jar started by appuser in /app)
+2025-07-26T10:38:05.820Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : The following 1 profile is active: "prod"
+2025-07-26T10:38:09.105Z  INFO 1 --- [           main] i.o.i.s.a.OpenTelemetryAutoConfiguration : OpenTelemetry Spring Boot starter has been disabled
+
+2025-07-26T10:38:10.323Z  INFO 1 --- [           main] o.s.b.a.e.w.EndpointLinksResolver        : Exposing 4 endpoints beneath base path '/actuator'
+2025-07-26T10:38:12.338Z  INFO 1 --- [           main] o.s.b.w.e.n.NettyWebServer               : Netty started on port 8080 (http)
+2025-07-26T10:38:12.365Z  INFO 1 --- [           main] c.a.s.u.UiApplication                    : Started UiApplication in 7.481 seconds (process running for 9.223)
 
 ```