@@ -15,7 +15,7 @@ This guide will demonstrate how to:
15
15
16
16
## Prerequisities
17
17
18
- 1 . Administrator access to a Kubernetes cluster is required .
18
+ 1 . Administrator access to a Kubernetes cluster.
19
19
2 . [ Helm] ( https://helm.sh ) and [ kubectl] ( https://kubernetes.io/docs/tasks/tools/#kubectl ) must be installed locally.
20
20
3 . Deploy NGINX Kubernetes Gateway (NKG) following the [ deployment instructions] ( /docs/installation.md ) .
21
21
4 . A DNS resolvable domain name is required. It must resolve to the public endpoint of the NKG deployment, and this
@@ -44,9 +44,9 @@ At a high level, the process looks like this:
44
44
that is referenced by the Gateway resource. As a result, NGINX is configured to terminate HTTPS traffic from clients
45
45
using this signed keypair.
46
46
5 . We deploy our application and our HTTPRoute which defines our routing rules. The routing rules defined configure
47
- NGINX to direct requests to https://www. cafe.example.com/coffee to our coffee-app application, and to use the https
47
+ NGINX to direct requests to https://cafe.example.com/coffee to our coffee-app application, and to use the https
48
48
Listener defined in our Gateway resource.
49
- 6 . When the client connects to https://www. cafe.example.com/coffee , the request is routed to the coffee-app application
49
+ 6 . When the client connects to https://cafe.example.com/coffee , the request is routed to the coffee-app application
50
50
and the communication is secured using the signed keypair contained in the cafe-secret Secret.
51
51
7 . The certificate will be automatically renewed when it is close to expiry, the Secret will be updated using the new
52
52
Certificate, and NKG will dynamically update the keypair on the filesystem used by NGINX for HTTPS termination once
@@ -58,24 +58,24 @@ At a high level, the process looks like this:
58
58
59
59
The first step is to deploy cert-manager onto the cluster.
60
60
61
- 1 . Add the Helm repository
61
+ - Add the Helm repository.
62
62
63
- ``` shell
63
+ ``` shell
64
64
helm repo add jetstack https://charts.jetstack.io
65
65
helm repo update
66
- ```
67
-
68
- 1 . Install cert-manager, and enable the GatewayAPI feature gate:
69
-
70
- ``` shell
71
- helm install \
72
- cert-manager jetstack/cert-manager \
73
- --namespace cert-manager \
74
- --create-namespace \
75
- --version v1.12.0 \
76
- --set installCRDs=true \
77
- --set " extraArgs={--feature-gates=ExperimentalGatewayAPISupport=true}"
78
- ```
66
+ ```
67
+
68
+ - Install cert-manager, and enable the GatewayAPI feature gate:
69
+
70
+ ``` shell
71
+ helm install \
72
+ cert-manager jetstack/cert-manager \
73
+ --namespace cert-manager \
74
+ --create-namespace \
75
+ --version v1.12.0 \
76
+ --set installCRDs=true \
77
+ --set " extraArgs={--feature-gates=ExperimentalGatewayAPISupport=true}"
78
+ ```
79
79
80
80
### Step 2 – Create a ClusterIssuer
81
81
0 commit comments