Aws-load-balancer-controller: How to config CORS with ALB?

Created on 26 Aug 2019 · 12Comments · Source: kubernetes-sigs/aws-load-balancer-controller

How to config CORS with ALB?
Like nginx ingress annotations. "nginx.ingress.kubernetes.io/enable-cors"

Source

anemptyair

👍12 😕4

Most helpful comment

Wondering why its closed? Isn't it a good thing to have CORS on ALB instead of putting it on every server?

lightsaway on 19 Mar 2020

👍7

All 12 comments

Same issue/question here! I think adding AWS "API Gateway" in front is a bad idea...

tspycher on 18 Sep 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 17 Dec 2019

Same issue here: tried with nginx's enable-cors annotation, with no luck! Is there another way to enable CORS on ALB?

log2 on 20 Dec 2019

has anyone find an way around or aws is going to provide a fix in future ?

thestrid3r on 16 Jan 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 15 Feb 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 16 Mar 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot on 16 Mar 2020

Wondering why its closed? Isn't it a good thing to have CORS on ALB instead of putting it on every server?

lightsaway on 19 Mar 2020

👍7

Why they are trying to close the issue without the answer.Thats not the way around to do the work.Btw facing the same issue :( .

saharanrenu on 10 May 2020

Also interested in keeping this open. Just hit this in our account and wondering if I will have to move us towards nginx ingress controller.

/remove-lifecycle rotten
/reopen

@anemptyair you may have to /reopen I tried but got denied by the bot :)

dailyherold on 29 May 2020

@dailyherold: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

k8s-ci-robot on 29 May 2020

ALB itself doesn't natively support CORS, therefore, CORS headers need to be added by the backend application. ALB just forwards CORS requests to the back-end application as well as forwards CORS responses to the clients.

Nginx's ingress controller does have a native support for adding CORS headers which works completely fine with ALB/CLB. https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#enable-cors