The GitHub Actions job "Tests" on airflow.git/backport-8fc2467-v3-2-test has 
failed.
Run started by GitHub user jscheffl (triggered by jscheffl).

Head commit for run:
58d74f22f3b9296841cb5ec1105f33db83918a10 / André Ahlert <[email protected]>
[v3-2-test] Docs: Expand Helm Chart upgrade tasks in Airflow 3 migration guide 
(#66118)

* Docs: Expand Helm Chart upgrade tasks in Airflow 3 migration guide

Replace the two-line Helm Chart note in the Airflow 3 migration guide
with a dedicated subsection that lists the concrete action items for
upgrading the official chart from Airflow 2.x to 3.x: webserver to
apiServer rename with a values.yaml before/after, secret_key relocation,
jwtSecretName, the standalone dagProcessor deployment, FabAuthManager
default, webserver_config.py rework, minimum Kubernetes 1.30, the DB
migration job, and a pointer to the chart release notes for renamed and
removed keys.

Signed-off-by: André Ahlert <[email protected]>

* Move Helm Chart upgrade tasks to chart/docs

Address review from @Miretpl: chart-specific upgrade content belongs
under chart/docs, mirroring the providers/fab/docs/upgrading.rst pattern
where each component owns its upgrade guide and the core migration guide
links to it.

Move the expanded Helm Chart upgrade checklist from
airflow-core/docs/installation/upgrading_to_airflow3.rst to a new
chart/docs/upgrading-to-airflow-3.rst, restore the original two-line
note in the core guide, and add a pointer to the chart doc from the
core guide. Register the new file in chart/docs/index.rst under Guides.

Signed-off-by: André Ahlert <[email protected]>

---------
(cherry picked from commit 8fc246721e5f348c43e8c3176d06aad9ead18f2e)

Co-authored-by: André Ahlert <[email protected]>
Signed-off-by: André Ahlert <[email protected]>

Report URL: https://github.com/apache/airflow/actions/runs/25249012781

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to