From f95f6c1cfd1b25fda2c1c93df5543a74d2acaff1 Mon Sep 17 00:00:00 2001 From: Gandham Jagadeesh Date: Fri, 19 Dec 2025 21:06:33 +0530 Subject: [PATCH] Update README.md /app2/* route should be route traffic to app2-nginx-nodeport-service The readme.md mentioned app1-nginx-nodeport-service --- .../08-03-ALB-Ingress-ContextPath-Based-Routing/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md b/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md index 82fc2e48..b9ac01d6 100755 --- a/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md +++ b/08-NEW-ELB-Application-LoadBalancers/08-03-ALB-Ingress-ContextPath-Based-Routing/README.md @@ -7,7 +7,7 @@ description: Learn AWS Load Balancer Controller - Ingress Context Path Based Rou - Discuss about the Architecture we are going to build as part of this Section - We are going to deploy all these 3 apps in kubernetes with context path based routing enabled in Ingress Controller - /app1/* - should go to app1-nginx-nodeport-service - - /app2/* - should go to app1-nginx-nodeport-service + - /app2/* - should go to app2-nginx-nodeport-service - /* - should go to app3-nginx-nodeport-service - As part of this process, this respective annotation `alb.ingress.kubernetes.io/healthcheck-path:` will be moved to respective application NodePort Service. - Only generic settings will be present in Ingress manifest annotations area `04-ALB-Ingress-ContextPath-Based-Routing.yml`