This is an automated email from the ASF dual-hosted git repository.
jscheffl pushed a commit to branch chart/v1-2x-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/chart/v1-2x-test by this push:
new dae65137c20 Backport of #73146 (#73573)
dae65137c20 is described below
commit dae65137c20b2b332a68a2a77db54a28c53ee293
Author: Przemysław Mirowski <[email protected]>
AuthorDate: Sun Nov 1 14:10:10 2026 +0100
Backport of #73146 (#73573)
Co-authored-by: Jens Scheffler <[email protected]>
---
chart/docs/extending-the-chart.rst | 2 +-
chart/docs/manage-dag-files.rst | 2 +-
chart/docs/parameters-ref.rst | 2 +-
chart/docs/production-guide.rst | 12 ++++++------
chart/docs/setting-resources-for-containers.rst | 2 +-
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/chart/docs/extending-the-chart.rst
b/chart/docs/extending-the-chart.rst
index e368e019c20..172dbb59acc 100644
--- a/chart/docs/extending-the-chart.rst
+++ b/chart/docs/extending-the-chart.rst
@@ -28,7 +28,7 @@ You can extend the official Airflow chart by applying the
following steps.
Create your custom Helm Chart
-----------------------------
-First, you will need to create you own chart directory. You can do it by
running the following command:
+First, you will need to create your own chart directory. You can do it by
running the following command:
.. code-block:: bash
diff --git a/chart/docs/manage-dag-files.rst b/chart/docs/manage-dag-files.rst
index 3ab65295654..e6ed7b6c47a 100644
--- a/chart/docs/manage-dag-files.rst
+++ b/chart/docs/manage-dag-files.rst
@@ -215,7 +215,7 @@ To configure mounting Dags from private GitHub repository,
follow below steps:
ssh-keygen -t rsa -b 4096 -C "[email protected]"
3. Add the public key to your private repo under ``Settings > Deploy keys``.
-4. Convert the private ssh key to a base64 string and save it's value.
+4. Convert the private ssh key to a base64 string and save its value.
.. note::
diff --git a/chart/docs/parameters-ref.rst b/chart/docs/parameters-ref.rst
index 49fd609f839..94157b156bd 100644
--- a/chart/docs/parameters-ref.rst
+++ b/chart/docs/parameters-ref.rst
@@ -81,7 +81,7 @@ and install the chart:
Deprecated Parameters
=====================
-The following table contains all deprecated configuration parameters of the
Airflow chart with their default values. All values defined in below table with
be removed
+The following table contains all deprecated configuration parameters of the
Airflow chart with their default values. All values defined in below table will
be removed
in the next Helm Chart major release.
.. jinja:: params_ctx
diff --git a/chart/docs/production-guide.rst b/chart/docs/production-guide.rst
index 4c3b7c00cda..ec6cb19eb36 100644
--- a/chart/docs/production-guide.rst
+++ b/chart/docs/production-guide.rst
@@ -49,7 +49,7 @@ To provide the database credentials to Airflow, you have 2
options - in your val
Values file
^^^^^^^^^^^
-This is the simpler options, as the chart will create a Kubernetes Secret for
you. However, keep in mind your credentials will be in your values file.
+This is the simpler option, as the chart will create a Kubernetes Secret for
you. However, keep in mind your credentials will be in your values file.
.. code-block:: yaml
:caption: values.yaml
@@ -128,8 +128,8 @@ If you are using PostgreSQL as your database, you will
likely want to enable `Pg
Due to distributed nature of Airflow, it can open a lot of database
connections. Using a connection pooler can significantly
reduce the number of open connections on the database.
-Database credentials stored Values file
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Database credentials stored in Values file
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. code-block:: yaml
:caption: values.yaml
@@ -138,8 +138,8 @@ Database credentials stored Values file
enabled: true
-Database credentials stored Kubernetes Secret
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Database credentials stored in Kubernetes Secret
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The default connection string in this case will not work. You need to modify
accordingly the Kubernetes secret:
@@ -659,7 +659,7 @@ Security Context
Constraints
^^^^^^^^^^^
-A ``Security Context Constraint`` (SCC) is a OpenShift construct that works as
a RBAC rule. However, it targets Pods instead of users.
+A ``Security Context Constraint`` (SCC) is an OpenShift construct that works
as an RBAC rule. However, it targets Pods instead of users.
When defining a SCC, one can control actions and resources a POD can perform
or access during startup and runtime.
The SCCs are split into different levels or categories with the ``restricted``
SCC being the default one assigned to Pods.
diff --git a/chart/docs/setting-resources-for-containers.rst
b/chart/docs/setting-resources-for-containers.rst
index 397d032052c..7c1398c62a4 100644
--- a/chart/docs/setting-resources-for-containers.rst
+++ b/chart/docs/setting-resources-for-containers.rst
@@ -50,4 +50,4 @@ For example, specifying resources for scheduler container:
memory: 1Gi
requests:
cpu: 500m
- memory: 512Gi
+ memory: 512Mi
