Skip to content

Commit

Permalink
merge main
Browse files Browse the repository at this point in the history 
Signed-off-by: ShutingZhao <shuting@nirmata.com>
  • Loading branch information
@realshuting
realshuting committed Jul 24, 2024
2 parents acaed21 + 3162f33 commit fff9f2b
Show file tree
Hide file tree
Showing 2 changed files with 32 additions and 6 deletions.
10 changes: 5 additions & 5 deletions programs/lfx-mentorship/2024/03-Sep-Nov/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,11 @@ Mentorship duration - three months (12 weeks - full-time schedule)

| activity | date |
|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
| project proposals | Jul 3 - Jul 23 5:00 PM PDT |
| mentee applications open | Jul 24 - Aug 6 5:00 PM PDT |
| application review/admission decisions | Aug 7 - Aug 20 5:00 PM PDT |
| selection notifications | Aug 27, 2024 5:00 PM PDT |
| Mentorship program begins with the initial work assignments | Sept 4, 2024 |
| project proposals | Jul 3 - Jul 30 5:00 PM PDT |
| mentee applications open | Jul 31 - Aug 13 5:00 PM PDT |
| application review/admission decisions | Aug 14 - Aug 27 5:00 PM PDT |
| selection notifications | Sept 3, 2024 5:00 PM PDT |
| Mentorship program begins with the initial work assignments | Sept 9, 2024 |
| Midterm mentee evaluations and first stipend payments | October 15, 2024 5:00 PM PDT (the week following the National Day holiday in China) |
| Final mentee evaluations and mentee feedback/blog submission due, second and final stipend payment approvals | Nov 26, 2024 5:00 PM PDT (Giving some time after KubeCon NA) |
| Last day of term | November 29, 2024 |
Expand Down
28 changes: 27 additions & 1 deletion programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,32 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
- 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

### Kyverno

#### Kyverno CLI for the Mutate Existing Rule
Expand All @@ -235,4 +261,4 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
- Mentor(s):
- Mariam Fahmy (@MariamFahmy98, mariam@nirmata.com)
- Shuting Zhao (@realshuting, shuting@nirmata.com)
- Upstream Issue: https://github.com/kyverno/kyverno/issues/9478
- Upstream Issue: https://github.com/kyverno/kyverno/issues/9478

0 comments on commit fff9f2b

Please sign in to comment.