-
Notifications
You must be signed in to change notification settings - Fork 14k
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
added labels to airflow specific pods #25031
added labels to airflow specific pods #25031
Conversation
…:rishkarajgi/airflow into feature/support-labels-per-component-mod
@jedcunningham - pls see if this can be merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Component specific labels should go on all objects, not just pods, like the global labels do. Also there are merge conflicts currently.
…:rishkarajgi/airflow into feature/support-labels-per-component-mod
@jedcunningham Have addressed the above. Please take a look |
…:rishkarajgi/airflow into feature/support-labels-per-component-mod
…:rishkarajgi/airflow into feature/support-labels-per-component-mod
Adds the ability to inject additional labels to specific components. This currently supports addition to scheduler, webserver, worker, pod template, triggerer, flower, cleanup and create user job.
^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.