Skip to content

flux2-sync: Add support for sparseCheckout in GitRepository#274

Open
madhan1115 wants to merge 6 commits intofluxcd-community:mainfrom
madhan1115:main
Open

flux2-sync: Add support for sparseCheckout in GitRepository#274
madhan1115 wants to merge 6 commits intofluxcd-community:mainfrom
madhan1115:main

Conversation

@madhan1115
Copy link

@madhan1115 madhan1115 commented Jan 2, 2026

The GitRepository resource includes a sparseCheckout option to limit Flux artifacts to specific directories; however, this functionality was previously missing from the flux2-sync helm chart. This PR implements that support.

Checklist

  • DCO signed
  • Chart Version bumped
  • helm-docs are updated
  • Helm chart is tested
  • Update artifacthub.io/changes in Chart.yaml
  • Run make reviewable

Signed-off-by: madhanb <madhanb@informatica.com>
Signed-off-by: madhanb <madhanb@informatica.com>
Signed-off-by: madhanb <madhanb@informatica.com>
Signed-off-by: madhanb <madhanb@informatica.com>
Signed-off-by: madhanb <madhanb@informatica.com>
Signed-off-by: madhanb <madhanb@informatica.com>
@madhan1115
Copy link
Author

@stefanprodan @dwerder @haarchri @dmccaffery Please review the attached comparison of repository sizes with and without the Sparse Checkout feature enabled. Our benchmarks show that enabling this feature significantly reduces both disk footprint and clone duration.

Given that the source controller clones the repository every 15 minutes, implementing this change will save terabytes of data transfer monthly, leading to substantial cost savings and improved pipeline efficiency.

Please consider labeling this priority one.

with-sparse-checkout without-sparse-checkout

@alex-shpak
Copy link

Seems to be a duplicate: #260 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants