From 55ab934ca6723b3c4eaccec27f6f7f2892337713 Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Wed, 13 May 2020 14:31:07 +0100 Subject: [PATCH 1/6] Update links to point to website --- examples-of-custom-resources/advanced-routing/README.md | 4 ++-- examples-of-custom-resources/basic-configuration/README.md | 4 ++-- .../cross-namespace-configuration/README.md | 4 ++-- examples-of-custom-resources/traffic-splitting/README.md | 4 ++-- examples/complete-example/README.md | 2 +- examples/custom-annotations/README.md | 2 +- examples/custom-templates/README.md | 2 +- examples/customization/README.md | 2 +- examples/daemon-set/README.md | 2 +- examples/externalname-services/README.md | 2 +- examples/grpc-services/README.md | 2 +- examples/mergeable-ingress-types/README.md | 2 +- examples/multiple-ingress-controllers/README.md | 2 +- examples/opentracing/README.md | 2 +- examples/rbac/README.md | 2 +- examples/tcp-udp/README.md | 4 ++-- examples/wildcard-tls-certificate/README.md | 2 +- 17 files changed, 22 insertions(+), 22 deletions(-) diff --git a/examples-of-custom-resources/advanced-routing/README.md b/examples-of-custom-resources/advanced-routing/README.md index 5466d7dbd5..83ef68621f 100644 --- a/examples-of-custom-resources/advanced-routing/README.md +++ b/examples-of-custom-resources/advanced-routing/README.md @@ -1,13 +1,13 @@ # Advanced Routing -In this example we use the [VirtualServer](../../docs/virtualserver-and-virtualserverroute.md) resource to configure advanced routing for the cafe application from the [Basic Configuration](../basic-configuration/) example, for which we have introduced the following changes: +In this example we use the [VirtualServer](https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/) resource to configure advanced routing for the cafe application from the [Basic Configuration](../basic-configuration/) example, for which we have introduced the following changes: * Instead of one version of the tea service, we have two: `tea-post-svc` and `tea-svc`. We send POST requests for tea to `tea-post-svc` and non-POST requests, such as GET requests, to `tea-svc`. * Instead of one version of the coffee service, we have two: `coffee-v1-svc` and `coffee-v2-svc`. We send requests that include the cookie `version` set to `v2` to `coffee-v2-svc` and all other requests to `coffee-v1-svc`. * To simplify the example, we have removed TLS termination. ## Prerequisites -1. Follow the [installation](../../docs/installation.md) instructions to deploy the Ingress Controller with custom resources enabled. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress Controller with custom resources enabled. 1. Save the public IP address of the Ingress Controller into a shell variable: ``` $ IC_IP=XXX.YYY.ZZZ.III diff --git a/examples-of-custom-resources/basic-configuration/README.md b/examples-of-custom-resources/basic-configuration/README.md index 670e593cbf..09288f3e16 100644 --- a/examples-of-custom-resources/basic-configuration/README.md +++ b/examples-of-custom-resources/basic-configuration/README.md @@ -1,12 +1,12 @@ # Basic Configuration -In this example we configure load balancing with TLS termination for a simple web application using the [VirtualServer](../../docs/virtualserver-and-virtualserverroute.md) resource. The application, called cafe, lets you get either tea via the tea service or coffee via the coffee service. You indicate your drink preference with the URI of your HTTP request: URIs ending with `/tea` get you tea and URIs ending with `/coffee` get you coffee. +In this example we configure load balancing with TLS termination for a simple web application using the [VirtualServer](https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/) resource. The application, called cafe, lets you get either tea via the tea service or coffee via the coffee service. You indicate your drink preference with the URI of your HTTP request: URIs ending with `/tea` get you tea and URIs ending with `/coffee` get you coffee. The example is similar to the [complete example](../../examples/complete-example/README.md). However, instead of the Ingress resource, we use the VirtualServer. ## Prerequisites -1. Follow the [installation](../../docs/installation.md) instructions to deploy the Ingress Controller with custom resources enabled. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress Controller with custom resources enabled. 1. Save the public IP address of the Ingress Controller into a shell variable: ``` $ IC_IP=XXX.YYY.ZZZ.III diff --git a/examples-of-custom-resources/cross-namespace-configuration/README.md b/examples-of-custom-resources/cross-namespace-configuration/README.md index 614fc3606c..de32b01406 100644 --- a/examples-of-custom-resources/cross-namespace-configuration/README.md +++ b/examples-of-custom-resources/cross-namespace-configuration/README.md @@ -1,13 +1,13 @@ # Cross-Namespace Configuration -In this example we use the [VirtualServer and VirtualServerRoute](../../docs/virtualserver-and-virtualserverroute.md) resources to configure load balancing for the modified cafe application from the [Basic Configuration](../basic-configuration/) example. We have put the load balancing configuration as well as the deployments and services into multiple namespaces. Instead of one namespace, we now use three: `tea`, `coffee`, and `cafe`. +In this example we use the [VirtualServer and VirtualServerRoute](https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/) resources to configure load balancing for the modified cafe application from the [Basic Configuration](../basic-configuration/) example. We have put the load balancing configuration as well as the deployments and services into multiple namespaces. Instead of one namespace, we now use three: `tea`, `coffee`, and `cafe`. * In the tea namespace, we create the tea deployment, service, and the corresponding load-balancing configuration. * In the coffee namespace, we create the coffee deployment, service, and the corresponding load-balancing configuration. * In the cafe namespace, we create the cafe secret with the TLS certificate and key and the load-balancing configuration for the cafe application. That configuration references the coffee and tea configurations. ## Prerequisites -1. Follow the [installation](../../docs/installation.md) instructions to deploy the Ingress Controller with custom resources enabled. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress Controller with custom resources enabled. 1. Save the public IP address of the Ingress Controller into a shell variable: ``` $ IC_IP=XXX.YYY.ZZZ.III diff --git a/examples-of-custom-resources/traffic-splitting/README.md b/examples-of-custom-resources/traffic-splitting/README.md index 51ddcc018f..96fb025fd5 100644 --- a/examples-of-custom-resources/traffic-splitting/README.md +++ b/examples-of-custom-resources/traffic-splitting/README.md @@ -1,12 +1,12 @@ # Traffic Splitting -In this example we use the [VirtualServer](../../docs/virtualserver-and-virtualserverroute.md) resource to configure traffic splitting for the cafe application from the [Basic Configuration](../basic-configuration/) example, for which we have introduced the following changes: +In this example we use the [VirtualServer](https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/) resource to configure traffic splitting for the cafe application from the [Basic Configuration](../basic-configuration/) example, for which we have introduced the following changes: * Instead of one version of the coffee service, we have two: `coffee-v1-svc` and `coffee-v2-svc`. We send 90% of the coffee traffic to `coffee-v1-svc` and the remaining 10% to `coffee-v2-svc`. * To simplify the example, we have removed TLS termination and the tea service. ## Prerequisites -1. Follow the [installation](../../docs/installation.md) instructions to deploy the Ingress Controller with custom resources enabled. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress Controller with custom resources enabled. 1. Save the public IP address of the Ingress Controller into a shell variable: ``` $ IC_IP=XXX.YYY.ZZZ.III diff --git a/examples/complete-example/README.md b/examples/complete-example/README.md index 0389464bf5..ea638c2802 100644 --- a/examples/complete-example/README.md +++ b/examples/complete-example/README.md @@ -6,7 +6,7 @@ In this example we deploy the NGINX or NGINX Plus Ingress controller, a simple w ## 1. Deploy the Ingress Controller -1. Follow the installation [instructions](../../docs/installation.md) to deploy the Ingress controller. +1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/) to deploy the Ingress controller. 2. Save the public IP address of the Ingress controller into a shell variable: ``` diff --git a/examples/custom-annotations/README.md b/examples/custom-annotations/README.md index 7f5ea8202b..d755b0753c 100644 --- a/examples/custom-annotations/README.md +++ b/examples/custom-annotations/README.md @@ -9,7 +9,7 @@ Let's create a set of custom annotations to support [rate-limiting](https://ngin ## Prerequisites -* Read the [custom annotations doc](../../docs/custom-annotations.md) before going through this example first. +* Read the [custom annotations doc](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/custom-annotations/) before going through this example first. * Read about [custom templates](../custom-templates). ## Step 1 - Customize the Template diff --git a/examples/custom-templates/README.md b/examples/custom-templates/README.md index d5db93c06b..24bbd50dc6 100644 --- a/examples/custom-templates/README.md +++ b/examples/custom-templates/README.md @@ -1,6 +1,6 @@ # Custom Templates -The Ingress controller allows you to customize your templates through a [ConfigMap](../../docs/configmap-and-annotations.md) via the following keys: +The Ingress controller allows you to customize your templates through a [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) via the following keys: * `main-template` - Sets the main NGINX configuration template. * `ingress-template` - Sets the Ingress NGINX configuration template for an Ingress resource. diff --git a/examples/customization/README.md b/examples/customization/README.md index 2ab97d0f03..54e5690852 100644 --- a/examples/customization/README.md +++ b/examples/customization/README.md @@ -1,3 +1,3 @@ # Customization of NGINX Configuration -This example has been transformed into the [ConfigMap and Annotations doc](../../docs/configmap-and-annotations.md). \ No newline at end of file +This example has been transformed into the [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/) doc. \ No newline at end of file diff --git a/examples/daemon-set/README.md b/examples/daemon-set/README.md index 7d0741126a..5d93d81dee 100644 --- a/examples/daemon-set/README.md +++ b/examples/daemon-set/README.md @@ -2,4 +2,4 @@ You can deploy the NGINX or NGINX Plus controller as a [Daemon Set](https://kubernetes.io/docs/admin/daemons/). This allows you to deploy the controller on all or select nodes of your cluster. -Read the installation instructions [here](../../docs/installation.md). +Read the installation instructions [here](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/). diff --git a/examples/externalname-services/README.md b/examples/externalname-services/README.md index 30daa693a9..0e31917bbd 100644 --- a/examples/externalname-services/README.md +++ b/examples/externalname-services/README.md @@ -21,7 +21,7 @@ data: resolver-addresses: "10.0.0.10" ``` -Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap and Annotations](../../docs/configmap-and-annotations.md) section. +Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/) section. ## Example diff --git a/examples/grpc-services/README.md b/examples/grpc-services/README.md index f0bcdef98d..9413fd791d 100644 --- a/examples/grpc-services/README.md +++ b/examples/grpc-services/README.md @@ -4,7 +4,7 @@ To support a gRPC application with NGINX Ingress controllers, you need to add th ## Prerequisites -* HTTP/2 must be enabled. See `http2` ConfigMap key in the [ConfigMap and Annotations doc](../../docs/configmap-and-annotations.md). +* HTTP/2 must be enabled. See `http2` ConfigMap key in the [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/). * Ingress resources for gRPC applications must include TLS termination. ## Syntax diff --git a/examples/mergeable-ingress-types/README.md b/examples/mergeable-ingress-types/README.md index aab0ed965b..1bba5342f8 100644 --- a/examples/mergeable-ingress-types/README.md +++ b/examples/mergeable-ingress-types/README.md @@ -63,7 +63,7 @@ load balancing for that application using Ingress resources with the `nginx.org/ ## 1. Deploy the Ingress Controller -1. Follow the installation [instructions](../../docs/installation.md) to deploy the Ingress controller. +1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to deploy the Ingress controller. 2. Save the public IP address of the Ingress controller into a shell variable: ``` diff --git a/examples/multiple-ingress-controllers/README.md b/examples/multiple-ingress-controllers/README.md index 569cb26be8..910b3c5b01 100644 --- a/examples/multiple-ingress-controllers/README.md +++ b/examples/multiple-ingress-controllers/README.md @@ -1,3 +1,3 @@ # Using Multiple Ingress Controllers -This example has been transformed into the [Multiple Ingress Controllers doc](../../docs/multiple-ingress-controllers.md). +This example has been transformed into the [Multiple Ingress Controllers doc](https://docs.nginx.com/nginx-ingress-controller/installation/running-multiple-ingress-controllers/). diff --git a/examples/opentracing/README.md b/examples/opentracing/README.md index 498f9ccf7f..5f2a21331a 100644 --- a/examples/opentracing/README.md +++ b/examples/opentracing/README.md @@ -5,7 +5,7 @@ In this example we deploy the NGINX or NGINX Plus Ingress Controller and a simpl ## Prerequisites -The default Ingress Controller images don’t include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](../../docs/opentracing.md#Prerequisites) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. +The default Ingress Controller images don’t include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](https://docs.nginx.com/nginx-ingress-controller/third-party-modules/opentracing/) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. ## Step 1 - Deploy Ingress Controller and the Cafe App diff --git a/examples/rbac/README.md b/examples/rbac/README.md index 5b13952401..053677becb 100644 --- a/examples/rbac/README.md +++ b/examples/rbac/README.md @@ -1,3 +1,3 @@ # RBAC -It is possible to run the Ingress controller in a cluster with [RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) enabled. Read the installation instructions [here](../../docs/installation.md). \ No newline at end of file +It is possible to run the Ingress controller in a cluster with [RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) enabled. Read the installation instructions [here](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/). \ No newline at end of file diff --git a/examples/tcp-udp/README.md b/examples/tcp-udp/README.md index 030d9bd175..fed533854b 100644 --- a/examples/tcp-udp/README.md +++ b/examples/tcp-udp/README.md @@ -1,6 +1,6 @@ # Support for TCP/UDP Load Balancing -In this example we deploy the NGINX or NGINX Plus Ingress controller, a DNS server and then configure both TCP and UDP load balancing for the DNS server using the `stream-snippets` [ConfigMap key](../../docs/configmap-and-annotations.md). +In this example we deploy the NGINX or NGINX Plus Ingress controller, a DNS server and then configure both TCP and UDP load balancing for the DNS server using the `stream-snippets` [ConfigMap key](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/). The standard Kubernetes Ingress resources assume that all traffic is HTTP-based; they do not cater for the case of basic TCP or UDP load balancing. In this example, we use the `stream-snippets` ConfigMap key to embed the required TCP and UDP load-balancing configuration directly into the `stream{}` block of the NGINX configuration file. @@ -15,7 +15,7 @@ With NGINX, we’ll use the DNS name or virtual IP address to identify the servi ### 1. Deploy the Ingress Controller -1. Follow the installation [instructions](../../docs/installation.md) to deploy the Ingress controller. Make sure to expose port 5353 of the Ingress controller +1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to deploy the Ingress controller. Make sure to expose port 5353 of the Ingress controller both for TCP and UDP traffic. 2. Save the public IP address of the Ingress controller into a shell variable: diff --git a/examples/wildcard-tls-certificate/README.md b/examples/wildcard-tls-certificate/README.md index 6eb8696864..17ae5e328a 100644 --- a/examples/wildcard-tls-certificate/README.md +++ b/examples/wildcard-tls-certificate/README.md @@ -6,7 +6,7 @@ The wildcard TLS certificate simplifies the configuration of TLS termination if ### Prerequisites -Start the Ingress Controller with the `-wildcard-tls-secret` [command-line argument](../../docs/cli-arguments.md) set to a TLS secret with a wildcard cert/key. For example: +Start the Ingress Controller with the `-wildcard-tls-secret` [command-line argument](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/command-line-arguments/) set to a TLS secret with a wildcard cert/key. For example: ```yaml -wildcard-tls-secret=nginx-ingress/wildlcard-tls-secret From dd05fdea21f8577ae8676d9d0d0164ee9980472a Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Wed, 13 May 2020 20:48:00 +0100 Subject: [PATCH 2/6] Address feedback --- examples/opentracing/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/opentracing/README.md b/examples/opentracing/README.md index 5f2a21331a..967a0258af 100644 --- a/examples/opentracing/README.md +++ b/examples/opentracing/README.md @@ -5,7 +5,7 @@ In this example we deploy the NGINX or NGINX Plus Ingress Controller and a simpl ## Prerequisites -The default Ingress Controller images don’t include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](https://docs.nginx.com/nginx-ingress-controller/third-party-modules/opentracing/) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. +The default Ingress Controller images don’t include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](https://docs.nginx.com/nginx-ingress-controller/third-party-modules/opentracing/#prerequisites) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. ## Step 1 - Deploy Ingress Controller and the Cafe App From 4cc6c4855ba3bd12f5ea70da7c76d7c5939e9852 Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Tue, 26 May 2020 11:35:40 +0100 Subject: [PATCH 3/6] Address further feedback --- examples/externalname-services/README.md | 2 +- examples/grpc-services/README.md | 2 +- examples/opentracing/README.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/externalname-services/README.md b/examples/externalname-services/README.md index 0e31917bbd..a97856399c 100644 --- a/examples/externalname-services/README.md +++ b/examples/externalname-services/README.md @@ -21,7 +21,7 @@ data: resolver-addresses: "10.0.0.10" ``` -Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/) section. +Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/) sections. ## Example diff --git a/examples/grpc-services/README.md b/examples/grpc-services/README.md index 9413fd791d..b3fbd9bb2a 100644 --- a/examples/grpc-services/README.md +++ b/examples/grpc-services/README.md @@ -4,7 +4,7 @@ To support a gRPC application with NGINX Ingress controllers, you need to add th ## Prerequisites -* HTTP/2 must be enabled. See `http2` ConfigMap key in the [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/). +* HTTP/2 must be enabled. See `http2` ConfigMap key in the [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/#listeners) * Ingress resources for gRPC applications must include TLS termination. ## Syntax diff --git a/examples/opentracing/README.md b/examples/opentracing/README.md index 967a0258af..1d5ef97e0b 100644 --- a/examples/opentracing/README.md +++ b/examples/opentracing/README.md @@ -5,7 +5,7 @@ In this example we deploy the NGINX or NGINX Plus Ingress Controller and a simpl ## Prerequisites -The default Ingress Controller images don’t include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](https://docs.nginx.com/nginx-ingress-controller/third-party-modules/opentracing/#prerequisites) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. +The default Ingress Controller images do not include the OpenTracing module required for this example. See Step 1 of the [Prerequisites section](https://docs.nginx.com/nginx-ingress-controller/third-party-modules/opentracing/#prerequisites) in the OpenTracing doc for the instructions on how to get the right image with Jaeger tracer. ## Step 1 - Deploy Ingress Controller and the Cafe App From 18ab6da49b1422a489f0d19831835fa9fb71793b Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Wed, 27 May 2020 09:55:40 +0100 Subject: [PATCH 4/6] Further Addressing feedback --- examples/externalname-services/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/externalname-services/README.md b/examples/externalname-services/README.md index a97856399c..390d2ca8ab 100644 --- a/examples/externalname-services/README.md +++ b/examples/externalname-services/README.md @@ -21,7 +21,7 @@ data: resolver-addresses: "10.0.0.10" ``` -Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) and [Annotations](https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/) sections. +Additional resolver parameters, including the caching of DNS records, are available. Check the corresponding [ConfigMap](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) section. ## Example From 27226e70f28a4683df36cf32ddfedeb72ae33969 Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Thu, 28 May 2020 10:03:12 +0100 Subject: [PATCH 5/6] Feedback --- examples/complete-example/README.md | 2 +- examples/tcp-udp/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/complete-example/README.md b/examples/complete-example/README.md index ea638c2802..e58c251142 100644 --- a/examples/complete-example/README.md +++ b/examples/complete-example/README.md @@ -6,7 +6,7 @@ In this example we deploy the NGINX or NGINX Plus Ingress controller, a simple w ## 1. Deploy the Ingress Controller -1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/) to deploy the Ingress controller. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress controller. 2. Save the public IP address of the Ingress controller into a shell variable: ``` diff --git a/examples/tcp-udp/README.md b/examples/tcp-udp/README.md index fed533854b..14f88df467 100644 --- a/examples/tcp-udp/README.md +++ b/examples/tcp-udp/README.md @@ -15,7 +15,7 @@ With NGINX, we’ll use the DNS name or virtual IP address to identify the servi ### 1. Deploy the Ingress Controller -1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to deploy the Ingress controller. Make sure to expose port 5353 of the Ingress controller +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress controller. Make sure to expose port 5353 of the Ingress controller both for TCP and UDP traffic. 2. Save the public IP address of the Ingress controller into a shell variable: From 78e95caecf1fb66a39b30072b01b2e33ddeb2423 Mon Sep 17 00:00:00 2001 From: LorcanMcVeigh Date: Thu, 28 May 2020 14:33:23 +0100 Subject: [PATCH 6/6] wip --- examples/mergeable-ingress-types/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/mergeable-ingress-types/README.md b/examples/mergeable-ingress-types/README.md index 1bba5342f8..ed21708b46 100644 --- a/examples/mergeable-ingress-types/README.md +++ b/examples/mergeable-ingress-types/README.md @@ -63,7 +63,7 @@ load balancing for that application using Ingress resources with the `nginx.org/ ## 1. Deploy the Ingress Controller -1. Follow the installation [instructions](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to deploy the Ingress controller. +1. Follow the [installation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the Ingress controller. 2. Save the public IP address of the Ingress controller into a shell variable: ```