Add k8s event generator resources #1088
Merged
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
Add a Daemonset yaml that allows running the falco event generator on syscalls. It will run on any non-master node. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
Add a deployment yaml that allows running the event generator in a k8s cluster: - Change the event generator to create/delete objects in a namespace "falco-eg-sandbox" instead of "falco-event-generator". That way you separate the generator from the resources it modifies (mostly, the exception being the rolebinding). - Create a serviceaccount, clusterrole, and rolebinding that allows the event generator to create/list/delete objects in the falco-eg-sandbox namespace. The list of permissions is fairly broad mostly so the event generator can delete all resources without explicitly naming them. The binding does limit permissions to the falco-eg-sandbox namespace, though. A one-line way to run this would be: kubectl create namespace falco-event-generator && \ kubectl create namespace falco-eg-sandbox && \ kubectl apply -f event-generator-role-rolebinding-serviceaccount.yaml && \ kubectl apply -f event-generator-k8saudit-deployment.yaml I haven't actually pushed a new docker image to replace the current event generator yet--the deployment yaml refers to a placeholder falcosecurity/falco-event-generator:eg-sandbox image. Once the review is done I'll rebase this to change the image to latest before merging. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
mstemm
force-pushed
the
add-k8s-event-generator-resources
branch
from
94945dc to
cba422e
Compare
|
I also updated the docs to reflect these changes: falcosecurity/falco-website#163 |
|
/milestone 0.21.0 |
|
LGTM label has been added. Git tree hash: 59f6ee9bf4edabecc6fdbd9fdd740fb461ac9e21
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fntlnz, kris-nova 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 |
mstemm
added a commit
that referenced
this pull request
Mar 12, 2020
I had a bug in #1088 where the image name for the event generator was pointing to a temporary tag instead of latest. This switches the image name back to latest. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
poiana
pushed a commit
that referenced
this pull request
Mar 12, 2020
I had a bug in #1088 where the image name for the event generator was pointing to a temporary tag instead of latest. This switches the image name back to latest. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
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 type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area integrations
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?: