Osquerybeat: add extension uptycs/kubequery #7
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
This submodule includes the uptycs/kubequery repository within beats. This repository implements an osquery extension for Kube API information, and will be used by osquerybeat for this purpose.
The new WorkDir option added to the build library gives an option to change the current working directory before performing builds.
Also added kubequery binaries and such to .gitignore
Minor changes allow osquerybeat to support multiple 'required' extensions instead of just osquery-extension`. kubequery is added as a required extension.
amirbenun
force-pushed
the
master
branch
2 times, most recently
from
11f3b3c
to
e8023f6
Compare
|
Can we close it? @yashtewari |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This is a candidate PR to integrate https://github.com/Uptycs/kubequery into osquerybeat as an extension.
This is a work in progress.
Why is it important?
There are some teams, such as Cloud Security Posture, who need Kube API information to be sent from client clusters to Elasticsearch. Leveraging the existing open source extension https://github.com/Uptycs/kubequery and combining it with osquerybeat is a good way to achieve this.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
The changes done to achieve this are broadly as follows. Please advise for each of them if its the best way forward.
WorkDirto the beats build library. This allows for running Go build in a specific working directory, an option that I couldn't find in the library.How to test this PR locally
mage buildfor osquerybeat should show that it's building kubequery as well, and the binary for the extension should show up in the osquerybeat directory.Running the osquerybeat binary should show debug logs for kubequery plugins being registered, or errors if for example the Kube configuration file is not present/doesn't work.
Related issues
Use cases
Screenshots
Logs