Add support for ARM for falcosidekick-ui chart
Motivation
As Falco supports ARM, I guess it would be nice for sidekick-ui to support ARM as well, and that includes the Redis dependency
Feature
Support ARM CPUs
Alternatives
Use sidekick with no UI
Additional context
Related to https://github.com/falcosecurity/falcosidekick-ui/issues/66
Related to https://github.com/RediSearch/RediSearch/issues/3110
I agree it could be nice, for falcosidekick-ui itself, it's not an issue and we can add ARM support. For redisearch, they don't provide an ARM image and you must know, I had to fork it to add TTL to keys, my PR to add it in the upstream is still waiting https://github.com/RediSearch/redisearch-go/pull/167
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Does Falco fully support ARM?
I am testing out running the daemonset on the latest k8s v1.23 EKS AMI and I am getting this error from the init container (image docker.io/falcosecurity/falco-driver-loader:0.33.1):
* Trying to download a prebuilt falco module from https://download.falco.org/driver/3.0.1%2Bdriver/aarch64/falco_amazonlinux2_5.4.228-131.415.amzn2.aarch64_1.ko
curl: (22) The requested URL returned error: 404
Unable to find a prebuilt falco module
How often are these prebuilt falco modules updated?
You can search for available prebuilt drivers here https://download.falco.org/driver/site/index.html
Okay, so according to the docker hub readme for https://hub.docker.com/r/redislabs/redisearch container is deprecated and one should look into replacing it with redis-stack container. Worth noting is that the redis-stack container is indeed multi-arch.
I tested the images from https://hub.docker.com/r/redis/redis-stack, everything seems OK. I need to do more tests to see if you can migrate without losing the data.
Edit:
Good news, it works:
9:M 06 Feb 2023 19:05:12.873 # Done loading RDB, keys loaded: 50, keys expired: 0.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/reopen /remove-lifecycle rotten
@Issif: Reopened this issue.
In response to this:
/reopen /remove-lifecycle rotten
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
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 /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.