search

kubernetes / sig-security

Process documentation, non-code deliverables, and miscellaneous artifacts of Kubernetes SIG Security
Apache License 2.0
166 stars 55 forks source link

REQUEST: Request a Learning session for Tetragon #90

Closed mtardy closed 3 months ago

mtardy commented 1 year ago

Please tell us a bit more about the topic

I would love to present Tetragon to people at SIG security tooling! It's an eBPF-based Security Observability and Runtime Enforcement software. In brief, it allows for process lifecycle observability by default and you can extend its capabilities by writing Kubernetes CRD in YAML (called TracingPolicy) that will be translated to eBPF programs to perform customized observability and enforcement.

I'm not exactly sure from which angle we want to present but I have some ideas :)!

Please share speaker details

Partially unsure. I think I will present but would love to have someone from the Tetragon team with me.

If speaker is confirmed, please share speaker availability

The next challenge will be to find a nice timeslot for the learning session!

Explain the benefits to the community that this session provides

The community would benefit from learning about this new open-source tool that solves security observability and enforcement problem. People are starting to realize that a lot of their security needs can be addressed with eBPF-powered software, but may not know how to get started. Introducing attendees to Tetragon and its TracingPolicy gives them an opportunity to get a bit familiar with eBPF security coming straight from the kernel through things they already know like Kubernetes custom resources. In addition, it will introduce them to some kernel concepts that they will need to understand for security, like syscalls, tracepoints, kprobes, etc, and how to leverage them in the context of Kubernetes clusters.

See you SIG security people!! 👋

PushkarJ commented 1 year ago

@mtardy thanks for filing this! Would May 24 work for you and the tetragon team?

mtardy commented 1 year ago

I proposed, I think it will be yes, let me some days to confirm again :)

PushkarJ commented 1 year ago

We are postponing this due to my unavailability to host on May 24. I am working with @mtardy to figure out the next date and will post an update here when I know more.

PushkarJ commented 1 year ago

@mtardy can you and the team present it for June 21 slot?

mtardy commented 1 year ago

@mtardy can you and the team present it for June 21 slot?

Personally yes, I'll propose and double confirm.

PushkarJ commented 1 year ago

@mtardy any luck confirming this yet with the rest of the team?

mtardy commented 1 year ago

@mtardy any luck confirming this yet with the rest of the team?

Yep, sorry for the late reply, I think it's not for the best because one of my team mate cannot join. Do you think we can do bpfd at this date and then tetragon maybe?

mtardy commented 1 year ago

I think the 19th of July would be good.

PushkarJ commented 1 year ago

Let's do it @mtardy ! Tetragon is on for July 19th.

Thanks for your patience with this :)

iamvolvo commented 1 year ago

Kind reminder to update the issue with a link to the recording when available :-)

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

PushkarJ commented 8 months ago

@tabbysable can you please add a link to July 19 2023 Tooling session as a comment?

/remove-lifecycle stale

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 3 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/sig-security/issues/90#issuecomment-2192873863): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
mtardy commented 3 months ago

/reopen

Might be a bit outdated now but I think we still don't have the link.

k8s-ci-robot commented 3 months ago

@mtardy: Reopened this issue.

In response to [this](https://github.com/kubernetes/sig-security/issues/90#issuecomment-2194267181): >/reopen > >Might be a bit outdated now but I think we still don't have the link. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
tabbysable commented 3 months ago

I think you probably have the link now! thanks for keeping track of this and your patience with the upload backlog!

https://www.youtube.com/watch?v=4ifEI1n4lY4