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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to