Airflow git-sync is not working

[Jim0530]

Checks

• I have checked for existing issues.
• This report is about the User-Community Airflow Helm Chart.

Chart Version

8.9.0

Kubernetes Version

1.28.1
1.24.17

Helm Version

3.9.4

Description

my airflow version is 2.9.3
I was trying to use git-sync as my dag solution. My git respository is called Airflow. And when i deploy airflow with helm. i found out that there's no dag in airflow. However when i user airflow with image to update dags it works.
This is my folder structure of my repo.

• dags
• src
  so i config the subrepoPath: "dags/"

So when i find out dags missing, i check my folder under /opt/airflow/dags there's a /opt/airflow/dags/Airflow.git which is weird and maybe can explain the reason that dags is missing. Is there any solution of it?

Relevant Logs

Nothing

Custom Helm Values

No response

[thesuperzapper]

@Jim0530 what version of airflow do you see in the bottom left of your web UI?

Also, do you seen any logs on the git-sync sidecar container of the scheduler pod?

Also, can you share your git-sync values?

[Jim0530]

i find out that i am using the newest image for git-sync which those variables are not allowed to use

[CoinCoderBuffalo]

Seeing the same problem with 8.9.0. I downgraded to 8.8.0 and the git sync seems to be working again.

[thesuperzapper]

@CoinCoderBuffalo I think the most likely issue was that you were trying to use the 4.X.X versions of the git-sync image, rather than the 3.6.9 versions.

Currently, the latest version supported by 8.9.0 (and before) is registry.k8s.io/git-sync/git-sync:v3.6.9.

If someone wants to look into what changed in git-sync v4 and make a PR for the chart, that would be great. (Not sure if its possible to make the changes in a backwards compatible way, or if we need to tell people to use v4 versions of git-sync only, after the update).

[stale]

This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.

Thank you for your contributions.

---

Issues never become stale if any of the following is true:

1. they are added to a Project
2. they are added to a Milestone
3. they have the lifecycle/frozen label