From f00da064eab8cb202e19498aa95a75b49b9e1c48 Mon Sep 17 00:00:00 2001 From: claudenm Date: Mon, 5 Mar 2018 15:53:32 -0500 Subject: [PATCH 1/3] AWS_MAX_RETRIES is a string, not a numeric --- examples/alb-ingress-controller.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/alb-ingress-controller.yaml b/examples/alb-ingress-controller.yaml index 60dbcace8..441fb15be 100644 --- a/examples/alb-ingress-controller.yaml +++ b/examples/alb-ingress-controller.yaml @@ -71,7 +71,7 @@ spec: # Maximum number of times to retry the aws calls. # defaults to 20. - name: AWS_MAX_RETRIES - value: 20 + value: "20" - name: POD_NAME valueFrom: fieldRef: From 64d932bdecff5494a009c74e51155302d74f6d3c Mon Sep 17 00:00:00 2001 From: claudenm Date: Mon, 5 Mar 2018 16:00:01 -0500 Subject: [PATCH 2/3] Clarify the number of subnets necessary to launch an ALB. --- docs/walkthrough.md | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/docs/walkthrough.md b/docs/walkthrough.md index e803d4ea4..1f4c2ab57 100755 --- a/docs/walkthrough.md +++ b/docs/walkthrough.md @@ -108,16 +108,26 @@ In this example, you'll wget https://raw.githubusercontent.com/coreos/alb-ingress-controller/master/examples/echoservice/echoserver-ingress.yaml ``` -1. Alter the host field to a domain that you own in Route 53 +1. Edit the alb.ingress.kubernetes.io/subnets annotation to include at least two subnets. If you'd like to use external dns, alter the host field to a domain that you own in Route 53. Assuming you managed `example.com` in Route 53. ```yaml - spec: - rules: - - host: echoserver.example.com - http: - paths: + apiVersion: extensions/v1beta1 + kind: Ingress + metadata: + name: echoserver + namespace: echoserver + annotations: + alb.ingress.kubernetes.io/scheme: internet-facing + alb.ingress.kubernetes.io/subnets: subnet-1, subnet-2 + alb.ingress.kubernetes.io/security-groups: sg-1 + alb.ingress.kubernetes.io/tags: Environment=dev,Team=test + spec: + rules: + - host: echoserver.example.com + http: + paths: ``` 1. Add tags to subnets where ALBs should be deployed. From a66eeeb13d37c2288f3eeadae3be67d7ef8f5dce Mon Sep 17 00:00:00 2001 From: claudenm Date: Mon, 5 Mar 2018 16:05:24 -0500 Subject: [PATCH 3/3] Security group note --- docs/walkthrough.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/walkthrough.md b/docs/walkthrough.md index 1f4c2ab57..4ab8580ab 100755 --- a/docs/walkthrough.md +++ b/docs/walkthrough.md @@ -31,7 +31,7 @@ In this example, you'll value: us-west-1 ``` - - `CLUSTER_NAME`: name of the cluster. + - `CLUSTER_NAME`: name of the cluster. ```yaml - name: CLUSTER_NAME @@ -108,9 +108,7 @@ In this example, you'll wget https://raw.githubusercontent.com/coreos/alb-ingress-controller/master/examples/echoservice/echoserver-ingress.yaml ``` -1. Edit the alb.ingress.kubernetes.io/subnets annotation to include at least two subnets. If you'd like to use external dns, alter the host field to a domain that you own in Route 53. - - Assuming you managed `example.com` in Route 53. +1. Edit the alb.ingress.kubernetes.io/subnets annotation to include at least two subnets. If you'd like to use external dns, alter the host field to a domain that you own in Route 53. Assuming you managed `example.com` in Route 53. *Note:* The security group you specify must have public http access on port 80. ```yaml apiVersion: extensions/v1beta1