You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
In the weaveworks sock shop cluster I observed fluxd running kubectl every few seconds. See #926 (comment)
@squaremo discovered that there was a github hook configured, and removing that stopped this behaviour.
What's puzzling here is that the underlying repo receives just ~1 commit a day, so the hook should not be triggered frequently.
One theory here is that flux is doing some git tagging when sync'ing, and that in turn is triggering the hook, which in turn would trigger more sync'ing.
The text was updated successfully, but these errors were encountered:
One theory here is that flux is doing some git tagging when sync'ing, and that in turn is triggering the hook, which in turn would trigger more sync'ing.
Maybe, but the daemon doesn't attempt to push a new tag unless the head commit has changed, and I'd expect it to log that it was doing so. Maybe there's some corner case for this particular repo; one could try installing the hook for a fresh flux-example to see if it happens there too.
Extracted from #926...
In the weaveworks sock shop cluster I observed fluxd running kubectl every few seconds. See #926 (comment)
@squaremo discovered that there was a github hook configured, and removing that stopped this behaviour.
What's puzzling here is that the underlying repo receives just ~1 commit a day, so the hook should not be triggered frequently.
One theory here is that flux is doing some git tagging when sync'ing, and that in turn is triggering the hook, which in turn would trigger more sync'ing.
The text was updated successfully, but these errors were encountered: