Skip to content

Conversation

@nailo2c
Copy link
Contributor

@nailo2c nailo2c commented Dec 23, 2025

Closes: #40005

Why

Based on my experience resolving k8s-related bugs, it's quite inconvenience to build and upload a k8s image when I only make a small change.

How

After some research, I decided integrate Skaffold into breeze k8s to improve the development experience.

What

  1. /dags folder synchronization
airflow_40005_demo_output.mp4
  1. Airflow Core synchronization [WIP]

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Dec 23, 2025
@potiuk
Copy link
Member

potiuk commented Dec 23, 2025

WOWOWOWOWOW !

@potiuk
Copy link
Member

potiuk commented Dec 23, 2025

One comment here - (might be follow-up) - if we run airflow commands in the chart with --dev flags , we could also simply synchronize airflow's source code - not only Dags. We already have built-in hot-reload in airflow components when they are run in --dev mode, so all we need is to sync the source change to the right folder.

- Updated output_k8s.txt with new hash value.
- Added output_k8s_dev.svg for visual representation of the 'k8s dev' command usage.
- Created output_k8s_dev.txt with corresponding hash for the new SVG output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve development experience for breeze k8s suite of commands

2 participants