Skip to content

Commit 1f17269

Browse files
committed
Final review feedback
1 parent 8501eae commit 1f17269

File tree

2 files changed

+18
-18
lines changed

2 files changed

+18
-18
lines changed

docs/guides/integrating-cert-manager.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This guide will demonstrate how to:
1515

1616
## Prerequisities
1717

18-
1. Administrator access to a Kubernetes cluster is required.
18+
1. Administrator access to a Kubernetes cluster.
1919
2. [Helm](https://helm.sh) and [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) must be installed locally.
2020
3. Deploy NGINX Kubernetes Gateway (NKG) following the [deployment instructions](/docs/installation.md).
2121
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:
4444
that is referenced by the Gateway resource. As a result, NGINX is configured to terminate HTTPS traffic from clients
4545
using this signed keypair.
4646
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
4848
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
5050
and the communication is secured using the signed keypair contained in the cafe-secret Secret.
5151
7. The certificate will be automatically renewed when it is close to expiry, the Secret will be updated using the new
5252
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:
5858

5959
The first step is to deploy cert-manager onto the cluster.
6060

61-
1. Add the Helm repository
61+
- Add the Helm repository.
6262

63-
```shell
63+
```shell
6464
helm repo add jetstack https://charts.jetstack.io
6565
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+
```
7979

8080
### Step 2 – Create a ClusterIssuer
8181

-1.38 KB
Loading

0 commit comments

Comments
 (0)