-
Notifications
You must be signed in to change notification settings - Fork 16
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
Control the memory consumption of Redis Stack #140
Comments
Thanks for this issue and the details. I'll think a way to manage that. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
It's now possible to specify a custom config for the redis deployed with falcosidekick-ui: https://github.com/falcosecurity/charts/blob/22b3f58f5e7816ffdce8cb67ec2aa132192429d7/charts/falcosidekick/values.yaml#L1243 |
On Kubernetes, using Falco, Falcosidekick and Falcosidekick UI with the Redis instance that comes with it, we're looking for a way to control Redis memory usage. Because usage seems to grow and grow until the Redis pod gets OOM killed over and over again.
This is the used Redis config:
And I believe the
ttl
setting below should rotate data:It is unclear what Redis does with this setting. It would be useful to be able to set settings like the below, which should probably prevent these issues:
I hope there is a way to keep it manageable without increasing the memory limit and decreasing the
ttl
.The text was updated successfully, but these errors were encountered: