Jed Cunningham

Yes you could, you'd just add extra `extraInitContainers` and `extraContainers`. The `extraVolumes` portion would only need to be done once. The example on the readme (which it looks like you...

Hi @Maksimov-Dmitry, sorry for the slow reply. Our 2.3 images will only ever have a bullseye image. There are no plans to offer one for buster. If this causes you...

I just realized you may have just updated the version number in your dockerfile and you may not actually care about the distribution. 2.3 no longer has the distribution in...

Do we want the version check here, or still in a separate package? I lean toward separate to keep things simple?

@ephraimbuddy, can we resurrect this for 2.3.4 and 2.4.1?

Yes, we should. @mabrikan, can you expand this test to cover the pull policy also? Thanks! https://github.com/apache/airflow/blob/52560b87c991c9739791ca8419219b0d86debacd/tests/charts/test_pod_template_file.py#L281-L290

Instead of adding a column solely for the purposes of cleaning, we should consider not directly cleaning RTIF and letting the cascading FK on TI do the work for us.

There is already that behavior if you only choose to clear TI - RTIF is dependent on the TI existing already. The removal of execution_date/the transition to the TI FK...

Sorry, I'm advocating for removing RTIF as an option altogether and if you run `airflow db clean -t rendered_task_instance_fields` you get a warning like this instead: ``` WARNING - Sorry,...

I think just removing [this line](https://github.com/apache/airflow/blob/55d11464c047d2e74f34cdde75d90b633a231df2/airflow/utils/db_cleanup.py#L100)? A quick look makes me think everything else (e.g. help text) is okay as is because it's dynamically generated.