You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A `NodePort` service will randomly allocate one port on every node of the cluster. To access NGINX Kubernetes Gateway, use an IP address of any node in the cluster along with the allocated port.
71
+
A `NodePort` Service will randomly allocate one port on every Node of the cluster. To access NGINX Kubernetes Gateway, use an IP address of any Node in the cluster along with the allocated port.
72
72
73
73
### Create a LoadBalancer Service
74
74
75
-
Create a service with type `LoadBalancer` using the appropriate manifest for your cloud provider.
75
+
Create a Service with type `LoadBalancer` using the appropriate manifest for your cloud provider.
76
76
77
77
- For GCP or Azure:
78
78
@@ -108,4 +108,4 @@ Create a service with type `LoadBalancer` using the appropriate manifest for you
108
108
109
109
### Use NGINX Kubernetes Gateway
110
110
111
-
To get started, follow the tutorials in the [examples](../examples/) directory.
111
+
To get started, follow the tutorials in the [examples](../examples) directory.
> Note: NGINX will not listen on any ports until you configure a [Gateway](https://gateway-api.sigs.k8s.io/api-types/gateway/#gateway) resource with a valid listener.
31
31
32
32
## Use NGINX Kubernetes Gateway
33
-
To get started, follow the tutorials in the [examples](../examples/) directory.
33
+
To get started, follow the tutorials in the [examples](../examples) directory.
Copy file name to clipboardExpand all lines: examples/advanced-routing/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
In this example we will deploy NGINX Kubernetes Gateway and configure advanced routing rules for a simple cafe application.
4
4
We will use `HTTPRoute` resources to route traffic to the cafe application based on a combination of the request method, headers, and query parameters.
5
5
6
-
The cafe application consists of four services: `coffee-v1-svc`, `coffee-v2-svc`, `tea-svc`, and `tea-post-svc`. In the next section we will create the following routing rules for the cafe application:
6
+
The cafe application consists of four Services: `coffee-v1-svc`, `coffee-v2-svc`, `tea-svc`, and `tea-post-svc`. In the next section we will create the following routing rules for the cafe application:
7
7
- For the path `/coffee` route requests with the header `version` set to `v2` or with the query param `TEST` set to `v2` to `coffee-v2-svc`, and all other requests to `coffee-v1-svc`.
8
8
- For the path `/tea` route POST requests to `tea-post-svc`, and all other requests, such as `GET` requests, to `tea-svc`.
9
9
@@ -27,7 +27,7 @@ The cafe application consists of four services: `coffee-v1-svc`, `coffee-v2-svc`
27
27
28
28
## 2. Deploy the Cafe Application
29
29
30
-
1. Create the coffee and the tea deployments and services:
30
+
1. Create the coffee and the tea Deployments and Services:
0 commit comments