Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Make update interval a configurable flag #44

Merged
merged 3 commits into from
Sep 23, 2019
Merged

Conversation

hiddeco
Copy link
Member

@hiddeco hiddeco commented Sep 19, 2019

As in clusters that have many HelmRelease resources, the hardcoded
default would put too much pressure on etcd due to Tiller collecting
information. By making the interval a configurable flag, people can
tweak the value to find the right balance of (non) pressure and
observability.

Image for testing available as hiddeco/helm-operator:update-interval-conf-9a48227b

As in clusters that have many `HelmRelease` resources, the hardcoded
default would put too much pressure on `etcd` due to Tiller collecting
information. By making the interval a configurable flag, people can
tweak the value to find the right balance of (non) pressure and
observability.
@hiddeco hiddeco force-pushed the update-interval-conf branch from 9a48227 to 91c0b11 Compare September 23, 2019 09:24
Copy link
Member

@stefanprodan stefanprodan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hiddeco
Copy link
Member Author

hiddeco commented Sep 23, 2019

@stefanprodan given we do not have an 'additional args' value in the Helm chart as we have in the Flux one; do you think adding this to the chart as a dedicated flag is desired, or would you vote for adding an 'additional args' value to the chart instead?

@stefanprodan
Copy link
Member

I would go with a dedicated flag.

@hiddeco hiddeco force-pushed the update-interval-conf branch from 04a98b0 to 59fab1c Compare September 23, 2019 14:37
@hiddeco hiddeco merged commit 088bbb3 into master Sep 23, 2019
@hiddeco hiddeco deleted the update-interval-conf branch September 23, 2019 14:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants