-
Notifications
You must be signed in to change notification settings - Fork 169
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
refactor(userspace/libsinsp)!: remove legacy metadata clients for k8s and mesos #1478
Conversation
Signed-off-by: Jason Dellaluce <[email protected]>
Signed-off-by: Jason Dellaluce <[email protected]>
/milestone 0.14.0 |
Uh a small cleanup over here. 🤣 |
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.
😍
/approve
LGTM label has been added. Git tree hash: 0f568701a6ad36e2d0e1e5c95a5f8489ff014607
|
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP, jasondellaluce The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
In coordination with @Andreagit97 and @alacuku with regards to falcosecurity/falco#2973 and falcosecurity/falco#2763, this PR introduces the breaking changes required to removing the metadata clients of k8s and mesos from our codebase.
This removes all the files related to the implementation of the clients, plus all the code related to them in other classes (such as
sinsp
and filterchecks). This preserves thek8s.*
andmesos.*
filterchecks classes, which will be cleaned up in a future PR due to some additional challenges specific to them.Which issue(s) this PR fixes:
Special notes for your reviewer:
Removing these 25k LOC gives me quite a trill and a totally expected feeling of joy.
Does this PR introduce a user-facing change?: