You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jscheffl (via GitHub)" <gi...@apache.org> on 2026/03/16 21:37:41 UTC
[PR] Update Helm Chart release notes for 1.20.0 [airflow]
jscheffl opened a new pull request, #63759:
URL: https://github.com/apache/airflow/pull/63759
Update release notes for upcoming Helm Chart release 1.20.0
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR, please
change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update Helm Chart release notes for 1.20.0 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on code in PR #63759:
URL: https://github.com/apache/airflow/pull/63759#discussion_r2943397200
##########
chart/RELEASE_NOTES.rst:
##########
@@ -23,6 +23,144 @@ Run ``helm repo update`` before upgrading the chart to the latest version.
.. towncrier release notes start
+Airflow Helm Chart 1.20.0 (2026-03-16)
+--------------------------------------
+
+Significant Changes
+^^^^^^^^^^^^^^^^^^^
+
+Support for old versions of Apache Airflow <2.11 has been dropped (#61018)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+Minimum supported version of Apache Airflow is now 2.11.0. If you want to deploy an
+old version of Apache Airflow, please use the last released version of the chart 1.19.0.
+
+Parameters moved to related workers section
+"""""""""""""""""""""""""""""""""""""""""""
+
+* ``workers.podDisruptionBudget`` section is now deprecated in favor of ``workers.celery.podDisruptionBudget``. Please update your configuration accordingly. (#61414)
+* ``workers.keda`` section is now deprecated in favor of ``workers.celery.keda``. Please update your configuration accordingly. (#61820)
+* ``workers.resources`` section is now deprecated in favor of ``workers.celery.resources`` and ``workers.kubernetes.resources``. Please update your configuration accordingly. (#61890)
+
+
+As Git-Sync is not service-type object, the readiness probe will be removed. (#62334)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``. Section itself will be removed in future release as to not break setups during upgrades.
+
+As Git-Sync has dedicated liveness service, the liveness probe behaviour will be changed. To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``.
+
+Please update your configuration accordingly.
+
+
+Automatic ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` and ``AIRFLOW__KUBERNETES_SECRETS__`` prefix addition removed from ``container_extra_envs`` and ``custom_airflow_environment`` (#60750)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The automatic prefix addition for Kubernetes Executor environment variables and secrets has been removed from both the ``container_extra_envs`` and ``custom_airflow_environment`` helper functions.
+
+**What changed:**
+
+Previously, when you added environment variables to component-specific configurations (e.g., ``.Values.scheduler.env``, ``.Values.workers.env``, ``.Values.apiServer.env``, ``.Values.dagProcessor.env``), the chart automatically created an additional environment variable with the ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` prefix for Kubernetes Executor worker pods.
+
+**Example - Before:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+This would automatically create both:
+* ``MY_VAR=my_value`` (for the apiServer)
+* ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR=my_value`` (for worker pods)
+
+**Example - After:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+Now only ``MY_VAR=my_value`` is created for the apiServer. The ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR`` is **no longer automatically created**.
+
+**Why this change:**
+
+* **Prevent Unintended Exposure of Sensitive Data**: Sensitive information (e.g., ``client_secret``) that should be securely handled via ``secretKeyRef`` for specific components was being automatically prefixed with ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__``. This prefixing causes these variables to be recognized as part of Airflow's internal configuration, leading to their unintended exposure in the Airflow Web UI (under Admin -> Configuration), even when ``AIRFLOW__API__EXPOSE_CONFIG`` is set to ``non-sensitive-only``.
+
+* **Avoid Unintended Environment Propagation to Workers**: Component-specific env configurations are intended strictly for specific components. However, the previous behavior caused these variables to be inadvertently passed to worker pods, which may result in unintended configuration conflicts and unexpected side effects.
+
+**Migration Required:**
+
+If you need to pass environment variables specifically to Kubernetes Executor worker pods, use one of the following approaches:
+
+**Option 1: Use ``.Values.env``**
+.. code-block:: yaml
+
+ env:
+ - name: my_var
+ value: "my_value"
+
+Environment variables in ``.Values.env`` are now passed as-is without the automatic prefix (same behavior as component-specific env).
+
+**Option 2: Use ``.Values.config.kubernetes_environment_variables``**
+.. code-block:: yaml
+
+ config:
+ kubernetes_environment_variables:
+ my_var: "my_value"
+
+**Secrets (``.Values.secret``):** The ``AIRFLOW__KUBERNETES_SECRETS__`` prefix is no longer automatically added. Secrets are now passed as-is via ``secretKeyRef`` without the prefixed copy for worker pods.
+
+Default Airflow image is updated to ``3.1.8`` (#63392)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The default Airflow image that is used with the Chart is now ``3.1.8``, previously it was ``3.1.7``.
+
+
+Features
+^^^^^^^^
+
+- Support Helm template expressions in ``podAnnotations`` and ``airflowPodAnnotations`` values. (#63019)
+- Add minute-level log retention to clean-logs script (#61855)
+- Add LOG_MAX_SIZE environment variables to log groomer (#61559)
+
+Improvements
+^^^^^^^^^^^^
+
+- Remove automatic ``KUBERNETES_ENVIRONMENT_VARIABLES`` and ``KUBERNETES_SECRETS`` prefixes from chart helpers (#60750)
+- Remove JWT secrets from triggerer, worker and dag-processor (#63204)
+- Add workers.celery.nodeSelector & workers.kubernetes.nodeSelector (#61957)
+- Add workers.celery.terminationGracePeriodSeconds & workers.kubernetes.terminationGracePeriodSeconds (#61892)
+- Add workers.celery.resources & workers.kubernetes.resources (#61890)
+- Add workers.celery.keda section (#61820)
+- Add workers.celery.podDisruptionBudget (#61414)
+- Add workers.celery.containerLifecycleHooks & workers.kubernetes.containerLifecycleHooks (#61369)
+- Refactor Git-Sync livenessProbe & deprecate readinessProbe & add startupProbe (#62334)
+- Default airflow version to 3.1.8 (#63392)
+- Drop support for all Airflow versions below 2.11 in Helm Chart (#61018)
+- Support Helm template expressions in podAnnotations (#63019)
+- Warn on deprecated per-component securityContext values (#62729)
+
+Bug Fixes
+^^^^^^^^^
+
+- Add ``*.iml`` to .gitignore in all distributions (#63636)
Review Comment:
Better now? :-D (All non user facing going to Misc?)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update Helm Chart release notes for 1.20.0 [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on code in PR #63759:
URL: https://github.com/apache/airflow/pull/63759#discussion_r2943397200
##########
chart/RELEASE_NOTES.rst:
##########
@@ -23,6 +23,144 @@ Run ``helm repo update`` before upgrading the chart to the latest version.
.. towncrier release notes start
+Airflow Helm Chart 1.20.0 (2026-03-16)
+--------------------------------------
+
+Significant Changes
+^^^^^^^^^^^^^^^^^^^
+
+Support for old versions of Apache Airflow <2.11 has been dropped (#61018)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+Minimum supported version of Apache Airflow is now 2.11.0. If you want to deploy an
+old version of Apache Airflow, please use the last released version of the chart 1.19.0.
+
+Parameters moved to related workers section
+"""""""""""""""""""""""""""""""""""""""""""
+
+* ``workers.podDisruptionBudget`` section is now deprecated in favor of ``workers.celery.podDisruptionBudget``. Please update your configuration accordingly. (#61414)
+* ``workers.keda`` section is now deprecated in favor of ``workers.celery.keda``. Please update your configuration accordingly. (#61820)
+* ``workers.resources`` section is now deprecated in favor of ``workers.celery.resources`` and ``workers.kubernetes.resources``. Please update your configuration accordingly. (#61890)
+
+
+As Git-Sync is not service-type object, the readiness probe will be removed. (#62334)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``. Section itself will be removed in future release as to not break setups during upgrades.
+
+As Git-Sync has dedicated liveness service, the liveness probe behaviour will be changed. To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``.
+
+Please update your configuration accordingly.
+
+
+Automatic ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` and ``AIRFLOW__KUBERNETES_SECRETS__`` prefix addition removed from ``container_extra_envs`` and ``custom_airflow_environment`` (#60750)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The automatic prefix addition for Kubernetes Executor environment variables and secrets has been removed from both the ``container_extra_envs`` and ``custom_airflow_environment`` helper functions.
+
+**What changed:**
+
+Previously, when you added environment variables to component-specific configurations (e.g., ``.Values.scheduler.env``, ``.Values.workers.env``, ``.Values.apiServer.env``, ``.Values.dagProcessor.env``), the chart automatically created an additional environment variable with the ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` prefix for Kubernetes Executor worker pods.
+
+**Example - Before:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+This would automatically create both:
+* ``MY_VAR=my_value`` (for the apiServer)
+* ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR=my_value`` (for worker pods)
+
+**Example - After:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+Now only ``MY_VAR=my_value`` is created for the apiServer. The ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR`` is **no longer automatically created**.
+
+**Why this change:**
+
+* **Prevent Unintended Exposure of Sensitive Data**: Sensitive information (e.g., ``client_secret``) that should be securely handled via ``secretKeyRef`` for specific components was being automatically prefixed with ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__``. This prefixing causes these variables to be recognized as part of Airflow's internal configuration, leading to their unintended exposure in the Airflow Web UI (under Admin -> Configuration), even when ``AIRFLOW__API__EXPOSE_CONFIG`` is set to ``non-sensitive-only``.
+
+* **Avoid Unintended Environment Propagation to Workers**: Component-specific env configurations are intended strictly for specific components. However, the previous behavior caused these variables to be inadvertently passed to worker pods, which may result in unintended configuration conflicts and unexpected side effects.
+
+**Migration Required:**
+
+If you need to pass environment variables specifically to Kubernetes Executor worker pods, use one of the following approaches:
+
+**Option 1: Use ``.Values.env``**
+.. code-block:: yaml
+
+ env:
+ - name: my_var
+ value: "my_value"
+
+Environment variables in ``.Values.env`` are now passed as-is without the automatic prefix (same behavior as component-specific env).
+
+**Option 2: Use ``.Values.config.kubernetes_environment_variables``**
+.. code-block:: yaml
+
+ config:
+ kubernetes_environment_variables:
+ my_var: "my_value"
+
+**Secrets (``.Values.secret``):** The ``AIRFLOW__KUBERNETES_SECRETS__`` prefix is no longer automatically added. Secrets are now passed as-is via ``secretKeyRef`` without the prefixed copy for worker pods.
+
+Default Airflow image is updated to ``3.1.8`` (#63392)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The default Airflow image that is used with the Chart is now ``3.1.8``, previously it was ``3.1.7``.
+
+
+Features
+^^^^^^^^
+
+- Support Helm template expressions in ``podAnnotations`` and ``airflowPodAnnotations`` values. (#63019)
+- Add minute-level log retention to clean-logs script (#61855)
+- Add LOG_MAX_SIZE environment variables to log groomer (#61559)
+
+Improvements
+^^^^^^^^^^^^
+
+- Remove automatic ``KUBERNETES_ENVIRONMENT_VARIABLES`` and ``KUBERNETES_SECRETS`` prefixes from chart helpers (#60750)
+- Remove JWT secrets from triggerer, worker and dag-processor (#63204)
+- Add workers.celery.nodeSelector & workers.kubernetes.nodeSelector (#61957)
+- Add workers.celery.terminationGracePeriodSeconds & workers.kubernetes.terminationGracePeriodSeconds (#61892)
+- Add workers.celery.resources & workers.kubernetes.resources (#61890)
+- Add workers.celery.keda section (#61820)
+- Add workers.celery.podDisruptionBudget (#61414)
+- Add workers.celery.containerLifecycleHooks & workers.kubernetes.containerLifecycleHooks (#61369)
+- Refactor Git-Sync livenessProbe & deprecate readinessProbe & add startupProbe (#62334)
+- Default airflow version to 3.1.8 (#63392)
+- Drop support for all Airflow versions below 2.11 in Helm Chart (#61018)
+- Support Helm template expressions in podAnnotations (#63019)
+- Warn on deprecated per-component securityContext values (#62729)
+
+Bug Fixes
+^^^^^^^^^
+
+- Add ``*.iml`` to .gitignore in all distributions (#63636)
Review Comment:
Better now? :-D
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update Helm Chart release notes for 1.20.0 [airflow]
Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal commented on code in PR #63759:
URL: https://github.com/apache/airflow/pull/63759#discussion_r2943236133
##########
chart/RELEASE_NOTES.rst:
##########
@@ -23,6 +23,144 @@ Run ``helm repo update`` before upgrading the chart to the latest version.
.. towncrier release notes start
+Airflow Helm Chart 1.20.0 (2026-03-16)
+--------------------------------------
+
+Significant Changes
+^^^^^^^^^^^^^^^^^^^
+
+Support for old versions of Apache Airflow <2.11 has been dropped (#61018)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+Minimum supported version of Apache Airflow is now 2.11.0. If you want to deploy an
+old version of Apache Airflow, please use the last released version of the chart 1.19.0.
+
+Parameters moved to related workers section
+"""""""""""""""""""""""""""""""""""""""""""
+
+* ``workers.podDisruptionBudget`` section is now deprecated in favor of ``workers.celery.podDisruptionBudget``. Please update your configuration accordingly. (#61414)
+* ``workers.keda`` section is now deprecated in favor of ``workers.celery.keda``. Please update your configuration accordingly. (#61820)
+* ``workers.resources`` section is now deprecated in favor of ``workers.celery.resources`` and ``workers.kubernetes.resources``. Please update your configuration accordingly. (#61890)
+
+
+As Git-Sync is not service-type object, the readiness probe will be removed. (#62334)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``. Section itself will be removed in future release as to not break setups during upgrades.
+
+As Git-Sync has dedicated liveness service, the liveness probe behaviour will be changed. To enable feature behaviour set ``dags.gitSync.recommendedProbeSetting`` to ``true``.
+
+Please update your configuration accordingly.
+
+
+Automatic ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` and ``AIRFLOW__KUBERNETES_SECRETS__`` prefix addition removed from ``container_extra_envs`` and ``custom_airflow_environment`` (#60750)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The automatic prefix addition for Kubernetes Executor environment variables and secrets has been removed from both the ``container_extra_envs`` and ``custom_airflow_environment`` helper functions.
+
+**What changed:**
+
+Previously, when you added environment variables to component-specific configurations (e.g., ``.Values.scheduler.env``, ``.Values.workers.env``, ``.Values.apiServer.env``, ``.Values.dagProcessor.env``), the chart automatically created an additional environment variable with the ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__`` prefix for Kubernetes Executor worker pods.
+
+**Example - Before:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+This would automatically create both:
+* ``MY_VAR=my_value`` (for the apiServer)
+* ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR=my_value`` (for worker pods)
+
+**Example - After:**
+.. code-block:: yaml
+
+ apiServer:
+ env:
+ - name: MY_VAR
+ value: "my_value"
+
+Now only ``MY_VAR=my_value`` is created for the apiServer. The ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__MY_VAR`` is **no longer automatically created**.
+
+**Why this change:**
+
+* **Prevent Unintended Exposure of Sensitive Data**: Sensitive information (e.g., ``client_secret``) that should be securely handled via ``secretKeyRef`` for specific components was being automatically prefixed with ``AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__``. This prefixing causes these variables to be recognized as part of Airflow's internal configuration, leading to their unintended exposure in the Airflow Web UI (under Admin -> Configuration), even when ``AIRFLOW__API__EXPOSE_CONFIG`` is set to ``non-sensitive-only``.
+
+* **Avoid Unintended Environment Propagation to Workers**: Component-specific env configurations are intended strictly for specific components. However, the previous behavior caused these variables to be inadvertently passed to worker pods, which may result in unintended configuration conflicts and unexpected side effects.
+
+**Migration Required:**
+
+If you need to pass environment variables specifically to Kubernetes Executor worker pods, use one of the following approaches:
+
+**Option 1: Use ``.Values.env``**
+.. code-block:: yaml
+
+ env:
+ - name: my_var
+ value: "my_value"
+
+Environment variables in ``.Values.env`` are now passed as-is without the automatic prefix (same behavior as component-specific env).
+
+**Option 2: Use ``.Values.config.kubernetes_environment_variables``**
+.. code-block:: yaml
+
+ config:
+ kubernetes_environment_variables:
+ my_var: "my_value"
+
+**Secrets (``.Values.secret``):** The ``AIRFLOW__KUBERNETES_SECRETS__`` prefix is no longer automatically added. Secrets are now passed as-is via ``secretKeyRef`` without the prefixed copy for worker pods.
+
+Default Airflow image is updated to ``3.1.8`` (#63392)
+""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+The default Airflow image that is used with the Chart is now ``3.1.8``, previously it was ``3.1.7``.
+
+
+Features
+^^^^^^^^
+
+- Support Helm template expressions in ``podAnnotations`` and ``airflowPodAnnotations`` values. (#63019)
+- Add minute-level log retention to clean-logs script (#61855)
+- Add LOG_MAX_SIZE environment variables to log groomer (#61559)
+
+Improvements
+^^^^^^^^^^^^
+
+- Remove automatic ``KUBERNETES_ENVIRONMENT_VARIABLES`` and ``KUBERNETES_SECRETS`` prefixes from chart helpers (#60750)
+- Remove JWT secrets from triggerer, worker and dag-processor (#63204)
+- Add workers.celery.nodeSelector & workers.kubernetes.nodeSelector (#61957)
+- Add workers.celery.terminationGracePeriodSeconds & workers.kubernetes.terminationGracePeriodSeconds (#61892)
+- Add workers.celery.resources & workers.kubernetes.resources (#61890)
+- Add workers.celery.keda section (#61820)
+- Add workers.celery.podDisruptionBudget (#61414)
+- Add workers.celery.containerLifecycleHooks & workers.kubernetes.containerLifecycleHooks (#61369)
+- Refactor Git-Sync livenessProbe & deprecate readinessProbe & add startupProbe (#62334)
+- Default airflow version to 3.1.8 (#63392)
+- Drop support for all Airflow versions below 2.11 in Helm Chart (#61018)
+- Support Helm template expressions in podAnnotations (#63019)
+- Warn on deprecated per-component securityContext values (#62729)
+
+Bug Fixes
+^^^^^^^^^
+
+- Add ``*.iml`` to .gitignore in all distributions (#63636)
Review Comment:
Not a user facing pr
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org