sig-security icon indicating copy to clipboard operation
sig-security copied to clipboard

REQUEST: Request a Learning session for Tetragon

Open mtardy opened this issue 2 years ago • 13 comments
trafficstars

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!! 👋

mtardy avatar May 04 '23 14:05 mtardy

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

PushkarJ avatar May 04 '23 21:05 PushkarJ

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

mtardy avatar May 08 '23 08:05 mtardy

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 avatar May 17 '23 16:05 PushkarJ

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

PushkarJ avatar Jun 06 '23 20:06 PushkarJ

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

Personally yes, I'll propose and double confirm.

mtardy avatar Jun 06 '23 20:06 mtardy

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

PushkarJ avatar Jun 14 '23 15:06 PushkarJ

@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 avatar Jun 14 '23 23:06 mtardy

I think the 19th of July would be good.

mtardy avatar Jun 30 '23 14:06 mtardy

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

Thanks for your patience with this :)

PushkarJ avatar Jul 01 '23 02:07 PushkarJ

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

iamvolvo avatar Jul 24 '23 13:07 iamvolvo

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jan 25 '24 03:01 k8s-triage-robot

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

/remove-lifecycle stale

PushkarJ avatar Jan 28 '24 23:01 PushkarJ

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Apr 28 '24 00:04 k8s-triage-robot

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:

  • 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:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar May 28 '24 00:05 k8s-triage-robot

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

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

/close not-planned

k8s-triage-robot avatar Jun 27 '24 01:06 k8s-triage-robot

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

In response to this:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

k8s-ci-robot avatar Jun 27 '24 01:06 k8s-ci-robot

/reopen

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

mtardy avatar Jun 27 '24 09:06 mtardy

@mtardy: Reopened this issue.

In response to this:

/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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

k8s-ci-robot avatar Jun 27 '24 09:06 k8s-ci-robot

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

tabbysable avatar Jul 01 '24 21:07 tabbysable