Skip to content
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

allow gunicorn config to be passed to airflow webserver #7961

Closed
dimberman opened this issue Mar 29, 2020 · 0 comments
Closed

allow gunicorn config to be passed to airflow webserver #7961

dimberman opened this issue Mar 29, 2020 · 0 comments

Comments

@dimberman
Copy link
Contributor

Ticket was created 14/Oct/16 22:48

Description

I have run into an issue when running airflow webserver behind a load balancer where redirects result in https requests forwarded to http. I ran into a similar issue with Caravel which also uses gunicorn. apache/superset#978 From that issue:

When gunicorn is run on a different machine from the load balancer (nginx or ELB), it needs to be told explicitly to trust the X-Forwarded-* headers sent. gunicorn takes an option --forwarded-allow-ips which can either be a comma separated list of ip addresses, or "*" to trust all.

I don't see a simple way to inject custom arguments to the gunicorn call in webserver(). Rather than making a special case to set --forwarded-allow-ips, it would be nice if the caller of airflow webserver could pass an additional gunicorn config file.

The call to gunicorn is already including a -c and I'm not sure gunicorn will take multiple configs, so maybe we have to parse the config and include each name=value on the gunicorn command line. Any suggestions on how best to allow this?

Use case / motivation

Related Issues

Moved here from https://issues.apache.org/jira/browse/AIRFLOW-571

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant