You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/04/24 18:31:35 UTC
[PR] Helm release docs: add Breeze + KinD verification path [airflow]
potiuk opened a new pull request, #65817:
URL: https://github.com/apache/airflow/pull/65817
The contributor verification section in
``dev/README_RELEASE_HELM_CHART.md`` currently only shows
``helm install`` against an existing cluster. Add an end-to-end
recipe that uses the ``breeze k8s`` commands to spin up a fresh
KinD cluster from scratch, build a k8s-ready airflow image,
load it into the cluster, and helm-install the chart from the
RC tag.
Useful when the verifier doesn't already have a Kubernetes
cluster handy — and doubles as a chart-content sanity check
because it deploys the same chart files that were packaged into
the RC tarball. Documents both the ``deploy-cluster`` aggregate
(on main) and the constituent ``create-cluster`` /
``configure-cluster`` / ``build-k8s-image`` / ``upload-k8s-image``
sequence (on older tags), plus the ``status`` /
``api/v2/monitor/health`` smoke checks and the
``delete-cluster`` teardown.
Verified against helm-chart/1.21.0rc2 — all airflow pods reached
Running, all four health entries (metadatabase, scheduler,
triggerer, dag_processor) reported healthy, and the version
endpoint returned the airflow image pinned by the chart.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.7)
Generated-by: Claude Code (Opus 4.7) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #65817:
URL: https://github.com/apache/airflow/pull/65817#issuecomment-4320203502
Also - added manual verification step - actually **doing stuff** with running Airflow. :)
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #65817:
URL: https://github.com/apache/airflow/pull/65817#discussion_r3142318508
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,72 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Install the shared k8s tooling (kind, kubectl, helm) into Breeze's
+ pinned virtualenv:
+
+ ```shell
+ breeze k8s setup-env
Review Comment:
Ahh.. good point.
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,72 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Install the shared k8s tooling (kind, kubectl, helm) into Breeze's
+ pinned virtualenv:
+
+ ```shell
+ breeze k8s setup-env
+ ```
+
+3. Create the cluster, configure namespaces, build a k8s-ready airflow
+ image, and load it into KinD. On main these are bundled into a single
+ `breeze k8s deploy-cluster`; on older tags run them in sequence:
+
+ ```shell
+ breeze k8s deploy-cluster # main
Review Comment:
NIce!
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "Miretpl (via GitHub)" <gi...@apache.org>.
Miretpl commented on code in PR #65817:
URL: https://github.com/apache/airflow/pull/65817#discussion_r3142397483
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,90 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Create the cluster, configure namespaces, build a k8s-ready airflow
+ image, and load it into KinD. On main these are bundled into a single
+ `breeze k8s deploy-cluster` (which also installs the shared k8s
+ tooling — kind, kubectl, helm — into Breeze's pinned virtualenv,
+ i.e. it includes the work `breeze k8s setup-env` would do); on older
+ tags, run `setup-env` plus the constituent commands in sequence:
+
+ ```shell
+ breeze k8s deploy-cluster --rebuild-base-image # main
+ # or, on older tags:
+ breeze k8s setup-env
+ breeze k8s create-cluster
+ breeze k8s configure-cluster
+ breeze k8s build-k8s-image --rebuild-base-image
Review Comment:
```suggestion
breeze k8s configure-cluster
breeze ui compile-assets # Makes sure that all UI-related assets are built
breeze k8s build-k8s-image --rebuild-base-image
```
Didn't notice on the phone before - this is for making sure that after deployment of Airflow, the user will not face `missing index.html file` error during UI loading (FYI: this command is also part of the `deploy-cluster` one).
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "bugraoz93 (via GitHub)" <gi...@apache.org>.
bugraoz93 commented on PR #65817:
URL: https://github.com/apache/airflow/pull/65817#issuecomment-4315662636
Thanks Jarek!
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #65817:
URL: https://github.com/apache/airflow/pull/65817
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "Miretpl (via GitHub)" <gi...@apache.org>.
Miretpl commented on code in PR #65817:
URL: https://github.com/apache/airflow/pull/65817#discussion_r3141613362
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,72 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Install the shared k8s tooling (kind, kubectl, helm) into Breeze's
+ pinned virtualenv:
+
+ ```shell
+ breeze k8s setup-env
+ ```
+
+3. Create the cluster, configure namespaces, build a k8s-ready airflow
+ image, and load it into KinD. On main these are bundled into a single
+ `breeze k8s deploy-cluster`; on older tags run them in sequence:
+
+ ```shell
+ breeze k8s deploy-cluster # main
Review Comment:
```suggestion
breeze k8s deploy-cluster --rebuild-base-image # main
```
To make this one the same with the set of commands below
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,72 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Install the shared k8s tooling (kind, kubectl, helm) into Breeze's
+ pinned virtualenv:
+
+ ```shell
+ breeze k8s setup-env
Review Comment:
This command is also part of `breeze k8s deploy-cluster` command
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #65817:
URL: https://github.com/apache/airflow/pull/65817#issuecomment-4320192896
Thanks for the review @Miretpl! Both points applied:
- Removed the standalone `setup-env` step on the `deploy-cluster` path and noted that `deploy-cluster` already covers it; `setup-env` is now only listed for the older-tags constituent-commands path.
- Added `--rebuild-base-image` to the `deploy-cluster` invocation to match the `build-k8s-image` flag below.
Could you take another look when you get a chance?
--
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] Helm release docs: add Breeze + KinD verification path [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #65817:
URL: https://github.com/apache/airflow/pull/65817#discussion_r3144173728
##########
dev/README_RELEASE_HELM_CHART.md:
##########
@@ -768,6 +771,90 @@ helm install airflow apache-airflow-dev/airflow
You can then perform any other verifications to check that it works as you expected by
upgrading the Chart or installing by overriding default of `values.yaml`.
+## End-to-end verification with Breeze and KinD
+
+If you don't already have a Kubernetes cluster handy, the `breeze k8s`
+commands give you a clean room: a fresh KinD cluster plus the chart
+deployed from your local checkout. This runs the same chart files that
+were packaged into the RC tarball, so it doubles as a chart-content
+sanity check.
+
+1. Check out the RC tag so the local `chart/` directory is the candidate
+ under vote:
+
+ ```shell
+ git checkout helm-chart/${VERSION_RC}
+ ```
+
+2. Create the cluster, configure namespaces, build a k8s-ready airflow
+ image, and load it into KinD. On main these are bundled into a single
+ `breeze k8s deploy-cluster` (which also installs the shared k8s
+ tooling — kind, kubectl, helm — into Breeze's pinned virtualenv,
+ i.e. it includes the work `breeze k8s setup-env` would do); on older
+ tags, run `setup-env` plus the constituent commands in sequence:
+
+ ```shell
+ breeze k8s deploy-cluster --rebuild-base-image # main
+ # or, on older tags:
+ breeze k8s setup-env
+ breeze k8s create-cluster
+ breeze k8s configure-cluster
+ breeze k8s build-k8s-image --rebuild-base-image
Review Comment:
Applied in d775708c — added `breeze ui compile-assets` between `configure-cluster` and `build-k8s-image` on the older-tags constituent path. Inline comment is slightly different from your suggestion ("ensures the UI is built so the API server can serve index.html") because that names the failure mode it prevents. Thanks for catching it!
--
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