Add information for users who ask for requirements #32262
Conversation
boring-cyborg
bot
added
area:Scheduler
potiuk
requested review from
eladkal,
jedcunningham,
dstandish,
uranusjr,
pierrejeambrun and
pankajastro
|
This one is an effort to have a place where we can sand our users when they ask "what are minimum requirements". As there is not an easy answer, I kept on answering various users different variants of the answer "why it is impossible". This is an attempt to make a distilled answer that resonated with many users - they don't realise that in the modern computing and especially when you have complex system like Airflow running on top of multi-layer deployment tooling you cannot just have "min requirements" that you will set in advance - you should approach it differently and this is an attempt to explain it. Comments are welcome! |
This change is based on a number of discussions with the users asking what are the minimum requirements for Airflow to run. While we cannot give precise answer, we should also make the users aware that simple answers are not possible, and that when they are deciding to install airflow and manage it on their own, they also take the responsibility to monitor and adjust the resources they need based on the monitoring they have to run.
potiuk
force-pushed
the
update-requirements-information
branch
from
537b24e
to
17ee7d1
Compare
potiuk
changed the title
|
Thanks @Adaverse -> looking for more inputs/comments. BTW. Maybe there are other ways we can give a helpful advice to our users without explicitly stating requirements (which is impossible). |
| The requirements that Airflow might need depend on many factors, including (but not limited to): | ||
| * The deployment your Airflow is installed with (see above ways of installing Airflow) | ||
| * The requirements of the Deployment environment (for example Kubernetes, Docker, Helm, etc.) that | ||
| are completely independent from Airflow (for example DNS resources, sharing the nodes/resources |
There was a problem hiding this comment.
we're missing to close the ( opened here
Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com>
|
Applied @pankajkoti review |
* Add information for users who ask for requirements This change is based on a number of discussions with the users asking what are the minimum requirements for Airflow to run. While we cannot give precise answer, we should also make the users aware that simple answers are not possible, and that when they are deciding to install airflow and manage it on their own, they also take the responsibility to monitor and adjust the resources they need based on the monitoring they have to run. * Apply suggestions from code review Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> * Update docs/apache-airflow/installation/index.rst --------- Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> (cherry picked from commit f6db66e)
This change is based on a number of discussions with the users asking what are the minimum requirements for Airflow to run.
While we cannot give precise answer, we should also make the users aware that simple answers are not possible, and that when they are deciding to install airflow and manage it on their own, they also take the responsibility to monitor and adjust the resources they need based on the monitoring they have to run.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.