-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make event cache tunable #2928
Make event cache tunable #2928
Conversation
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8a06e70
to
7ff711c
Compare
eb2d780
to
649da64
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Lgtm! Out of curiosity, what was the reason behind this change?
These include the number of retries and the delay between them. New command line arguments to do that: --event-cache-retries int Number of retries for event cache (default 15) --event-cache-retry-delay int Delay in seconds between event cache retries (default 2) Signed-off-by: Anastasios Papagiannis <[email protected]>
The previous patch makes EventCache configurable. This allows to reduce some delays in the tests. Signed-off-by: Anastasios Papagiannis <[email protected]>
Signed-off-by: Anastasios Papagiannis <[email protected]>
649da64
to
b2f6473
Compare
There may be cases where the k8s watcher is overloaded and the default settings may not enough. On the other hand, having a large delay may result on waiting too much for getting events (even without pod info). So I believe that this is a good idea to allow users to configure that based on their needs. |
This PR makes the event cache tunable. This includes the number of retries and the delay between each retry. For this reason we introduce 2 new command line flags:
This PR does not change the default values of those.
We also export those values through the Helm Chart.