squaremo
commented
6 years ago flux will run
kubectl apply -fevery five minutes even though there are no changes to my images or git repo. I'm unsure if this is expected behavior, but this causes some chatty logs and makes alert mechanisms like fluxcloud useless.
Running every five minutes, whether or not there are changes in the git repo, is deliberate. We aren't in general party to changes made in the cluster, so to have any kind of reliable convergence, we need to maintain the state in git as well as effect changes. (If we were listening to all changes, we could make compensating changes to maintain the state -- but since kubectl apply effectively calculates those compensating changes for us, it's simpler to just apply everything).
Sending notifications on every sync is not expected. I can think of a couple of reasons it might happen:
-
The git tag used as a high water mark is not pushed to the upstream git repo; that will cause fluxd to resend notifications (they are at-least-once). I think you've indicated in slack that this shouldn't be a problem, and it's not reported in the log above, either.
-
fluxd genuinely thinks it's syncing new commits each time. We can only see one such occasion in the logs above; the tell-tale sign would be if it repeated the line naming the commits, with the same SHA1s.
ts=2018-09-18T17:00:42.202641443Z caller=loop.go:399 component=sync-loop tag=flux-sync old=7fe661acf0038cbf31d8cc1af16e7e2f147129ae new=0cdad5feccc7ad234d77c81c45ad71398b652ea3
wavemoran
flux will run
kubectl apply -fevery five minutes even though there are no changes to my images or git repo. I'm unsure if this is expected behavior, but this causes some chatty logs and makes alert mechanisms like fluxcloud useless.Example log file: