Skip to content

Conversation

irozzo-1A
Copy link
Contributor

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@poiana
Copy link
Contributor

poiana commented Sep 17, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: irozzo-1A
Once this PR has been reviewed and has the lgtm label, please assign molter73 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

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

Copy link

Please double check driver/API_VERSION file. See versioning.

/hold

@poiana
Copy link
Contributor

poiana commented Sep 17, 2025

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

  • 9a4c7ab Adapt the cmake scripts to easily integrate with vcpkg
  • c960790 Start adapting GH workflows
  • eeafe43 Fix vcpkg installation
  • 2a6266c Install vcpkg dependencies

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-sigs/prow repository. I understand the commands that are listed here.

@ekoops
Copy link
Contributor

ekoops commented Sep 18, 2025

Wow! This would be great! I'm setting the milestone to be 0.22.0, but we can delay this if we don't feel comfortable with it! 😄

/milestone 0.22.0

@poiana poiana added this to the 0.22.0 milestone Sep 18, 2025
@Molter73
Copy link
Contributor

Haven't gone through the PR yet, but preemptively asking just in case. We build the libraries in hermetic environments where we pre-install the dependencies we need and won't be able to have vcpkg reach out to download the dependencies itself. Am I correct thinking this new approach will also work for this use case? As long as the packages are installed with the required cmake files to find the packages, of course.

Great PR BTW! Huge fan of package managers in general!

Copy link
Contributor

@terror96 terror96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just small, quick findings.

- name: Install deps ⛓️
run: |
apk add g++ gcc cmake make git bash perl linux-headers autoconf automake m4 libtool elfutils-dev libelf-static patch binutils clang llvm
apk add build-base cmake ninja zip unzip curl git curl tar g++ gcc make bash perl linux-headers autoconf automake m4 libtool elfutils-dev libelf-static patch binutils clang llvm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
apk add build-base cmake ninja zip unzip curl git curl tar g++ gcc make bash perl linux-headers autoconf automake m4 libtool elfutils-dev libelf-static patch binutils clang llvm
apk add build-base cmake ninja zip unzip curl git tar g++ gcc make bash perl linux-headers autoconf automake m4 libtool elfutils-dev libelf-static patch binutils clang llvm

apt update && apt install -y --no-install-recommends curl ca-certificates build-essential git clang llvm pkg-config autoconf automake libtool libelf-dev wget libtbb-dev libjq-dev libjsoncpp-dev protobuf-compiler libgtest-dev libprotobuf-dev linux-headers-${{ matrix.arch }}
apt update && apt install -y --no-install-recommends curl zip unzip tar ca-certificates build-essential git clang llvm pkg-config autoconf automake libtool libelf-dev wget libtbb-dev libjq-dev libjsoncpp-dev protobuf-compiler libgtest-dev libprotobuf-dev linux-headers-${{ matrix.arch }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra spaces here

@irozzo-1A
Copy link
Contributor Author

Haven't gone through the PR yet, but preemptively asking just in case. We build the libraries in hermetic environments where we pre-install the dependencies we need and won't be able to have vcpkg reach out to download the dependencies itself. Am I correct thinking this new approach will also work for this use case? As long as the packages are installed with the required cmake files to find the packages, of course.

Great PR BTW! Huge fan of package managers in general!

Yep @Molter73 , you're correct this approach is supposed to work with pre-installed dependencies too.

@irozzo-1A
Copy link
Contributor Author

Just small, quick findings.

Thanks @terror96 for the early review! I have still some work to do here before it gets ready and it's a low priority task for me at the moment, but I'll let you know when it's in good shape 😉

@terror96
Copy link
Contributor

Just small, quick findings.

Thanks @terror96 for the early review! I have still some work to do here before it gets ready and it's a low priority task for me at the moment, but I'll let you know when it's in good shape 😉

No worries. I'll give it a better look later...

@terror96 terror96 closed this Sep 19, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in Falco Roadmap Sep 19, 2025
@terror96 terror96 reopened this Sep 19, 2025
@github-project-automation github-project-automation bot moved this from Done to In progress in Falco Roadmap Sep 19, 2025
@terror96
Copy link
Contributor

:( Sorry, still having problems in selecting the right button...

@ekoops
Copy link
Contributor

ekoops commented Sep 24, 2025

/milestone 0.23.0

@poiana poiana removed this from the 0.22.0 milestone Sep 24, 2025
@poiana poiana added this to the 0.23.0 milestone Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

5 participants