jedcunningham opened a new issue, #70784: URL: https://github.com/apache/airflow/issues/70784
### Under which category would you file this issue? Helm chart ### Apache Airflow version main ### What happened and how to reproduce it? I noticed what the logic to determine if a scheduler is a deployment or a statefulset now looks at the `.Values.workers.celery.persistence.enabled `. This used to be the more general `.Values.workers.persistence.enabled`, but now this coupling does not make sense. This was a miss when celery was split out of the general workers section. ### What you think should happen instead? I haven't spent much time thinking about it, but maybe we just need a new `scheduler.persistence` to control it? Or `workers.local.persistence`? Whoever picks this up should explore the possible options. ### Operating System _No response_ ### Deployment Official Apache Airflow Helm Chart ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers _No response_ ### Official Helm Chart version main (development) ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
