Chart Postgres:15.4.1 and airflow default version description: 2.9.1 update

[dirrao]

Chart Postgres:16.3.0 and airflow default version description: 2.9.1 update

[potiuk]

I am not sure we want to change Postgres version "like that" without more serious testing and consideration and likely resulting in a significant note.

There are certain consequences of changing Postgres version. In the past we had the case where changing Postgres version - see https://github.com/apache/airflow/blob/main/chart/RELEASE_NOTES.rst#airflow-helm-chart-1120-2024-02-11

It would be great if testing of the scenario is performed and in case (which I believe it will be happening again) manual migration is neded we need to mention that in in a significant newsfragment - so that it lands in the relase notes: (https://github.com/apache/airflow/tree/main/chart/newsfragments)

While using embedded Postgres is not recommended for "production" - we know a number of our users actually rely on it for various purposes - including development and testing, and while we do not aim to keep automated migration and backwards-compatibility, some way of warning them is necessary in case the migration requires some manual step.

[dirrao]

I am not sure we want to change Postgres version "like that" without more serious testing and consideration and likely resulting in a significant note.

There are certain consequences of changing Postgres version. In the past we had the case where changing Postgres version - see https://github.com/apache/airflow/blob/main/chart/RELEASE_NOTES.rst#airflow-helm-chart-1120-2024-02-11

It would be great if testing of the scenario is performed and in case (which I believe it will be happening again) manual migration is neded we need to mention that in in a significant newsfragment - so that it lands in the relase notes: (https://github.com/apache/airflow/tree/main/chart/newsfragments)

While using embedded Postgres is not recommended for "production" - we know a number of our users actually rely on it for various purposes - including development and testing, and while we do not aim to keep automated migration and backwards-compatibility, some way of warning them is necessary in case the migration requires some manual step.

Thanks. We have been using the Postgres 16. we haven't faced any issues during the upgrade from 13 to 16. However, we are using external Postgres. I will test it and update the documentation.

[jedcunningham]

This will be done during the next release anyways, that's why it isn't done in those Airflow version bump PRs.

Said another way, this is just a different representation of the changelog for chart version 1.13.0.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.