From 6260d6b89ec99ea64ac122589ac3183728429091 Mon Sep 17 00:00:00 2001 From: Zara Gebru Date: Thu, 22 Feb 2018 21:07:30 +0100 Subject: [PATCH] [readme] use right aws yaml to create loadbalancer --- docs/installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/installation.md b/docs/installation.md index 97beef7be8..0ade7735b1 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -109,7 +109,7 @@ Create a service using a manifest for your cloud provider: ``` * For AWS, run: ``` - $ kubectl apply -f service/loadbalancer-aws.yaml + $ kubectl apply -f service/loadbalancer-aws-elb.yaml ``` Kubernetes will allocate a Classic Load Balancer (ELB) in TCP mode with the PROXY protocol enabled to pass the client's information (the IP address and the port). NGINX must be configured to use the PROXY protocol: * Add the following keys to the config map file `nginx-config.yaml` from the Step 1 : @@ -154,4 +154,4 @@ For NGINX Plus, you can access the live activity monitoring dashboard: Delete the `nginx-ingress` namespace to uninstall the Ingress controller along with all the auxiliary resources that were created: ``` $ kubectl delete namespace nginx-ingress -``` \ No newline at end of file +```