Add Tetragon talk from Kubecon NA

[daxmc99]

This talk compares Tetragon with other popular security tools. Tetragon comes out on top in this comparison

Description

I found this talk useful for understanding Tetragon and aided my choice in understanding the observability tool landscape.
However, this talk is not explicitly focused on Tetragon and instead offers a comparison.
I find tools that offer comparisons to be valuable to understand if they are worth pursuing.

Changelog

Add link to Kubecon NA 2024 talk discussing Tetragon

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	4da3fb6
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/6787f1edbf0a3d0008d1abe6
😎 Deploy Preview	https://deploy-preview-3303--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mtardy]

Thanks!

[mtardy]

Thanks for the patch! However, it looks like your commit is not signed-off, to improve tracking of who did what, the Tetragon project uses a "sign-off" procedure which you can learn more about in the Cilium project documentation.

Concretely it consists of adding your real name and an email address to your git config and using git commit -s to write your commit message. You can use git commit --amend -s to add the signature to existing commits.

See more details on how to comply with the "sign-off" procedure

To add your name and email to your git config:

git config user.email "[email protected]"
git config user.name "firstname lastname"

Note: add the --global flag after config to configure this by default for repositories on your host.

Then you can use for new commits:

git commit -s

Or for existing commits on which you want to add the signed-off-by statement:

git commit --amend -s

For more information, see this extract from git-commit(1) man page regarding the -s flag:

-s, --signoff, --no-signoff
   Add a Signed-off-by trailer by the committer at the end of the commit log
   message. The meaning of a signoff depends on the project to which you're
   committing. For example, it may certify that the committer has the rights to
   submit the work under the project's license or agrees to some contributor
   representation, such as a Developer Certificate of Origin. (See
   http://developercertificate.org for the one used by the Linux kernel and Git
   projects.) Consult the documentation or leadership of the project to which
   you're contributing to understand how the signoffs are used in that project.

   The --no-signoff option can be used to countermand an earlier --signoff
   option on the command line.

[daxmc99]

@mtardy Whoops, signed-off now.

Thank you!