GitHub user starkmarkus added a comment to the discussion: storage for tracking rate limits
You are right. This is not exposed in `airflow.cfg`. Airflow’s FAB docs say the limiter is configured in `webserver_config.py`, and the example is `RATELIMIT_STORAGE_URI = "redis://redis_host:6379/0"`. The default in-memory storage is only per webserver/gunicorn process, so it is not shared unless you configure a backend. So the production-ready answer is still: put the limiter storage on a shared backend such as Redis or Valkey. If the Helm chart does not expose a hook for `webserver_config.py` or `RATELIMIT_STORAGE_URI`, that is the missing piece in the deployment setup, not something you overlooked. GitHub link: https://github.com/apache/airflow/discussions/68630#discussioncomment-17334805 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
