Skip to content

Commit 6633e49

Browse files
apgordon312mjang
andauthored
Update ingress-controller-elastic-kubernetes-services.md (#503)
Removed gerunds from headings. Co-authored-by: Mike Jang <[email protected]>
1 parent 128c678 commit 6633e49

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/nginx/deployment-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The `PREFIX` argument specifies the repo name in your private container registry
3333

3434

3535
<span id="amazon-eks"></span>
36-
## Creating an Amazon EKS Cluster
36+
## Create an Amazon EKS Cluster
3737
You can create an Amazon EKS cluster with:
3838
- the AWS Management Console
3939
- the AWS CLI
@@ -46,7 +46,7 @@ This guide covers the `eksctl` command as it is the simplest option.
4646
2. Create an Amazon EKS cluster by following the instructions in the [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html). Select the <span style="white-space: nowrap; font-weight:bold;">Managed nodes – Linux</span> option for each step. Note that the <span style="white-space: nowrap;">`eksctl create cluster`</span> command in the first step can take ten minutes or more.
4747

4848
<span id="amazon-ecr"></span>
49-
## Pushing the NGINX Plus Ingress Controller Image to AWS ECR
49+
## Push the NGINX Plus Ingress Controller Image to AWS ECR
5050

5151
This step is only required if you do not plan to use the prebuilt NGINX Open Source image.
5252

@@ -81,7 +81,7 @@ This step is only required if you do not plan to use the prebuilt NGINX Open Sou
8181
```
8282

8383
<span id="ingress-controller"></span>
84-
## Installing the NGINX Plus Ingress Controller
84+
## Install the NGINX Plus Ingress Controller
8585

8686
Use [our documentation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/) to install the NGINX Plus Ingress Controller in your Amazon EKS cluster.
8787

@@ -97,15 +97,15 @@ You need a Kubernetes `LoadBalancer` service to route traffic to the NGINX Ingre
9797

9898
We also recommend enabling the PROXY Protocol for both the NGINX Plus Ingress Controller and your NLB target groups. This is used to forward client connection information. If you choose not to enable the PROXY protocol, see the [Appendix](#appendix).
9999

100-
### Configuring a `LoadBalancer` Service to Use NLB
100+
### Configure a `LoadBalancer` Service to Use NLB
101101

102102
Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `LoadBalancer` of type NLB:
103103

104104
```shell
105105
kubectl apply -f deployments/service/loadbalancer-aws-elb.yaml
106106
```
107107

108-
### Enabling the PROXY Protocol
108+
### Enable the PROXY Protocol
109109

110110
1. Add the following keys to the `deployments/common/nginx-config.yaml` config map file:
111111

@@ -158,7 +158,7 @@ Apply the manifest `deployments/service/loadbalancer-aws-elb.yaml` to create a `
158158

159159

160160
<span id="appendix"></span>
161-
## Appendix: Disabling the PROXY Protocol
161+
## Appendix: Disable the PROXY Protocol
162162

163163
If you want to disable the PROXY Protocol, perform these steps.
164164

0 commit comments

Comments
 (0)