-
Notifications
You must be signed in to change notification settings - Fork 23
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
Use vanilla Falco #1343
Merged
Merged
Use vanilla Falco #1343
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Skipping CI for Draft Pull Request. |
a16b87a
to
376214b
Compare
376214b
to
db09a19
Compare
808394b
to
f8a8eed
Compare
0617786
to
068c0f2
Compare
|
ff480e3
to
88e1c15
Compare
0f329f0
to
b834dd2
Compare
b6837ad
to
2700d87
Compare
3eb4593
to
ead8ac4
Compare
11 tasks
ead8ac4
to
a8f6517
Compare
071b476
to
d9a6a31
Compare
Needed to include the arm64 builder image
One side effect of [1] is that procexit is not included by default any more if ppm_sc is not empty. Which means to continue receiving procexit we need to explicitly add it into the list of interesting events. procexit is essential for memory management, as its handlers perform threadinfo cache clean up. [1]: falcosecurity/libs#1001
Turn on Falco assert logging for all build types. Make _DEBUG dependent on the Debug build type, it would impact asserts logic when asserts logging is disabled.
If CMAKE_BUILD_TYPE is debug, the condition for stripping the binary is not invoked, and the resulting exit code is 1, stopping the build. Ignore this branch and return exit code 0.
dd22a13
to
61f438b
Compare
- s390x images are now built natively - ppc64le core-bpf is enabled - VM creation is consolidated in GHA - numerous improvements to ansible variables and multiarch VM creation
Stringy
reviewed
Jan 3, 2024
Stringy
reviewed
Jan 3, 2024
Stringy
reviewed
Jan 3, 2024
Stringy
reviewed
Jan 3, 2024
Stringy
reviewed
Jan 3, 2024
ovalenti
reviewed
Jan 4, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This overall looks good to me. Some parts are so much simpler 👍
Co-authored-by: Olivier Valentin <ovalenti@redhat.com>
Stringy
approved these changes
Jan 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
all-integration-tests
build-full-images
build-legacy-probes
integration-tests-trace-logging
Turn on additional logging in Collector
run-multiarch-builds
Run steps for non-x86 archs.
skip-built-drivers
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change makes it so collector compiles and runs using upstream Falco directly. There are a few minor tweaks still required in Falco itself, but they are things that are either on their way to upstream or should be real ease to upstream.
List of changes needed for vanilla to be compatible:
Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why you did not do so. (Valid reasons include "CI is sufficient" or "No testable changes")
In addition to reviewing your code, reviewers must also review your testing instructions, and make sure they are sufficient.
For more details, ref the Confluence page about this section.