diff --git a/.idea/mentoring.iml b/.idea/mentoring.iml
new file mode 100644
index 00000000..5e764c4f
--- /dev/null
+++ b/.idea/mentoring.iml
@@ -0,0 +1,9 @@
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/modules.xml b/.idea/modules.xml
new file mode 100644
index 00000000..f8d9bffd
--- /dev/null
+++ b/.idea/modules.xml
@@ -0,0 +1,8 @@
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/vcs.xml b/.idea/vcs.xml
new file mode 100644
index 00000000..94a25f7f
--- /dev/null
+++ b/.idea/vcs.xml
@@ -0,0 +1,6 @@
+
+
+
+
+
+
\ No newline at end of file
diff --git a/.idea/workspace.xml b/.idea/workspace.xml
new file mode 100644
index 00000000..6b9b6d4a
--- /dev/null
+++ b/.idea/workspace.xml
@@ -0,0 +1,65 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {
+ "keyToString": {
+ "RunOnceActivity.OpenProjectViewOnStart": "true",
+ "RunOnceActivity.ShowReadmeOnStart": "true",
+ "RunOnceActivity.go.format.on.save.advertiser.fired": "true",
+ "RunOnceActivity.go.formatter.settings.were.checked": "true",
+ "RunOnceActivity.go.migrated.go.modules.settings": "true",
+ "RunOnceActivity.go.modules.go.list.on.any.changes.was.set": "true",
+ "RunOnceActivity.go.watchers.conflict.with.on.save.actions.check.performed": "true",
+ "WebServerToolWindowFactoryState": "false",
+ "go.import.settings.migrated": "true",
+ "go.sdk.automatically.set": "true",
+ "last_opened_file_path": "C:/Users/Administrator",
+ "settings.editor.selected.configurable": "reference.settings.ide.settings.web.browsers"
+ }
+}
+
+
+
+
+
+
+
+
+ false
+ true
+
+
\ No newline at end of file
diff --git a/programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md b/programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md
index c3c497bf..5557b3b6 100644
--- a/programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md
+++ b/programs/lfx-mentorship/2024/03-Sep-Nov/project_ideas.md
@@ -389,3 +389,68 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke
- Florent Poinsard (@frouioui, florent@planetscale.com)
- Matt Lord (@mattlord, mlord@planetscale.com)
- Upstream Issue: https://github.com/vitessio/website/issues/1798
+
+### 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
+
+#### Enhance the test coverage for the Karmada search, operator, and webhook components
+
+- 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 `karmada-search`, `karmada-operator`, `karmada-webhook` 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