From 03ee3039796a88a80e15fda73fa40f3a8aca0288 Mon Sep 17 00:00:00 2001
From: Greg Whorley <11302134+gregwhorley@users.noreply.github.com>
Date: Wed, 3 Nov 2021 12:26:20 -0700
Subject: [PATCH] Fix ingress spec in given examples

### Description
A previous PR (#1978) updated the ingress API version but the spec needed an update as well. I tested this locally by applying the yaml with a valid DNS hostname.

### Checklist
- [ ] Unit tests updated
- [x] End user documentation updated
---
 docs/tutorials/alb-ingress.md | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)

diff --git a/docs/tutorials/alb-ingress.md b/docs/tutorials/alb-ingress.md
index 0d818ac54..4e68a3e53 100644
--- a/docs/tutorials/alb-ingress.md
+++ b/docs/tutorials/alb-ingress.md
@@ -88,9 +88,11 @@ spec:
     http: &echoserver_root
       paths:
       - backend:
-          serviceName: echoserver
-          servicePort: 80
-        path: /
+          service:
+            name: echoserver
+            port:
+              number: 80
+        pathType: ImplementationSpecific
   - host: echoserver.example.org
     http: *echoserver_root
 ```
@@ -123,9 +125,11 @@ spec:
   - http:
       paths:
       - backend:
-          serviceName: echoserver
-          servicePort: 80
-        path: /
+          service:
+            name: echoserver
+            port:
+              number: 80
+        pathType: ImplementationSpecific
 ```
 
 In the above example we create a default path that works for any hostname, and
@@ -159,9 +163,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: echoserver
-          servicePort: 80
-        path: /
+          service:
+            name: echoserver
+            port:
+              number: 80
+        pathType: ImplementationSpecific
 ```
 
 The above Ingress object will result in the creation of an ALB with a dualstack