add two jaeger mentorship projects (#1275)

Signed-off-by: Jonah Kowall <jkowall@kowall.net>

programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md

@@ -210,3 +210,94 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
   - Michael Yuan (@juntao, michael@secondstate.io)
   - Hung-Ying, Tai (@hydai, hydai@secondstate.io)
 - Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3580
+
+### Jaeger
+#### Jaeger v2 Kubernetes Operator  
+- Description: Jaeger-v1 has its own Kubernetes Operator (https://github.com/jaegertracing/jaeger-operator) which deploys Jaeger components according to the deployment strategy as well as the database or datastore. The goal of this project is to develop a new operator for [Jaeger-v2](https://github.com/jaegertracing/jaeger/issues/4843) that achieves feature parity with the v1 operator while introducing improvements and new capabilities. This new operator will leverage the [OpenTelemetry operator](https://github.com/open-telemetry/opentelemetry-operator) for Jaeger-v2 deployment while maintaining and enhancing the storage management features from the v1 operator.
+- Expected Outcome: By the end of this project, we aim to achieve full feature parity between the Jaeger v2 operator and the v1 operator, with the added benefits of OpenTelemetry integration. The new operator will provide a seamless experience for users, maintaining the robustness and flexibility of v1 while introducing the advantages of v2 and OpenTelemetry.
+- Recommended Skills: Go, scripting, kubernetes, operator framework, CI/CD
+- Mentor(s):  
+  - Yuri Shkuro (@yurishkuro, github@ysh.us)
+  - Jonah Kowall (@jkowall, jkowall@kowall.net 
+- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5766
+#### Jaeger v2 Helm Chart 
+- Description: Currently, Jaeger v1 has an official Helm chart (https://github.com/jaegertracing/helm-charts), but there isn't one yet for Jaeger v2. The goal of this project is to develop a comprehensive Helm chart for Jaeger v2 that allows for easy deployment and management of Jaeger v2 components in Kubernetes environments. This chart should provide flexibility in configuration, support various deployment scenarios, and integrate well with the new architecture of Jaeger v2. Relevant links:
+ - Jaeger: https://www.jaegertracing.io/
+ - Jaeger v2 announcement: https://medium.com/jaegertracing/announcing-jaeger-v2-a-new-architecture-for-distributed-tracing-e87b1fea0fe4
+ - Helm: https://helm.sh/
+ - Existing Jaeger Helm charts: https://github.com/jaegertracing/helm-charts
+- Expected Outcome: By the end of this project, we aim to have a production-ready Helm chart for Jaeger v2 that is:
+ - Fully functional and tested on the current version of Kubernetes
+ - Well-documented with clear usage instructions and examples
+ - Flexible enough to support a wide range of deployment scenarios
+ - Ready for submission to the official Jaeger Helm chart repository
+- Recommended Skills: Go, scripting, kubernetes, helm, CI/CD
+- Mentor(s):  
+  - Yuri Shkuro (@yurishkuro, github@ysh.us)
+  - Jonah Kowall (@jkowall, jkowall@kowall.net 
+- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5767
+
+### Karmada
+
+#### Collect and visualize Karmada metrics
+
+- Description: Karmada dashboard now supports one-time metric retrieval, but it is difficult to observe the status of multi-clusters with one-time metric retrieval. Therefore, we would like to implement a lightweight metric collection capability to collect Karmada metrics and visualize them on the Karmada dashboard. This will allow cluster administrators to quickly get the status of the clusters and solve problems within the clusters.
+- Expected Outcome:
+  - Metric Collection and Storage Design Document
+  - Query Analysis Interface & Front-end Visualization
+- Recommended Skills:
+  - Kubernetes
+  - Go
+  - gin
+  - react
+  - sqlite
+- Mentor(s):
+  - Wenjiang Ding (@warjiang, 1096409085@qq.com)
+  - Zhen Chang (@XiShanYongYe-Chang, changzhen5@huawei.com)
+- Upstream Issue: https://github.com/karmada-io/dashboard/issues/62
+
+#### Enhance Karmada controller-manager and schedule testing coverage
+
+- Description: Karmada would like to improve the UT coverage of the code to better maintain the quality of the code and reduce the introduction of defects. Increase the UT coverage rate to 50% to 60% (currently, the UT coverage rate is [28.26%](https://app.codecov.io/gh/karmada-io/karmada) ). The entire Karmada repository is a bit large for one project, so we will split it into two projects. The current parts mainly target the `karmada-controller-manager` and `karmada-scheduler` components.
+- Expected Outcome:
+  - Increase the UT (Unit Test) coverage by more than 25% and add more than 4000 lines of code coverage in the following directories.
+```
+pkg/controllers
+pkg/dependenciesdistributor
+pkg/descheduler
+pkg/detector
+pkg/estimator
+pkg/scheduler
+pkg/resourceinterpreter
+pkg/util
+```
+- Recommended Skills:
+  - Go
+  - Cloud Native
+- Mentor(s):
+  - Zhen Chang (@XiShanYongYe-Chang, changzhen5@huawei.com)
+  - Zhuang Zhang (@zhzhuang-zju, m17799853869@163.com)
+- Upstream Issue: https://github.com/karmada-io/karmada/issues/5235
+
+####
+
+- Description: Karmada would like to improve the UT coverage of the code to better maintain the quality of the code and reduce the introduction of defects. Increase the UT coverage rate to 50% to 60% (currently, the UT coverage rate is [28.26%](https://app.codecov.io/gh/karmada-io/karmada) ). The entire Karmada repository is a bit large for one project, so we will split it into two projects. The current focus is mainly on other parts except for the `karmada-controller-manager` and `karmada-scheduler` components.
+- Expected Outcome:
+  - Increase the UT (Unit Test) coverage by more than 25% and add more than 5500 lines of code coverage except for the following directories.
+```
+pkg/controllers
+pkg/dependenciesdistributor
+pkg/descheduler
+pkg/detector
+pkg/estimator
+pkg/scheduler
+pkg/resourceinterpreter
+pkg/util
+```
+- Recommended Skills:
+  - Go
+  - Cloud Native
+- Mentor(s):
+  - Zhen Chang (@XiShanYongYe-Chang, changzhen5@huawei.com)
+  - Chaosi Pan (@chaosi-zju, chaosi@zju.edu.cn)
+- Upstream Issue: https://github.com/karmada-io/karmada/issues/5236