Remove Falco sidekick webui, since it uses Redis as a backend and that has issues

[wcarlsen]

TLDR: We opted for removing the webui component

Okay I found that we have around 300k events stored in Redis around the clock and we do not implement TTL (can be set via the values file) on events, so I think that might be why we see crazy memory usage. Also Redis seems to behave like it has a memory leak. Also in the webui OOM's whenever I query it.

Here is my conclusions from investigations:

• The webui might have worked upon install, but seems to have run into issues since then
• Redis has around 300k events, but many of them seems to be really old
• Falcoside kick sends event to webui that then uses Redis as a backend. We cannot set a minimumpriority here, but we can set TTL on events
• The webui OOM's upon simple queries going back in time

Solutions possible:

• Remove webui completely
• Set TTL on event from the webui and empty Redis for old event and set maxmemory-policy to volatile-ttl (evict keys closest to expiry)

[samidbb]

I can't see where this breaks anything on the consumer's end that you have marked to be as major release?

[wcarlsen]

I can't see where this breaks anything on the consumer's end that you have marked to be as major release?

I'm fine with lowering it to minor or patch. Which do you prefer?

[samidbb]

looks good