-
Notifications
You must be signed in to change notification settings - Fork 139
feat(components): add eBPF Summit: Hackathon Edition landing page #755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
doniacld
wants to merge
1
commit into
ebpf-io:main
Choose a base branch
from
doniacld:pr/doniacld/ebpf-summit-hackathon-edition-2025
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| # Contributing changes to [ebpf.io](https://ebpf.io/) | ||
| # Contributing changes to [ebpf.io](https://ebpf.io/) | ||
|
|
||
| :bee: Thanks for your help improving the project! We are open to any contribution from the community and would love to have you help us make the website better. | ||
|
|
||
| ## Blog posts | ||
|
|
||
| Our blog page includes original blog posts about eBPF, as well as links to external articles hosted elsewhere. If you'd like to submit a blog post to ebpf.io please check that your article meets the following guidelines. We welcome PRs, but if you'd like to discuss a possible submission first please message us on slack in the [#ebpf-website channel])https://cilium.slack.com/archives/C03TH72HCBW) or email us [[email protected]]([email protected]). | ||
| Our blog page includes original blog posts about eBPF, as well as links to external articles hosted elsewhere. If you'd like to submit a blog post to ebpf.io please check that your article meets the following guidelines. We welcome PRs, but if you'd like to discuss a possible submission first please message us on slack in the [#ebpf-website channel])<https://cilium.slack.com/archives/C03TH72HCBW>) or email us [[email protected]]([email protected]). | ||
|
|
||
| Please see the [full ebpf.io Blog Guidelines](https://github.com/ebpf-io/ebpf.io-website/blob/master/blog-guidelines.md), but in short: | ||
| Please see the [full ebpf.io Blog Guidelines](https://github.com/ebpf-io/ebpf.io-website/blob/master/blog-guidelines.md), but in short: | ||
|
|
||
| * Posts should be valuable content for the eBPF community | ||
| * Posts should not be vendor pitches, and should focus on the open source eBPF project | ||
| * Posts hosted on ebpf.io should be original content. You can submit a link to an external article instead of copying content. | ||
| * All content is contributed under the CC-BY-4.0 license | ||
| - Posts should be valuable content for the eBPF community | ||
| - Posts should not be vendor pitches, and should focus on the open source eBPF project | ||
| - Posts hosted on ebpf.io should be original content. You can submit a link to an external article instead of copying content. | ||
| - All content is contributed under the CC-BY-4.0 license | ||
|
|
||
| Links to posts hosted elsewhere are also given the **External** tag automatically. | ||
| Links to posts hosted elsewhere are also given the **External** tag automatically. | ||
|
|
||
| See the [Blog Guidelines](https://github.com/ebpf-io/ebpf.io-website/blob/master/blog-guidelines.md) for documentation on how to submit a post or external link. | ||
| See the [Blog Guidelines](https://github.com/ebpf-io/ebpf.io-website/blob/master/blog-guidelines.md) for documentation on how to submit a post or external link. | ||
|
|
||
| ## Other changes | ||
|
|
||
|
|
||
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community. | |
| Examples of behavior that contributes to a positive environment for our | ||
| community include: | ||
|
|
||
| * Demonstrating empathy and kindness toward other people | ||
| * Being respectful of differing opinions, viewpoints, and experiences | ||
| * Giving and gracefully accepting constructive feedback | ||
| * Accepting responsibility and apologizing to those affected by our mistakes, | ||
| - Demonstrating empathy and kindness toward other people | ||
| - Being respectful of differing opinions, viewpoints, and experiences | ||
| - Giving and gracefully accepting constructive feedback | ||
| - Accepting responsibility and apologizing to those affected by our mistakes, | ||
| and learning from the experience | ||
| * Focusing on what is best not just for us as individuals, but for the | ||
| - Focusing on what is best not just for us as individuals, but for the | ||
| overall community | ||
|
|
||
| Examples of unacceptable behavior include: | ||
|
|
||
| * The use of sexualized language or imagery, and sexual attention or | ||
| - The use of sexualized language or imagery, and sexual attention or | ||
| advances of any kind | ||
| * Trolling, insulting or derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or email | ||
| - Trolling, insulting or derogatory comments, and personal or political attacks | ||
| - Public or private harassment | ||
| - Publishing others' private information, such as a physical or email | ||
| address, without their explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| - Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Enforcement Responsibilities | ||
|
|
@@ -60,7 +60,7 @@ representative at an online or offline event. | |
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported to the community leaders responsible for enforcement at | ||
| [email protected]. | ||
| <[email protected]>. | ||
| All complaints will be reviewed and investigated promptly and fairly. | ||
|
|
||
| All community leaders are obligated to respect the privacy and security of the | ||
|
|
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban. | |
| ### 4. Permanent Ban | ||
|
|
||
| **Community Impact**: Demonstrating a pattern of violation of community | ||
| standards, including sustained inappropriate behavior, harassment of an | ||
| standards, including sustained inappropriate behavior, harassment of an | ||
| individual, or aggression toward or disparagement of classes of individuals. | ||
|
|
||
| **Consequence**: A permanent ban from any sort of public interaction within | ||
|
|
||
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,13 +27,13 @@ issue of the eBPF Updates, and Happy New Year! | |
|
|
||
| Let's start with some news from companies working on and with eBPF. | ||
|
|
||
| {/*2020-12-20*/} | ||
| {/_2020-12-20_/} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a tricky to review. Looks like there's lots of unrelated changes being made |
||
|
|
||
| - Microsoft is working on an eBPF-based monitoring tool for Linux: | ||
|
|
||
| <blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">We're working on eBPF-based Sysmon for Linux that has same filtering and output schema (where applicable) as Sysmon For Windows. Shooting for a preview in February. <a href="https://t.co/l0BTkVXac1">pic.twitter.com/l0BTkVXac1</a></p>— Mark Russinovich (@markrussinovich) <a href="https://twitter.com/markrussinovich/status/1340737856201879552?ref_src=twsrc%5Etfw">December 20, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> | ||
|
|
||
| {/*2021-01-11*/} | ||
| {/_2021-01-11_/} | ||
|
|
||
| - [_Isovalent Looks to Transform Container Networking With eBPF_](https://containerjournal.com/topics/container-networking/isovalent-container-networking-in-2021-using-ebpf/), | ||
| from Mike Vizard. | ||
|
|
@@ -42,7 +42,7 @@ Let's start with some news from companies working on and with eBPF. | |
| Cilium and Isovalent. The author foresees important changes for cloud-native | ||
| environments in terms of networking, security, and observability. | ||
|
|
||
| {/*2021-01-12*/} | ||
| {/_2021-01-12_/} | ||
|
|
||
| - [Kubernetes Podcast - _Episode #133: Cilium, with Thomas Graf_](https://kubernetespodcast.com/episode/133-cilium/), | ||
| from Craig Box and Adam Glick. | ||
|
|
@@ -55,14 +55,14 @@ Let's start with some news from companies working on and with eBPF. | |
| possible support for eBPF on Windows, follow. “Twenty-two years on, do you | ||
| think you finally fixed networking?” Future will tell. | ||
|
|
||
| {/*2021-01-18*/} | ||
| {/_2021-01-18_/} | ||
|
|
||
| - Optimyze.cloud [announced in a tweet](https://twitter.com/OptimyzeCloud/status/1351203905850519557) | ||
| that they are working on a “_Full-system lightweight continuous profiling for | ||
| Linux Kernel, C/C++, Rust, Golang, Python, JVM, PHP (with Ruby and Node | ||
| planned for the future)_”, apparently based on eBPF. | ||
|
|
||
| {/*2021-01-18*/} | ||
| {/_2021-01-18_/} | ||
|
|
||
| - [_Securing Containerized Environments with eBPF_](https://www.tag-cyber.com/advisory/articles/securing-containerized-environments-with-ebpf), | ||
| from Adam LeWinter. | ||
|
|
@@ -76,7 +76,7 @@ Let's start with some news from companies working on and with eBPF. | |
|
|
||
| ### Introductory Resources | ||
|
|
||
| {/*2020-11-25*/} | ||
| {/_2020-11-25_/} | ||
|
|
||
| - [_BPF: The future of configs_](https://blog.habets.se/2020/11/BPF-the-future-of-configs.html), | ||
| from Thomas Habets. | ||
|
|
@@ -89,7 +89,7 @@ Let's start with some news from companies working on and with eBPF. | |
| customization of TCP parameters, and more. This is a good read to help | ||
| understand what is at stake with eBPF. | ||
|
|
||
| {/*2020-12-11*/} | ||
| {/_2020-12-11_/} | ||
|
|
||
| - [_Linux Networking - eBPF, XDP, DPDK, VPP - What does all that mean?_](https://media.ccc.de/v/vnog-4-linux-networking-ebpf-xdp-dpdk-vp), | ||
| from Andree Toonk. | ||
|
|
@@ -102,7 +102,7 @@ Let's start with some news from companies working on and with eBPF. | |
| from the Linux kernel. Andree also covers this topic | ||
| [on his blog](https://toonk.io/tag/networking/index.html). | ||
|
|
||
| {/*2020-12-19*/} | ||
| {/_2020-12-19_/} | ||
|
|
||
| - [_File Integrity Monitoring using eBPF_](https://www.devseccon.com/file-integrity-monitoring-using-ebpf-secadvent-day-19/), | ||
| from Sylvain Baubeau. | ||
|
|
@@ -113,7 +113,7 @@ Let's start with some news from companies working on and with eBPF. | |
| performance overhead. eBPF addresses most of them, and provides performance | ||
| and over overall improvements to the feature. | ||
|
|
||
| {/*2021-01-19*/} | ||
| {/_2021-01-19_/} | ||
|
|
||
| - [_Introduction to eBPF_](https://oswalt.dev/2021/01/introduction-to-ebpf/), | ||
| from Matt Oswalt. | ||
|
|
@@ -130,7 +130,7 @@ Let's start with some news from companies working on and with eBPF. | |
|
|
||
| ### Deep Dives | ||
|
|
||
| {/*2020-12-23*/} | ||
| {/_2020-12-23_/} | ||
|
|
||
| - [Cilium documentation on _The Kubernetes Networking Guide_](https://k8s.networkop.co.uk/cni/cilium/), | ||
| from Michael Kashin. | ||
|
|
@@ -143,7 +143,7 @@ Let's start with some news from companies working on and with eBPF. | |
| This is a recommended read if you want a glimpse of advanced networking with | ||
| eBPF. | ||
|
|
||
| {/*2020-12-24*/} | ||
| {/_2020-12-24_/} | ||
|
|
||
| - [_How to Trace Linux System Calls in Production with Minimal Impact on Performance_](https://pingcap.com/blog/how-to-trace-linux-system-calls-in-production-with-minimal-impact-on-performance), | ||
| from Wenbo Zhang. | ||
|
|
@@ -301,18 +301,18 @@ or maps of maps. | |
|
|
||
| The enthusiasm about eBPF is strong: | ||
|
|
||
| {/*2020-12-19*/} | ||
| {/_2020-12-19_/} | ||
|
|
||
| <blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">The more I dig into eBPF the more it feels like there's a platform shift coming to parts of the market. The tone is reminiscent of early discussions around LXC and Docker. Exciting to watch and see what happens next!</p>— Alex Salazar (@TheMostlyGreat) <a href="https://twitter.com/TheMostlyGreat/status/1340361763112497152?ref_src=twsrc%5Etfw">December 19, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> | ||
|
|
||
| {/*2021-01-22*/} | ||
| {/_2021-01-22_/} | ||
|
|
||
| <blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">eBPF has to be one of the most fun things I’ve tinkered with in a while. The possibilities are really exciting! <a href="https://twitter.com/hashtag/infosec?src=hash&ref_src=twsrc%5Etfw">#infosec</a> <a href="https://twitter.com/hashtag/informationsecurity?src=hash&ref_src=twsrc%5Etfw">#informationsecurity</a> <a href="https://twitter.com/hashtag/linux?src=hash&ref_src=twsrc%5Etfw">#linux</a> <a href="https://twitter.com/hashtag/blueteam?src=hash&ref_src=twsrc%5Etfw">#blueteam</a></p>— Deathzone707 (@dunn707) <a href="https://twitter.com/dunn707/status/1352434717983817729?ref_src=twsrc%5Etfw">January 22, 2021</a></blockquote> | ||
| <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> | ||
|
|
||
| Below is a thread asking how to improve eBPF usability: | ||
|
|
||
| {/*2020-12-27*/} | ||
| {/_2020-12-27_/} | ||
|
|
||
| <blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">What would make eBPF more accessible/usable to you? 👇</p>— Jaana Dogan ヤナ ドガン (@rakyll) <a href="https://twitter.com/rakyll/status/1343072598901420034?ref_src=twsrc%5Etfw">December 27, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> | ||
|
|
||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The linter fixed me a bunch if things. I will move them to another PR.