Skip to content

Update ingress-controller-elastic-kubernetes-services.md #503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 4, 2025
Merged

Update ingress-controller-elastic-kubernetes-services.md #503

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
847cade
Update ingress-controller-elastic-kubernetes-services.md
apgordon312 May 4, 2025
b6cc5ec
Merge branch 'main' into patch-8
mjang May 4, 2025
8d63c61
Merge branch 'main' into patch-8
mjang May 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions ...nt-guides/amazon-web-services/ingress-controller-elastic-kubernetes-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The `PREFIX` argument specifies the repo name in your private container registry


<span id="amazon-eks"></span>
## Creating an Amazon EKS Cluster
## Create an Amazon EKS Cluster
You can create an Amazon EKS cluster with:
- the AWS Management Console
- the AWS CLI
Expand All @@ -46,7 +46,7 @@ This guide covers the `eksctl` command as it is the simplest option.
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.

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

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

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

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

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.

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

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).

### Configuring a `LoadBalancer` Service to Use NLB
### Configure a `LoadBalancer` Service to Use NLB

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

```shell
kubectl apply -f deployments/service/loadbalancer-aws-elb.yaml
```

### Enabling the PROXY Protocol
### Enable the PROXY Protocol

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

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


<span id="appendix"></span>
## Appendix: Disabling the PROXY Protocol
## Appendix: Disable the PROXY Protocol

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

Expand Down
Loading