Feature Request: Different period setting for the initial sync

[jebbench]

Is it possible to specify a different period option for the initial sync?

What I'd like to be able to do is have git-sync retry every 500ms until it manages to complete the initial sync and thereafter update every 60s.

Our use case is an envoy sidecar that takes a second or so to start up and provide internet access, unfortunatly git-sync is too fast and the initial sync fails; we then have to wait a minute before it retries.

Cheers

[thockin]

I would be open to a few options.

We could have a --startup-delay flag which just tells it to wait. But that is coarse.

We could have a --init-period and maybe --init-timeout to accommodate both the problem you described and the need to pull a whole repo on the first sync.

PRs are welcome. I am slammed right now.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale