From ad54d4cad29e554024977dde6a818a0f94b72f02 Mon Sep 17 00:00:00 2001 From: Martin Linkhorst Date: Tue, 7 Jan 2020 14:42:47 +0100 Subject: [PATCH] docs: switch apiVersion of Ingress to networking --- docs/tutorials/alb-ingress.md | 2 +- docs/tutorials/alibabacloud.md | 2 +- docs/tutorials/aws.md | 2 +- docs/tutorials/azure.md | 4 ++-- docs/tutorials/coredns.md | 4 ++-- docs/tutorials/dyn.md | 2 +- docs/tutorials/exoscale.md | 2 +- docs/tutorials/gke.md | 2 +- docs/tutorials/nginx-ingress.md | 2 +- docs/tutorials/public-private-route53.md | 8 ++++---- docs/tutorials/rdns.md | 2 +- 11 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/tutorials/alb-ingress.md b/docs/tutorials/alb-ingress.md index b1806e61c..3eb403b21 100644 --- a/docs/tutorials/alb-ingress.md +++ b/docs/tutorials/alb-ingress.md @@ -75,7 +75,7 @@ type `LoadBalancer` here, since we will be using an Ingress to create an ALB. Create the following Ingress to expose the echoserver application to the Internet. ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: diff --git a/docs/tutorials/alibabacloud.md b/docs/tutorials/alibabacloud.md index 51b75194f..fb15711ac 100644 --- a/docs/tutorials/alibabacloud.md +++ b/docs/tutorials/alibabacloud.md @@ -232,7 +232,7 @@ Create an ingress resource manifest file. > For ingress objects ExternalDNS will create a DNS record based on the host specified for the ingress object. ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: foo diff --git a/docs/tutorials/aws.md b/docs/tutorials/aws.md index ad4e0af89..ec86fc0ef 100644 --- a/docs/tutorials/aws.md +++ b/docs/tutorials/aws.md @@ -193,7 +193,7 @@ Create an ingress resource manifest file. > For ingress objects ExternalDNS will create a DNS record based on the host specified for the ingress object. ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: foo diff --git a/docs/tutorials/azure.md b/docs/tutorials/azure.md index 70845af87..18f7ab71c 100644 --- a/docs/tutorials/azure.md +++ b/docs/tutorials/azure.md @@ -396,9 +396,9 @@ spec: selector: app: nginx type: ClusterIP - + --- -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx diff --git a/docs/tutorials/coredns.md b/docs/tutorials/coredns.md index de8b16fca..01cbd2476 100644 --- a/docs/tutorials/coredns.md +++ b/docs/tutorials/coredns.md @@ -196,8 +196,8 @@ minikube addons enable ingress ## Testing ingress example ``` -$ cat ingress.yaml -apiVersion: extensions/v1beta1 +$ cat ingress.yaml +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx diff --git a/docs/tutorials/dyn.md b/docs/tutorials/dyn.md index a5aacf480..ed4d24ffc 100644 --- a/docs/tutorials/dyn.md +++ b/docs/tutorials/dyn.md @@ -111,7 +111,7 @@ Having `--dry-run=true` and `--log-level=debug` is a great way to see _exactly_ Create a file called 'test-ingress.yaml' with the following contents: ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test-ingress diff --git a/docs/tutorials/exoscale.md b/docs/tutorials/exoscale.md index 83ad1328f..a72c17423 100644 --- a/docs/tutorials/exoscale.md +++ b/docs/tutorials/exoscale.md @@ -107,7 +107,7 @@ subjects: Spin up a simple nginx HTTP server with the following spec (`kubectl apply -f`): ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx diff --git a/docs/tutorials/gke.md b/docs/tutorials/gke.md index cbedc727b..2de5cafb7 100644 --- a/docs/tutorials/gke.md +++ b/docs/tutorials/gke.md @@ -255,7 +255,7 @@ $ curl nginx.external-dns-test.gcp.zalan.do Let's check that Ingress works as well. Create the following Ingress. ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx diff --git a/docs/tutorials/nginx-ingress.md b/docs/tutorials/nginx-ingress.md index c7438f9f9..4ad7ce132 100644 --- a/docs/tutorials/nginx-ingress.md +++ b/docs/tutorials/nginx-ingress.md @@ -282,7 +282,7 @@ Use `--dry-run` if you want to be extra careful on the first run. Note, that you Create the following sample application to test that ExternalDNS works. ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx diff --git a/docs/tutorials/public-private-route53.md b/docs/tutorials/public-private-route53.md index 66c3e1386..179c59582 100644 --- a/docs/tutorials/public-private-route53.md +++ b/docs/tutorials/public-private-route53.md @@ -292,7 +292,7 @@ For this setup to work, you've to create two Service definitions for your applic At first, create public Service definition: ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: @@ -313,7 +313,7 @@ spec: Then create private Service definition: ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: @@ -334,7 +334,7 @@ spec: 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: ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: @@ -363,7 +363,7 @@ spec: And reuse the requested certificate in private Service definition: ```yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: diff --git a/docs/tutorials/rdns.md b/docs/tutorials/rdns.md index 8738d023d..92421392e 100644 --- a/docs/tutorials/rdns.md +++ b/docs/tutorials/rdns.md @@ -141,7 +141,7 @@ spec: ## Testing ingress example ``` $ cat ingress.yaml -apiVersion: extensions/v1beta1 +apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: nginx