Helm Chart Documentation Update#66970
Open
Miretpl wants to merge 9 commits into
Open
Conversation
Contributor
Author
|
Also goes for 1.2x line. Newsfragment - I'm not sure if it should be added here (to main) or in backport PR. I was also wondering if it should be added, but I think that it would be good for users to know (in one way or the other) that we do not know if the chart will render properly on lower versions than min in our CI. |
Miretpl
requested review from
bugraoz93,
hussein-awala,
jedcunningham and
jscheffl
as code owners
jscheffl
approved these changes
May 15, 2026
Contributor
jscheffl
left a comment
jscheffl
left a comment
There was a problem hiding this comment.
Cool! Just found 1 typo
|
|
||
| .. note:: | ||
|
|
||
| Due to security concerts, it is not advised to set sensitive values like passwords within the ``values.yaml``. |
Contributor
There was a problem hiding this comment.
Typo
Suggested change
| Due to security concerts, it is not advised to set sensitive values like passwords within the ``values.yaml``. | |
| Due to security concerns, it is not advised to set sensitive values like passwords within the ``values.yaml``. |
|
|
||
| Chart ``1.17.0`` raised the minimum supported Kubernetes version to ``1.30``. Upgrade your cluster before upgrading | ||
| the chart if needed. | ||
| Chart ``1.19.0`` supports ``1.30+`` Kubernetes version. Upgrade your cluster before upgrading the chart if needed. |
Contributor
There was a problem hiding this comment.
Adding Jinja constants here as well?
| .. jinja:: global_ctx | ||
|
|
||
| - Kubernetes {{ min_k8s_version }}+ cluster | ||
| - Helm 3.19+ |
Contributor
There was a problem hiding this comment.
Should we make Helm version also a Jinja value?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update of Helm Chart documentation, which consists of:
workerstoworkers.celery/workers.kubernetessectionsParametersdocumentation and add newDeprecated Parameterssectionresources-related docUpgrading to Airflow 3doc (mostly to not recommend users to use Helm Chart version with a lot of bugs which were fixed in later versions)Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.