daesung9511 opened a new pull request, #70808:
URL: https://github.com/apache/airflow/pull/70808

   This PR decouples scheduler persistence configuration from
   `workers.celery.persistence` by introducing `scheduler.persistence`.
   
   When `scheduler.persistence.enabled` is explicitly set, the scheduler uses 
its
   own persistence configuration to determine whether it should be rendered as a
   StatefulSet and to configure its PVC.
   
   For backward compatibility, when `scheduler.persistence.enabled` is unset, 
the
   scheduler continues to use `workers.celery.persistence`.
   
   The scheduler Helm tests were updated to cover:
   
   * Backward compatibility with the existing Celery persistence configuration
   * Independence between scheduler and Celery persistence settings
   * Scheduler StatefulSet and Deployment strategies
   * PVC size, annotations, StorageClass, and retention policy
   
   Tested with:
   
   ```bash
   breeze run pytest chart/tests/helm_tests/airflow_core/test_scheduler.py -q
   ```
   
   closes: #70784
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   * [x] Yes 
   
   ---
   
   * Read the **[[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([[AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [[ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x)](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments)](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.


-- 
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]

Reply via email to