developer-rpai commented on code in PR #73082: URL: https://github.com/apache/airflow/pull/73082#discussion_r4012091842
########## chart/docs/migrate-to-git-dag-bundle.rst: ########## @@ -0,0 +1,222 @@ +.. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +.. _git_sync_to_git_dag_bundle: + +Migrating from Git-Sync to GitDagBundle +======================================= + +This guide is for users of the Git-Sync sidecar (``dags.gitSync``) in Helm Chart 1.x. +The Git-Sync sidecar is planned for removal in Helm Chart 2.0 in favour of the +Airflow-native :class:`~airflow.providers.git.bundles.git.GitDagBundle`. + +What is changing +---------------- + +With Git-Sync, a ``git-sync`` container ran as a sidecar (or init container) on the +scheduler, dag processor, worker and triggerer pods, keeping a shared DAG folder up +to date from a git repository. + +With ``GitDagBundle``, syncing moves into Airflow itself. The Dag Processor clones +the repository once into a local bare repository and refreshes it every +``refresh_interval`` seconds. Task execution resolves DAG code from versioned +bundles, so workers always run the code version the Dag Processor recorded. No +sidecar containers and no shared ``ReadWriteMany`` volume are needed for syncing. + +Differences to be aware of before migrating: + +* Git-Sync synced a single repository per deployment (multiple repositories required + an "umbrella" repository with submodules). ``dagProcessor.dagBundleConfigList`` + accepts multiple bundles, so each repository simply becomes its own bundle. +* Git-Sync always checked out the latest commit. ``GitDagBundle`` supports Review Comment: Good catch, thanks. Removed that sentence as suggested. The bullet now covers only the GitDagBundle versioning behavior. -- 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]
