-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat(integrations): add the falco integrations from the main falco repo #3
Conversation
start to move the non-official and community maintained integrations of falco from the main repository. Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
3e74b64
to
b64b152
Compare
/cc @leodido |
LGTM! |
/check-dco |
integrations/anchore-falco/README.md
Outdated
### Build the image | ||
|
||
``` | ||
docker build -t sysdig/anchore-falco . |
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.
Can we please fix such occurrences? :)
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.
If it's what you mean, I didn't find a Docker hub repository in the falcosecurity organization as for the event-generator. It should still be created, right?
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.
Since there are no other references to sysdig/anchore-falco
besides these in the README, I would suggest to just rewrote the instruction in order to use a local image (eg. anchore-falco
).
IMHO, it would be enough. If it was actively maintained and required a new repo, we will create it later.
integrations/anchore-falco/README.md
Outdated
docker run --rm -e ANCHORE_CLI_USER=<user-for-custom-anchore-engine> \ | ||
-e ANCHORE_CLI_PASS=<password-for-user-for-custom-anchore-engine> \ | ||
-e ANCHORE_CLI_URL=http://<custom-anchore-engine-host>:8228/v1 \ | ||
sysdig/anchore-falco |
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.
And 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.
The same as above
spec: | ||
containers: | ||
- name: falco-event-generator | ||
image: sysdig/falco-event-generator:latest |
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 needs probably to be:
- renamed
- coordinate with the new event-generator at https://github.com/falcosecurity/event-generator
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.
I think that it can be considered done :)
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.
Atm, falcosecurity/event-generator
is not yet ready, although a test image already exists.
@leodido WDYT ?
We may keep this on hold until dependant issues are solved. Regarding the event-generator
, I guess it will take another week or so.
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.
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.
@leogr we'll keep the sysdig one for now? Or we can wait for a release of the Docker image v0.1.0? Thank you!
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.
You are welcome!
It's released on Docker Hub too, see my review below
# - name: FALCOCTL_FALCO_PROBE_URL | ||
# value: | ||
# - name: FALCOCTL_FALCO_PROBE_REPO | ||
# value: "https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/" |
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 URL can be left as is for now (but it'll need to be updated soon :))
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.
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.
I agree @leogr
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.
Some changes about names, nothing serious :)
Thanks for helping us Max! 🤗
update integrations' version with that of falco's master branch. Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
Sure @leodido ! I just replied to the specific reviews for clarifications and updated this branch because it was out-of-sync with the Falco repo's master branch. |
…itory replace the sysdig organization with the falcosecurity one Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
…odes sync kubernetes deployment and jobs specs from the event-generator git repository Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
fed9743
to
d461daf
Compare
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.
Please, check out my suggestions!
Thank you!
remove references to remote image published on docker hub Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
remove references to sysdig remote repository Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
remove references to remote image published on docker hub Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
- run only syscall, otherwise also the k8saudit events collection will run - run inside loop Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
6a739f0
to
be6eb63
Compare
- run only syscall, otherwise also the k8saudit events collection will run Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
- run only syscall, otherwise also the k8saudit events collection will run - run inside loop Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
- run only syscall, otherwise also the k8saudit events collection will run Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
set the event-generator github repo https url Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
refer to the official documentation for samples, remove duplicates Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
refer to the official documentation for samples, remove duplicates Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
refer to the official documentation for samples, remove duplicates Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com> Co-Authored-By: Leonardo Grasso <me@leonardograsso.com>
remove references to local kubernetes config samples, instead refer to the official repo Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
remove references to local kubernetes config samples, instead refer to the official repo Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
remove kubernetes event-generator config samples from falco k8s deployment integration, instead refer to the official repo Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
054d1cf
to
4c35201
Compare
remove kubernetes event-generator config samples from falco k8s daemonset integration, instead refer to the official repo Signed-off-by: maxgio92 <massimiliano.giovagnoli.1992@gmail.com>
Hi @leogr, I implemented the suggestions and then cleaned the event-generator sample configurations for consistency; updated the documentation to refer to the new official event-generator's repo. |
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.
LGTM now
thanks @maxgio92
LGTM label has been added. Git tree hash: 6c0e736ff8c61472b935c1592f08ba12148ea2c1
|
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.
Approving to unblock and merge it.
FYI the initcontainer in the k8s examples should be updated.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leodido, leogr 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 |
start to move the non-official and community maintained integrations of falco from the main
repository.