CI: pipeline, test and release targets for aarch64 and armv7

[fntlnz]

Motivation

Once that #1442 is merged, Falco can be built on aarch64 and armv7 architectures.

For divulgation purposes, we already created a manual build artifact with which @alexellis was able to run Falco on k3s - https://blog.alexellis.io/falco-at-the-edge-arm64/

However, until we don't have the build and test for aarch64 and armv7 in the pipeline we are not producing the artifacts to enable our users to use Falco on ARM in production.

Feature

• CircleCI pipeline to build and test Falco for aarch64
• CircleCI pipeline to build and test Falco for armv7
• CircleCI pipeline to release on tag for aarch64
• CircleCI pipeline to release on tag for armv7
• CircleCI pipeline to release the development version on master for aarch64
• CircleCI pipeline to release the development version on master for armv7

See: https://github.com/falcosecurity/falco/blob/master/.circleci/config.yml\

Discussion on how to do ARM builds on CircleCI: https://discuss.circleci.com/t/arm-builds/29102/13

Additional context

We have a working group to discuss the points above.

Working group announcement: https://lists.cncf.io/g/cncf-falco-dev/message/183

[AGSaidi]

Circle CI is planning arm64 support. In the mean time Travis has it available.

[inductor]

By using buildx you can simply build multi architecture images on anywhere :)

I found that Dockerfile in falco strongly depend on amd64 based packages.
ref. https://github.com/falcosecurity/falco/blob/master/docker/falco/Dockerfile#L42-L67

These package does not seem to be available on the artifact store.
https://dl.bintray.com/falcosecurity/dependencies/

[adammw]

@fntlnz is there possibility of cross-compiling using existing x86_64 CI pipeline until your CI tool provides native arm64/aarch64 support?

[xunholy]

Seeing the dependency PR merged is there any update on the progress of this ticket?

[leodido]

There has been an initial attempt by @fntlnz and myself using CircleCI and multiarch/qemu in this branch.

Anyway, we decided to implement it using our Falco Infra (ARM support is coming there, see this PR).

[poiana]

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

[poiana]

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

[poiana]

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]

@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.