-
Notifications
You must be signed in to change notification settings - Fork 84
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.
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
Make it possible to get a unique ALB for a single ingress resource #133
Conversation
README.md
Outdated
@@ -241,6 +241,11 @@ spec: | |||
|
|||
You can only select from `internet-facing` (default) and `internal` options. | |||
|
|||
By default the ingress-controller will aggregate all ingresses under a single |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
single? if you have more than 25 you have 2 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changed it to "as few as possible" :)
kubernetes/adapter_test.go
Outdated
@@ -18,6 +18,7 @@ func TestMappingRoundtrip(t *testing.T) { | |||
hostName: "bar", | |||
scheme: "internal", | |||
certificateARN: "zbr", | |||
shared: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to have also a test case that shows that shared: false works
👍 |
1 similar comment
👍 |
This adds an annotation
zalando.org/aws-load-balancer-shared: "false"
which, when set will make sure to provision an ALB that is unique for a single ingress resources. This is useful if a single application in the cluster has clients which doesn't support SNI or if it's getting so much traffic that it should not share the ALB with other applications.It works by having a
ingress:owner=<namespace>/<ingress-name>
tag on the stacks which are reserved for a single ingress. If the annotation is later removed from the ingress the stacks will be re-aggregated.Fix #129