Michael Crenshaw

imo it's a good change to make in the release branches for everyone. I've often wondered why we're using pull policy always.

A couple things I noticed from the logs: 1) Requests are being throttled. Maybe tweaking the `--qps` and `--burst` flags on the workflow-controller could help? 2) Templates are being fetched...

@yordis started the [work](https://github.com/argoproj/argo-cd/pull/14272) but I think hit some walls. Would anyone be up for collaborating with them, or picking up the PR?

@yordis and I are gonna set up a call soon. @hannesg if you'd like to join, hit me up on CNCF Slack!

Conversations about these options have gotten a bit scattered. I'm going to consolidate them here, since this has a lot of thumbs-up. Here's the challenge: > Sparse and shallow git...

Moved out of the 3.0 milestone. Shallow/sparse are a lot more involved to design/implement than we can get to in 3.0.

Just my $0.02: I think we should implement sparse (not shallow) clone, configured at the repo Secret level. To avoid clashes between multiple repo Secrets targeting the same repo, we...

@todaywasawesome the problem with app-level sparse configs is that multiple apps with different sparse configs may use the same cached repo on disk.

Interesting, that could work... it would probably require persisting the app name in the cache on disk somewhere so that the path can be rediscovered if the repo server restarts.

@tosi3k just reading around about the watch cache, it looks like maybe the watch cache doesn't support pagination? https://github.com/kubernetes/kubernetes/issues/102672 If that's still the case, are we going to end up...