-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Builder for RHCOS #86
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closing this issue. In response to this:
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. |
A builder for RHCOS/RHEL 8 still would be very helpful. |
/reopen |
@Tamronimus: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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 |
@FedeDP: Reopened this issue. In response to this:
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. |
I think you can use vanilla builder passing to it a kernel config; see for example what we do for bottlerocket with kernel-crawler: https://falcosecurity.github.io/kernel-crawler/?arch=x86_64&target=BottleRocket |
Well, for RHEL 8, you'll need access to a system that is registered to receive RHEL entitlements. I'm not sure how it's actually working now? |
Uh i forgot we had a |
Hahaha =) IIUC, there's no work to be done. If you look at the example builders, there's a sample config for RHEL8 (as well as RHEL9!) |
Oh i see; i completely forget about this 😆 |
I think so! yes |
/close |
@FedeDP: Closing this issue. In response to this:
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. |
Motivation
This comment explains well - IMHO - why the community might benefit from having a set of prebuilt Falco drivers for RHCOS.
To have such prebuilt drivers, we need a driverkit builder for RHCOS, first of all.
Feature
Create a builder for RHCOS.
The text was updated successfully, but these errors were encountered: