potiuk commented on issue #20999: URL: https://github.com/apache/airflow/issues/20999#issuecomment-1377127169
I think - it is REALLY useful to have redis managed internally same as postgres. We already have a huge problem with having to manage many things outside of the chart to be able to run and test airflow in a simple way with celery. Having an easy way where both Redis and Postgres are run inside Airflow Chart is the best way (and should be the default) so that you can do ``` helm install apache/airflow ``` and get it working. Without any extra setup. If anything is needed here, is possibly - similarly as in case of Postgres, clearly document and possibly even raise a warnign that using internal redis is meant to be used for quick start only and if you want to handle more "production" ready setup and include things like rotating passwords etc., you should configure your own redis externally. This is mostly a documentation and possibly warning change - nothing to change in the basic flag behaviour. @sudeepgupta90 - maybe you can create such PR with doc change, and possibly adding a warning. As someone who was mislead by thinking you should not use external redis, you are probably the best person to asses where as a user you would look for such an information and what warning wording would be best for people like you to make them aware that the basic setup is not handling all "production" cases. It's super easy - go to our docs and choose "Suggest a change on this page" - and you wil get a PR where you will be able to update the docs. (and adding warning could be a follow - up maybe). WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
