More polling

[derrickburns]

When i manually delete a HelmRelease it seems that the polling from that release still persists because I keep getting more and more polling:

default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:15.579423251Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:15.579423251Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:15.579423251Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:15.579423251Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:15.579423251Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:20.271795572Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:23.038161445Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:23.038161445Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:23.038161445Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:23.038161445Z caller=images.go:17 component=sync-loop msg="polling images"
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T03:14:23.038161445Z caller=images.go:17 component=sync-loop msg="polling images"


default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26
default/flux-fbcb78db-xfglz[flux]: ts=2019-03-19T04:14:24.526691555Z caller=loop.go:105 component=sync-loop event=refreshed url=git@github.com:tidepool-org/dev-ops branch=qa HEAD=156db4123487e0cfb701e4140f30623410e51d26

[squaremo]

That's basically spinning, isn't it. Have you supplied a value to any of the fluxd arguments with -interval in the name?

[derrickburns]

I don't think that it is spinning. I think the number of "polling images" is exactly the number of times I created a helm release (usually following the manual deletion of the previous one with kubectl delete helmrelease ....

[squaremo]

The subroutine that polling-images refers to isn't (or shouldn't be) related to the number of resources -- it's run on a timer. So it's mysterious that it appears to be triggered several times in quick succession, and that the number of times correlates with anything else. 🤔

[squaremo]

Is there anything "interesting" you can think of about how you've set fluxd and helm-operator up @derrickburns? Or to put it another way, if I set up a stock install of Flux (fluxd and helm-operator), do you reckon I'd need to do anything extra, before I'd be able to reproduce this behaviour?

[derrickburns]

I did not do anything "interesting".

…

On Mar 25, 2019, 9:58 AM -0700, Michael Bridgen ***@***.***>, wrote: Is there anything "interesting" you can think of about how you've set fluxd and helm-operator up @derrickburns? Or to put it another way, if I set up a stock install of Flux (fluxd and helm-operator), do you reckon I'd need to do anything extra, before I'd be able to reproduce this behaviour? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[kingdonb]

Closing. Flux v1 is in maintenance #3320