Skip to content

Conversation

@jaiakash
Copy link
Member

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

Signed-off-by: Akash Jaiswal <[email protected]>
Signed-off-by: Akash Jaiswal <[email protected]>
Signed-off-by: Xinmin Du <[email protected]>
kunal-511 and others added 3 commits October 19, 2025 16:00
Signed-off-by: kunal-511 <[email protected]>
Signed-off-by: Harshvir Potpose <[email protected]>
@juliusvonkohout
Copy link
Member

@varodrig for review

juliusvonkohout and others added 4 commits October 19, 2025 13:59
Updated mentor information and added project outcomes.

Signed-off-by: Julius von Kohout <[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]>
@jaiakash
Copy link
Member Author

Hi @kaikaila @fresende Can you please add your project to this PR?

Related slack discussion: https://cloud-native.slack.com/archives/C0742LBR5BM/p1760876548016539

LogicalGuy77 and others added 3 commits October 22, 2025 01:12
Signed-off-by: Harshit Nayan <[email protected]>
Signed-off-by: Harshit Nayan <[email protected]>
Signed-off-by: Julius von Kohout <[email protected]>
@juliusvonkohout
Copy link
Member

Please ping me when this is ready and i can approve

@jaiakash
Copy link
Member Author

Here are the current details:

Completed Projects: 1, 2, 3, 4, 5, 7, 10, 12
Pending Projects: 6, 8, 11
No GSoC Contributor: 9

I’ve already reached out to and tagged the contributors earlier, but haven’t received any response yet.

cc @varodrig @juliusvonkohout

- 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Enforcing PodSecurityStandars baseline/restricted
- Enforcing PodSecurityStandards baseline/restricted

Copy link
Member Author

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Kubeflow AI reference paltform end to end testing
- Kubeflow AI reference platform end to end testing

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

![Diagram](/images/2025-09-06-kubeflow-and-gsoc2025/project7.png)

**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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@varodrig
Copy link

varodrig commented Nov 3, 2025

looks great. Thank you for working on this.
Please make the updates requested by @tarekabouzeid so we can merge it.
@juliusvonkohout also if you can review since you are involved on many projects.

Signed-off-by: Akash Jaiswal <[email protected]>
@jaiakash
Copy link
Member Author

jaiakash commented Nov 3, 2025

Hi @varodrig did the changes.
Please review.

Signed-off-by: Julius von Kohout <[email protected]>
@juliusvonkohout
Copy link
Member

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.

@juliusvonkohout
Copy link
Member

juliusvonkohout commented Nov 4, 2025

So feel free to merge if we do not here complaints in the next 24 hours @varodrig, the PR is already 3 weeks old.

Copy link

@varodrig varodrig left a 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]>
@google-oss-prow google-oss-prow bot removed the lgtm label Nov 4, 2025
@tarekabouzeid
Copy link
Member

/lgtm

@juliusvonkohout
Copy link
Member

looks great! thank you for working on this.

/lgtm

/approve

@google-oss-prow
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit 96966f1 into kubeflow:master Nov 5, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add blog about all the GSoC 2025 projects.