diff --git a/docs/tutorials/alibabacloud.md b/docs/tutorials/alibabacloud.md index 85ee20386..c26c17c1e 100644 --- a/docs/tutorials/alibabacloud.md +++ b/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) diff --git a/docs/tutorials/aws.md b/docs/tutorials/aws.md index cbac5d637..5444e337b 100644 --- a/docs/tutorials/aws.md +++ b/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) diff --git a/docs/tutorials/azure-private-dns.md b/docs/tutorials/azure-private-dns.md index fc515e9bb..c77012e91 100644 --- a/docs/tutorials/azure-private-dns.md +++ b/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. diff --git a/docs/tutorials/azure.md b/docs/tutorials/azure.md index c54cdf0cd..16afd6cd6 100644 --- a/docs/tutorials/azure.md +++ b/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. diff --git a/docs/tutorials/dyn.md b/docs/tutorials/dyn.md index 18fb7bbd8..26eb5a158 100644 --- a/docs/tutorials/dyn.md +++ b/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: diff --git a/docs/tutorials/exoscale.md b/docs/tutorials/exoscale.md index 608e4b6e8..07bce44f5 100644 --- a/docs/tutorials/exoscale.md +++ b/docs/tutorials/exoscale.md @@ -117,8 +117,11 @@ spec: http: paths: - backend: - serviceName: nginx - servicePort: 80 + service: + name: "nginx" + port: + number: 80 + pathType: Prefix --- diff --git a/docs/tutorials/gke.md b/docs/tutorials/gke.md index 319135f26..28419ad05 100644 --- a/docs/tutorials/gke.md +++ b/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 diff --git a/docs/tutorials/public-private-route53.md b/docs/tutorials/public-private-route53.md index 764a7e747..ffe455984 100644 --- a/docs/tutorials/public-private-route53.md +++ b/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 diff --git a/docs/tutorials/ultradns.md b/docs/tutorials/ultradns.md index 5f37093c5..95884c71f 100644 --- a/docs/tutorials/ultradns.md +++ b/docs/tutorials/ultradns.md @@ -251,6 +251,7 @@ spec: - http: paths: - path: /apple + pathType: Prefix backend: service: name: example-service