Fix ingress formal error

Author: lou-lan

docs/tutorials/alibabacloud.md

@@ -241,8 +241,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: foo
-          servicePort: 80
+          service:
+            name: foo
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 ## Verify ExternalDNS works (Service example)

docs/tutorials/aws.md

@@ -265,8 +265,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: foo
-          servicePort: 80
+          service:
+            name: foo
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 ## Verify ExternalDNS works (Service example)

docs/tutorials/azure-private-dns.md

@@ -387,9 +387,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: nginx-svc
-          servicePort: 80
-        path: /
+          service:
+            name: nginx-svc
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 When using ExternalDNS with ingress objects it will automatically create DNS records based on host names specified in ingress objects that match the domain-filter argument in the externaldns deployment manifest. When those host names are removed or renamed the corresponding DNS records are also altered.

docs/tutorials/azure.md

@@ -415,13 +415,16 @@ metadata:
     kubernetes.io/ingress.class: nginx
 spec:
   rules:
-  - host: server.example.com
-    http:
-      paths:
-      - backend:
-          serviceName: nginx-svc
-          servicePort: 80
-        path: /
+    - host: server.example.com
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: nginx-svc
+                port:
+                  number: 80
 ```
 
 When using external-dns with ingress objects it will automatically create DNS records based on host names specified in ingress objects that match the domain-filter argument in the external-dns deployment manifest. When those host names are removed or renamed the corresponding DNS records are also altered.

docs/tutorials/dyn.md

@@ -122,9 +122,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: my-awesome-service
-          servicePort: 8080
-
+          service:
+            name: my-awesome-service
+            port:
+              number: 8080
+        pathType: Prefix
 ```
 
 As the DNS name `test-ingress.example.com` matches the filter, external-dns will create two records:

docs/tutorials/exoscale.md

@@ -117,8 +117,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: nginx
-          servicePort: 80
+          service:
+            name: "nginx"
+            port:
+              number: 80
+        pathType: Prefix
 
 ---
 

docs/tutorials/gke.md

@@ -222,8 +222,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: nginx
-          servicePort: 80
+          service:
+            name: nginx
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 Again, after roughly two minutes check that a corresponding DNS record for your Ingress was created.
@@ -471,8 +474,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: nginx
-          servicePort: 80
+          service:
+            name: nginx
+            port:
+              number: 80
+        pathType: Prefix
 ---
 apiVersion: v1
 kind: Service

docs/tutorials/public-private-route53.md

@@ -306,8 +306,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: app
-          servicePort: 80
+          service:
+            name: app
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 Then create private Service definition:
@@ -327,8 +330,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: app
-          servicePort: 80
+          service:
+            name: app
+            port:
+              number: 80
+        pathType: Prefix
 ```
 
 Additionally, you may leverage [cert-manager](https://github.com/jetstack/cert-manager) to automatically issue SSL certificates from [Let's Encrypt](https://letsencrypt.org/). To do that, request a certificate in public service definition:
@@ -352,8 +358,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: app
-          servicePort: 80
+          service:
+            name: app
+            port:
+              number: 80
+        pathType: Prefix
   tls:
   - hosts:
     - app.domain.com
@@ -377,8 +386,11 @@ spec:
     http:
       paths:
       - backend:
-          serviceName: app
-          servicePort: 80
+          service:
+            name: app
+            port:
+              number: 80
+        pathType: Prefix
   tls:
   - hosts:
     - app.domain.com

docs/tutorials/ultradns.md

@@ -251,6 +251,7 @@ spec:
   - http:
       paths:
         - path: /apple
+          pathType: Prefix
           backend:
             service:
               name: example-service