You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "deema-k (via GitHub)" <gi...@apache.org> on 2026/01/11 12:28:37 UTC
[D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
GitHub user deema-k created a discussion: Database cleanup configuration not exposed in Helm chart 1.18.0
I noticed that PR #58707 (https://github.com/apache/airflow/pull/58707) introduces support for a new value related to database/log cleanup (merged into Airflow main), however this value does not exist yet in the Helm chart 1.18.0 values.yaml.
current setup version :
Airflow version: 3.0.2
Helm chart version: 1.18.0
Is there a newer Helm chart version planned that will expose this value?
GitHub link: https://github.com/apache/airflow/discussions/60388
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "de-code (via GitHub)" <gi...@apache.org>.
GitHub user de-code closed the discussion with a comment: Database cleanup configuration not exposed in Helm chart 1.18.0
@potiuk I can certainly try to help. I don't anything about the devlist thread.
I just don't find the tone very friendly. I was looking for a new release of the Helm chart and found this issue / discussion raised by someone else. It was closed and I just wanted to be helpful to those that might also stumble across it.
GitHub link: https://github.com/apache/airflow/discussions/60388#discussioncomment-15707177
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk closed the discussion with a comment: Database cleanup configuration not exposed in Helm chart 1.18.0
Sure. I understand. And again - if you want to make it faster, help.
GitHub link: https://github.com/apache/airflow/discussions/60388#discussioncomment-15717648
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "deema-k (via GitHub)" <gi...@apache.org>.
GitHub user deema-k closed a discussion: Database cleanup configuration not exposed in Helm chart 1.18.0
I noticed that PR #58707 (https://github.com/apache/airflow/pull/58707) introduces support for a new value related to database/log cleanup (merged into Airflow main), however this value does not exist yet in the Helm chart 1.18.0 values.yaml.
current setup version :
Airflow version: 3.0.2
Helm chart version: 1.18.0
Is there a newer Helm chart version planned that will expose this value?
GitHub link: https://github.com/apache/airflow/discussions/60388
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "de-code (via GitHub)" <gi...@apache.org>.
GitHub user de-code closed the discussion with a comment: Database cleanup configuration not exposed in Helm chart 1.18.0
There still doesn't seem to be a helm chart release after 1.18.0 but there are release candidate tags:
* [helm-chart/1.19.0rc1](https://github.com/apache/airflow/releases/tag/helm-chart/1.19.0rc1)
* [helm-chart/1.19.0rc2](https://github.com/apache/airflow/releases/tag/helm-chart/1.19.0rc2)
GitHub link: https://github.com/apache/airflow/discussions/60388#discussioncomment-15705086
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk closed the discussion with a comment: Database cleanup configuration not exposed in Helm chart 1.18.0
Yes I am sometimes very direct when it comes to responding - but you got the link where you can sew the progress (what you wanted) and the way how you can make it faster. Maybe it was indeed very direct and not friendly in the sense of directly answering the question - but the truth is that the current status is 'testing by people like you who want it's and if your goal is to get it faster - doing it i(i.e testing) and providing feedback is best you can do. Sorry if you were put off by this, but we often get people who expect/demand things to happen mostly from volunteers for the software they get for free- when they contribute nothibg. That makes some of our answers seem quite harsh.
GitHub link: https://github.com/apache/airflow/discussions/60388#discussioncomment-15717708
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Database cleanup configuration not exposed in Helm chart 1.18.0 [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk closed the discussion with a comment: Database cleanup configuration not exposed in Helm chart 1.18.0
Yes. There is a devlist thread about it and ask to test it it in GitHub issues https://github.com/apache/airflow/issues/61268 - did you actually took it for a spin and tested it and provided feedback as we asked? I have not seen you being involved @de-code ? Maybe good time to do so?
Also there seem to be a patch that fixes last issue in 1.19.0rc2 https://github.com/apache/airflow/pull/61371 and you can definitely help by testing it and commenting if it work.
Generally, we cannot release something if there are no users who will be involved and test RCs and the fastest thing to help is to get involved and test.
Can we count on your help please @de-code ? Or you think that just commenting that "still" things did not happen makes it faster? I think actually testing and contributing is a far more efficient way to make the release happen.
GitHub link: https://github.com/apache/airflow/discussions/60388#discussioncomment-15706813
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org