-
Notifications
You must be signed in to change notification settings - Fork 57
blog: Kubeflow and GSoC 2025 blog #183
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.
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
Conversation
Signed-off-by: Akash Jaiswal <[email protected]>
Signed-off-by: Akash Jaiswal <[email protected]>
Signed-off-by: Xinmin Du <[email protected]>
7139ddc to
28643c7
Compare
Signed-off-by: kunal-511 <[email protected]>
Signed-off-by: Harshvir Potpose <[email protected]>
Signed-off-by: kunal-511 <[email protected]>
48e4ac4 to
5f4a065
Compare
|
@varodrig for review |
Updated mentor information and added project outcomes. Signed-off-by: Julius von Kohout <[email protected]>
Signed-off-by: madmecodes <[email protected]>
Added details about Project 5: JupyterLab Plugin for Kubeflow, including contributor, mentors, overview, key outcomes, and resources. Signed-off-by: Amrit Kumar <[email protected]>
Signed-off-by: Amrit Kumar <[email protected]>
|
Hi @kaikaila @fresende Can you please add your project to this PR? Related slack discussion: https://cloud-native.slack.com/archives/C0742LBR5BM/p1760876548016539 |
Signed-off-by: Harshit Nayan <[email protected]>
Signed-off-by: Harshit Nayan <[email protected]>
Signed-off-by: Julius von Kohout <[email protected]>
|
Please ping me when this is ready and i can approve |
Signed-off-by: SanthoshToorpu <[email protected]>
Signed-off-by: Akash Jaiswal <[email protected]>
|
Here are the current details: Completed Projects: 1, 2, 3, 4, 5, 7, 10, 12 I’ve already reached out to and tagged the contributors earlier, but haven’t received any response yet. |
| - Eliminated MinIO's licensing constraints by adopting SeaweedFS's more permissive license model | ||
| - Implemented comprehensive CI tests for SeaweedFS deployment and namespace isolation functionality | ||
| - Strengthened the manifests repository's CI pipeline and contributed to the dashboard migration efforts | ||
| - Enforcing PodSecurityStandars baseline/restricted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Enforcing PodSecurityStandars baseline/restricted | |
| - Enforcing PodSecurityStandards baseline/restricted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| This project focused on creating component-based Helm charts for Kubeflow, enabling flexible and incremental deployment of ML infrastructure. Instead of requiring a full platform installation, users can now deploy specific components like Katib, Pipelines, Model Registry, and others independently with customized configurations. | ||
|
|
||
| **Key Outcomes:** | ||
| - Kubeflow AI reference paltform end to end testing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Kubeflow AI reference paltform end to end testing | |
| - Kubeflow AI reference platform end to end testing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|  | ||
|
|
||
| **Overview:** | ||
| We had a few examples in the repository that we wanted to include in our end-to-end (E2E) tests, but all of them were CPU-based. Projects like Torchune and Qwen 2.5, for instance, require GPU resources to run — yet our existing CI setup couldn’t validate them at all because it was entirely CPU-focused. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| We had a few examples in the repository that we wanted to include in our end-to-end (E2E) tests, but all of them were CPU-based. Projects like Torchune and Qwen 2.5, for instance, require GPU resources to run — yet our existing CI setup couldn’t validate them at all because it was entirely CPU-focused. | |
| We had a few examples in the repository that we wanted to include in our end-to-end (E2E) tests, but all of them were CPU-based. Projects like TorchTune and Qwen 2.5, for instance, require GPU resources to run — yet our existing CI setup couldn’t validate them at all because it was entirely CPU-focused. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
looks great. Thank you for working on this. |
Signed-off-by: Akash Jaiswal <[email protected]>
|
Hi @varodrig did the changes. |
Signed-off-by: Julius von Kohout <[email protected]>
|
to me it looks good enough on a high level. /lgtm @akagami-harsh @LogicalGuy77 @madmecodes @kunal-511 and other students please complain here if you do not agree with the text. |
|
So feel free to merge if we do not here complaints in the next 24 hours @varodrig, the PR is already 3 weeks old. |
varodrig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great! thank you for working on this.
Signed-off-by: Fellipe Resende <[email protected]>
|
/lgtm |
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: juliusvonkohout The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?
This PR aims to add all the 9 project which were part of GSoC 2025. We wanted to show the community what our contributors, along with guidance of mentors have achieved in last 3-4 months of summer. Hopeful that this would be helpful for upcoming contributors as well.
Fixes #182