Thomas Labarussias

At falcosidekick level it's ok, and for falcosidekick-ui? Is the redis correctly running? When you try to access through the port-forward, what http error do you get?

Your service name is strange, on my side, I start the port-forward with just: ```shell kubectl port-forward svc/falco-falcosidekick-ui 2802:2802 -n falco ``` Can you list your services to be sure...

Everything is ok at this level, I don't understand why the port-forward fails. It doesn't seem related to falcosidekick-ui but more on your K8s config. Any CNI that could create...

Here's the correct syntax: ``` helm install falco -n falco --set tty=true falcosecurity/falco --set falcosidekick.enabled=true --set falcosidekick.webui.enabled=true --set falcosidekick.webui.externalRedis.enabled=true --set falcosidekick.webui.externalRedis.url=10.X.X.X --set falcosidekick.webui.externalRedis.port=6379 ``` I agree `falcosidekick.webui.externalRedis.url` is not well...

Add `--set falcosidekick.webui.redis.enabled=false`. All values are there: https://github.com/falcosecurity/charts/blob/master/falcosidekick/values.yaml

Are you sure to run a redis instance with `redisearch` module? It's a requirement.

Can you check in logs if : - falco triggered an alert - falcosidekick received the alert - falcosidekick forward the alert to the UI

Are you running falcosidekick-ui on arm64? We discovered a strange bug https://github.com/falcosecurity/falcosidekick-ui/issues/95 For now, I don't have access to an arm64 machine to reproduce.

Can you paste me your whole values.yaml please? Just edit the sensitive data. Right now, I don't see any issue.

I don't see any issue with this config. Can you try to create a port-forward to a falcosidekick pod and trigger a test event: ``` kubectl port-forward svc/falco-falcosidekick 2801:2801 -n...