Fix breeze k8s dev doesn't include configure-cluster test resource #60259
Conversation
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
Co-authored-by: jason810496 <68415893+jason810496@users.noreply.github.com>
jason810496
requested review from
amoghrajesh,
ashb,
bugraoz93,
ephraimbuddy,
gopidesupavan,
jedcunningham,
jscheffl,
kaxil and
potiuk
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
potiuk
approved these changes
Jan 8, 2026
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker e36e6ca v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
chirodip98
pushed a commit
to chirodip98/airflow-contrib
that referenced
this pull request
Jan 9, 2026
…pache#60259) * Initial plan * Add portForward section to _build_skaffold_config for API server Co-authored-by: jason810496 <68415893+jason810496@users.noreply.github.com> * Add kubectl section instead of portForward section * Fix: hooks should place under helm instead of kubectl --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
…pache#60259) * Initial plan * Add portForward section to _build_skaffold_config for API server Co-authored-by: jason810496 <68415893+jason810496@users.noreply.github.com> * Add kubectl section instead of portForward section * Fix: hooks should place under helm instead of kubectl --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
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.
related: #59869
Why
In #59869, we add the hint that show
Alternatively, jump straight into development on Kubernetes with: breeze k8s dev --python {python} --kubernetes-version {kubernetes_version}after runningbreeze k8s create-clusterhttps://github.com/apache/airflow/pull/59869/files#diff-ec0edb35ebfa2f51b6030b54f72eb90b0661eb310b0baea6e9c605f49c15123dR331-R335
However, when I run
breeze k8s devright afterbreeze k8s create-cluster. I'm not able to access API Server because the k8s test resources inscripts/ci/kubernetesare not deployed. Since we skip thebreeze k8s configure-clustercommand.What
We should also deploy the test resources in
scripts/ci/kuberneteswith skaffold in case the user didn't runbreeze k8s configure-clusterbeforebreeze k8s dev.Technical detail:
deploy.kubectlsection multi deploy approach (Use helm deploy next to kubectl GoogleContainerTools/skaffold#528), but doesn't work as expected