new: prebuild module for bottlerocketos_5.4.50_1

[faarshad]

Signed-off-by: Fahad Arshad [email protected]

This is for bottlerocketos with the AMI name bottlerocket-aws-k8s-1.16-x86_64-v1.0.1-2a181156.

[poiana]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[leodido]

Hello!

Unfortunately driverkit does not support bottlerocket yet.

There've been some requests to support it in the past and some discussions around it (see here).

We do not have cycles to work on a bottlerocket driverkit builder right now and we'd love to review a PR in driverkit that adds one!

[leodido]

/hold

[faarshad]

Hi @leodido ,
I tested building bottlerocket falco driver using the vanilla builder with kernelconfigdata embedded into the yaml and it seems to work fine. The kernel & kernel-devel packages for bottlerocket don't seem to be available publicly and neither is /proc/config.gz, so I am wondering whether it will be acceptable to put in a PR in https://github.com/falcosecurity/test-infra with kernelconfigdata for bottlerocket-5.4.50 in it using the vanilla builder. We can name the output .ko file something bottlerocket specific like falco_bottlerocket_5.4.50_1.ko

We will have to add a section a called drivers/build/vanilla in circleci jobs
WDYT?

[faarshad]

tagging falco maintainers to solicit some feedback ⬆️ cc: @leodido @leogr @fntlnz @kris-nova

[leodido]

Hey @farshad-hobsons thanks for investigating this topic.

Anyways, I'd personally avoid putting vanilla drivers in the drivers build grid in this repository.

Furthermore, I'm not still sure that using the vanilla builder + config.gz is the correct way to go for bottlerocket OS.

Please look here:

• https://github.com/bottlerocket-os/bottlerocket/blob/d3096e86cf63f49294144a1f5d5d0cd7d3d56f92/packages/kernel/kernel.spec#L10
• https://github.com/bottlerocket-os/bottlerocket/blob/d3096e86cf63f49294144a1f5d5d0cd7d3d56f92/packages/kernel/kernel.spec#L46-L58

These seem to be the steps a custom bottlerocket builder for driverkit must do, IMHO.

Waiting for the feedback of other test-infra maintainers @falcosecurity/test-infra-maintainers

[faarshad]

Thank you for your feedback. Closing this in favor of falcosecurity/driverkit#75