forked from cncf/mentoring
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
1 changed file
with
81 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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 |
---|---|---|
|
@@ -181,6 +181,58 @@ The objective of this project is to enhance the compliance of the Karmada certif | |
- Zhen Chang (@XiShanYongYe-Chang, [email protected]) | ||
- Upstream Issue: https://github.com/karmada-io/dashboard/issues/182 | ||
|
||
### Kmesh | ||
|
||
#### Re-design and implement the Kmesh website | ||
|
||
- Description: The existing Kmesh website theme struggled to meet existing development needs. Therefore, there is a need to redesign the Kmesh website and replace the theme to make it easier for developers to add documentation. Development instructions for the website are also provided. | ||
- Expected Outcome: | ||
- The website has more readable documentation, covering user cases, developer courses, etc. | ||
- Docs about how to develop website. | ||
- Recommended Skills: JS, Kmesh, Html | ||
- Mentor(s): | ||
- ZhenCheng Li(@LiZhenCheng9527, [email protected]), | ||
- Zhonghu Xu(@hzxuzhonghu, [email protected]) | ||
- Upstream Issue: https://github.com/kmesh-net/website/issues/115 | ||
|
||
#### Kmesh eBPF unit test | ||
|
||
- Description: As the community features continue to expand, the number of eBPF programs in the data plane has increased. Due to the inherent limitations of eBPF (third-state encoding, neither user space nor kernel space, running in a kernel virtual machine with a dedicated instruction set), Kmesh implements complex governance logic through features like tail call and map-in-map, which poses challenges for data plane quality protection. | ||
eBPF, a recently introduced programmable technology in the kernel, currently has an immature ecosystem. The industry is actively exploring eBPF testing capabilities (e.g., Unit Testing eBPF). This project aims to develop an eBPF UT testing framework in conjunction with the Kmesh project to ensure the quality of the Kmesh data plane. | ||
- Expected Outcome: | ||
- Export Kmesh eBPF programs to support UT test case. | ||
- Export design documentation for eBPF UT tests | ||
- Recommended Skills: C, eBPF, (go) | ||
- Mentor(s): | ||
- Xin Liu(@bitcoffeeiux, [email protected]) | ||
- Changye Wu(@nlgwcy, [email protected]) | ||
- Upstream Issue: https://github.com/kmesh-net/kmesh/issues/1209 | ||
|
||
#### Add the Kmesh e2e Test | ||
|
||
- Description: Kmesh now has an e2e testing framework, but it only covers some of the usage scenarios for key features. More test cases need to be covered to ensure the stability of key features. | ||
- Expected Outcome: | ||
- e2e Test Cases | ||
- Documentation maintenance for e2e testing | ||
- Recommended Skills: go, Kmesh | ||
- Mentor(s): | ||
- Zengzeng Yao(@yaozegzeng, [email protected]) | ||
- Zhonghu Xu(@hzxuzhonghu, [email protected]) | ||
- Upstream Issue: https://github.com/kmesh-net/kmesh/issues/1210 | ||
|
||
#### Metrics for TCP Long Connection | ||
|
||
- Description: Currently, Kmesh metrics are only reported when a TCP connection is closed. In the case of long connections, it is not possible to know the status before the connection is closed. Therefore, we hope to add the capability to periodically report metrics for long connections. | ||
- Expected Outcome: | ||
- proposal | ||
- code | ||
- user guide. | ||
- Recommended Skills: go, c, eBPF | ||
- Mentor(s): | ||
- Changye wu(@nlgwcy, [email protected]) | ||
- ZhenCheng Li(@LiZhenCheng9527, [email protected]) | ||
- Upstream Issue: https://github.com/kmesh-net/kmesh/issues/1211 | ||
|
||
### KubeEdge | ||
|
||
#### Domain-specific large model benchmarks: the edge perspective | ||
|
@@ -379,6 +431,35 @@ find requirements from https://github.com/WebAssembly/component-model/tree/main/ | |
- Vivian Hu (@alabulei1, [email protected]) | ||
- Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3986 | ||
|
||
### Harbor | ||
|
||
#### Harbor CLI | ||
|
||
- Description: Harbor is a widely adopted container registry, and its initial CLI has been developed by LFX mentees. The goal is to extend this CLI by implementing additional functionalities and workflows that are currently only available in the Web UI. The CLI should be useful for Harbor administrators and users, especially to manage workflows within CI/CD pipelines. We seek a Golang-experienced mentee to enhance the CLI independently. | ||
- Expected Outcome: | ||
- Extend the Harbor CLI to include essential commands not yet implemented. | ||
- Add new features to improve Harbor management via the CLI, enabling robust workflows in CI/CD environments. | ||
- Recommended Skills: Golang, spf13/cobra | ||
- Mentor(s): | ||
- Vadim Bauer (@vad1mo, [email protected]) | ||
- Orlin Vasilev (@OrlinVasilev, [email protected]) | ||
- Prasanth Baskar (@bupd, [email protected]) | ||
- Upstream Issue: https://github.com/goharbor/harbor-cli/issues/315 | ||
|
||
#### Harbor Satellite | ||
|
||
- Description: Containers have extended beyond their traditional cloud environments, becoming increasingly prevalent in remote and edge computing contexts. These environments often lack reliable internet connectivity, posing significant challenges in managing and running containerized applications due to difficulties in fetching container images. To address this, the project aims to decentralize container registries, making them more accessible to edge devices. | ||
- Expected Outcome: | ||
The goal is to extend the proof of concept and demonstrate that such a solution practically works. | ||
Candidates should be able understanding and implementing the [image](https://github.com/opencontainers/image-spec) and [distribution spec](https://github.com/opencontainers/distribution-spec) | ||
to replicate images from a central registry to a registry on the edge location. | ||
- Recommended Skills: Golang, Container, Image-spec, Distribution-spec | ||
- Mentor(s): | ||
- Vadim Bauer (@vad1mo, [email protected]) | ||
- Orlin Vasilev (@OrlinVasilev, [email protected]) | ||
- Prasanth Baskar (@bupd, [email protected]) | ||
- Upstream Issue: https://github.com/goharbor/harbor/issues/21469 | ||
|
||
### Prometheus | ||
|
||
#### Get `PrometheusRemoteWriteReceiver` in OTel-Collector to Alpha Maturity | ||
|