Skip to content
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.

Sign up for GitHub

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

Add Cilium GSoC idea #879

Merged
merged 1 commit into from
Mar 14, 2023
Merged

Add Cilium GSoC idea #879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions summerofcode/2023.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,8 @@ If you are a project maintainer and consider mentoring during the GSoC 2023 cycl
* [Armada](#armada)
+ [Add Kubectl Plugin for Armada](#add-kubectl-plugin-for-armada)
+ [Build interfaces around Postgres for Armada](#build-interfaces-around-postgres-for-armada)
* [Cilium](#cilium)
+ [Remove dependencies from Tetragon](#remove-dependencies-from-tetragon)
* [Cloud Native Buildpacks](#cloud-native-buildpacks)
+ [The Need for Speed](#the-need-for-speed)
+ [Enhancements for Dockerfiles](#enhancements-for-dockerfiles)
Expand Down Expand Up @@ -108,6 +110,19 @@ If you are a project maintainer and consider mentoring during the GSoC 2023 cycl
- Difficulty: Hard
- Upstream Issue (URL): https://github.com/armadaproject/armada/issues/2121

### Cilium

#### Remove Dependencies From Tetragon

- Description: Tetragon can run both with and without Cilium on the same node. Some functionality, however, still depends on the Cilium agent being present. Specifically, Tetragon uses Cilium to retrieve the pod information for destination IPs for pods which are not local to the node. The goal of this project is to introduce this functionality on Tetragon. One approach would be for the Tetragon agent to keep information about all pods in the cluster, but this approach does not scale well due to the Kubernetes API server needing to propagate all pod information to all nodes. Instead, the plan is to introduce a new custom resource (CR) which is maintained by the Tetragon operator and provides a mapping from IPs to the small subset of pod information that Tetragon needs. The Tetragon operator will monitor pod information and update the resource as needed. Tetragon agents will watch this CR to provide pod information for destination IPs.

- Expected outcome: Cilium dependency is removed from Tetragon
- Recommended Skills: Go, Kubernetes
- Mentor(s): Michi Mutsuzaki, michi-covalent, michi@isovalent.com. Kornilios Kourtis, kkourt,kornilios@isovalent.com
- Expected project size: 350 Hours
- Difficulty: Medium
- Upstream Issue (URL): https://github.com/cilium/tetragon/issues/794

### Cloud Native Buildpacks

#### The Need for Speed
Expand Down