Néstor Salceda e4ffa55d58 Add a playbook which starts to capturing data using Sysdig and uploads capture to a s3 bucket (#414) ...

* Fix spec name

* Add a playbook for capturing stuff using sysdig in a container

* Add event-name to job name for avoid collisions among captures

* Implement job for starting container in Pod in Kubernetes Client

We are going to pick data for all Pod, not limited to one container

* Use sysdig/capturer image for capture and upload to s3 the capture

* There is a bug with environment string splitting in kubeless

https://github.com/kubeless/kubeless/issues/824

So here is a workaround which uses multiple --env flags, one for each
environment.

* Use shorter job name. Kubernetes limit is 64 characters.

* Add a deployable playbook with Kubeless for capturing stuff with Sysdig

* Document the integration with Sysdig capture

* Add Dockerfile for creating sysdig-capturer

2018-10-11 16:55:40 -07:00

..

anchore-falco

Add a README

2018-07-12 17:56:59 +02:00

k8s-using-daemonset

Move kubernetes manifests from examples to integrations

2018-07-13 13:08:38 +02:00

kubernetes-response-engine

Add a playbook which starts to capturing data using Sysdig and uploads capture to a s3 bucket (#414)

2018-10-11 16:55:40 -07:00

logrotate

Move logrotate from examples to integrations

2018-07-13 13:02:26 +02:00

puppet-module

Change license to Apache 2.0 (#419)

2018-09-20 11:47:10 -07:00