GitHub user potiuk added a comment to the discussion: Kuberentes integration settings/commands for Breeze environment?
Yes. Breeze `k8s` suite of commands is the wy to go. It has a bit of a difficult in iterating - i.e. every time you make changes to provider / airflow code you need to rebuild and redeploy the image. We have an open issue to improve the iteration speed - https://github.com/apache/airflow/issues/44508 - but we did not have time/energy to work on it and other things took priority. You have details step-by-step instructions how to do it: https://github.com/apache/airflow/blob/main/contributing-docs/testing/k8s_tests.rst#typical-testing-pattern-for-kubernetes-tests - including the fact that k8s suite of commands work in a "wizard" like way guiding you what are the next steps. In short: * it sets up a local venv which has everything configured and all tools (kind, kubectl, helm) automatically installed in this separate env * it creates a kind cluster of your choice * It builds a base image that you can use to deploy airflow with (with embedded example dags) * it allows you to rebuild the image with your latest changes * it allows you to deploy the image to the kind cluster * it uses helm to start complete "airflow" installation in the cluster that you can connect to and interact with So - the limitation is that every time you make a change you need to: * rebuild (inclrementally - so it takes seconds) your image * deploy it to kind cluster * restart the pods This is slow - but works. With the opened issue we imagine a workflow where tools like teleport are used to send the modified files via ssh to the running pods and the pods have a way to pick the files up and restart the interpreters - that would be much faster, workflow but also more complex and brittle. GitHub link: https://github.com/apache/airflow/discussions/52131#discussioncomment-13560418 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
