We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#111 added support for aggregating ingresses with different Certificates under a single ALB using SNI.
Some clients might not support SNI and thus we should support opting out of an SNI ALB and create an a single ALB per certificate like before.
I suggest we do this with an annotation on the ingress object.
Something like:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myingress annotations: zalando.org/aws-load-balancer-sni: false
https://en.wikipedia.org/wiki/Server_Name_Indication
The text was updated successfully, but these errors were encountered:
It might makes sense to opt-out globally per flag, too
Sorry, something went wrong.
Make it possible to get a unique ALB for a single ingress resource
8a8142b
Fix #129
b0b4186
Make it possible to get a unique ALB for a single ingress resource (#133
4b10e08
) * Make it possible to get a unique ALB for a single ingress resource Fix #129 * Few ALBs * Add test for when LB is not shared
No branches or pull requests
#111 added support for aggregating ingresses with different Certificates under a single ALB using SNI.
Some clients might not support SNI and thus we should support opting out of an SNI ALB and create an a single ALB per certificate like before.
I suggest we do this with an annotation on the ingress object.
Something like:
https://en.wikipedia.org/wiki/Server_Name_Indication
The text was updated successfully, but these errors were encountered: