-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Include .Values.volumeMounts into chart/templates/cleanup/cleanup-cronjob.yaml #40191
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
Sure. Feel free to add it. |
I am interested. Could you please assign this to me |
Done |
@sanskrutikhedkar9 are you working on this actively? |
I would like to jump in here and fix this issue alongside with a problem that you are not able to deactivate the job history because the check {{ if .Values.cleanup.successfulJobsHistoryLimit }} is false if I use --set cleanup.successfulJobsHistoryLimit=0 and then the default of k8s (3) is used. Are you fine with this or do you prefer a separate issue here? |
…pache#40191) (apache#42268) * fix(helm): render global volumes and volume mounts in cleanup job (#64056) * fix(helm): allow to deactivate cleanup job history (#64056)
…pache#40191) (apache#42268) * fix(helm): render global volumes and volume mounts in cleanup job (#64056) * fix(helm): allow to deactivate cleanup job history (#64056)
Description
Since all templates supported airflow_config_mount supports Values.volumeMounts (except cleanup-cronjob.yaml)
Is it possible to add Values.volumeMounts support to cleanup-cronjob.yaml as well?
Thank you
Use case/motivation
use custom ConfigMap for airflow_local_settings.py instead of .Values.airflowLocalSettings
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: