Skip to content

Commit d0a2e1d

Browse files
committed
Fix installation instructions
Remove "optional" from the description of the create a configmap step (1.3). The manifests for the Ingress Controller set -nginx-configmaps argument. That is why step 1.3. is not optional.
1 parent 79d11e7 commit d0a2e1d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Make sure you have access to the Ingress controller image:
99

1010
The installation manifests are located in the [deployments](../deployments) folder. In the steps below we assume that you will be running the commands from that folder.
1111

12-
## 1. Create a Namespace, a SA and the Default Secret.
12+
## 1. Create a Namespace, a SA, the Default Secret and the Customization Config Map.
1313

1414
1. Create a namespace and a service account for the Ingress controller:
1515
```
@@ -24,7 +24,7 @@ The installation manifests are located in the [deployments](../deployments) fold
2424
2525
**Note**: The default server returns the Not Found page with the 404 status code for all requests for domains for which there are no Ingress rules defined. For testing purposes we include a self-signed certificate and key that we generated. However, we recommend that you use your own certificate and key.
2626
27-
1. *Optional*. Create a config map for customizing NGINX configuration (read more about customization [here](../examples/customization)):
27+
1. Create a config map for customizing NGINX configuration (read more about customization [here](../examples/customization)):
2828
```
2929
$ kubectl apply -f common/nginx-config.yaml
3030
```

0 commit comments

Comments
 (0)