JH-A-Kim commented on code in PR #67994: URL: https://github.com/apache/airflow/pull/67994#discussion_r3384344115
########## airflow-core/docs/core-concepts/overview.rst: ########## @@ -92,14 +96,14 @@ All the components are Python applications that can be deployed using various de They can have extra *installed packages* installed in their Python environment. This is useful for example to install custom operators or sensors or extend Airflow functionality with custom plugins. -While Airflow can be run in a single machine and with simple installation where only *scheduler* and -*webserver* are deployed, Airflow is designed to be scalable and secure, and is able to run in a distributed +While Airflow can be run in a single machine and with simple installation where only *scheduler*, *Dag processor* and +*API server* are deployed, Airflow is designed to be scalable and secure, and is able to run in a distributed environment - where various components can run on different machines, with different security perimeters and can be scaled by running multiple instances of the components above. The separation of components also allow for increased security, by isolating the components from each other and by allowing to perform different tasks. For example separating *Dag processor* from *scheduler* -allows to make sure that the *scheduler* does not have access to the *Dag files* and cannot execute +in Airflow 3 makes sure that the *scheduler* does not have access to the *Dag bundles* and cannot execute Review Comment: Thanks for the help! I made a change to the wording in 7d3c8b46e3cbe36496f113103d930224a390a05c Thank you! -- 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]
