GSOC 2025 - Mentor Project Planning

[rareddy]

Hello Kubeflow Community,

Kubeflow has officially submitted to be part of Goole Summer Code 2025. We do hope to get selected as one of the participating organizations this year. We had a very successful GSOC 2024. I thank all the Mentors and Students for making it successful.

I am looking for

• Signing up Mentors. If you would like to be a mentor this season, please reach out to me on CNCF Slack or leave your Name and git ID here. I will invite all the 2024 mentors by default, so please use this form only if you are a new mentor.

• Project Ideas for Kubeflow components. If you submit an idea, you must be a mentor (Kubeflow member and/or committer) or if you are a student submitting a proposal it must be approved by one of the component leads or a committer on that component.

Make sure your Project Ideas include ALL of the required information below:

1. Project title/description
2. Detailed description of the project. Provide as many details as possible for students to read and understand without asking too many questions about the project.
3. Expected outcomes
4. Skills required/preferred
5. Possible mentors
6. Component
7. Difficulty (Low, Medium, Expert)
8. If you already have Git issue for it, please include that here.
9. Expected size of the project (90, 175 or 350 hours. Please do NOT use any arbitrary number, choose one close to list given)

Leave a single comment here for each proposal. As we approve them, we will collate all the projects at https://www.kubeflow.org/events/gsoc-2025/. If you have questions, please come and ask in CNCF Slack #kubeflow-gsoc-participants.

All mentors MUST be assigned to one or more projects.

The deadline to submit all the ideas is Feb 15th, 2025. So, please take some time and submit them. Thank you all for your support.

[varodrig]

@rareddy are you thinking on having this content on the website? otherwise I'd recommend to create the issue on the community repository.

cc @franciscojavierarceo

[thesuperzapper]

/transfer community

[Shekharrajak]

@rareddy , I would like to be a mentor and interested on spark-operator project. I will be sharing my ideas/project proposals soon.

[Electronic-Waste]

@rareddy Hi, I was a GSoC student last year, and also a new maintainer in Kubeflow. Benefit from the GSoC project a lot, I would like to apply for the mentor of training-operator and katib this year. I'm sure it will help more new contributors like me to get engaged in Kubeflow and the world of open source.

As for the project ideas, not yet. But I'll put them here once they are ready.

cc @kubeflow/wg-automl-leads @kubeflow/wg-training-leads

[juliusvonkohout]

@rareddy here are my rough ideas

Project Idea 1

Project Title: multi-tenancy/security, Kubeflow repository Migration, and CI/CD Enhancement

Detailed Description:

• Productionize the seaweedfs PoC as secure minio replacement https://github.com/kubeflow/manifests/tree/master/contrib/seaweedfs, since we are stuck with a 5 year old minio due to AGPL
• add multi tenancy to seweadfs similar to the approach in feat(backend): isolate artifacts per namespace/profile/user using only one bucket pipelines#7725
  -Help to migrate Kubeflow/kubeflow components to kubeflow/dashboard and kubeflow/notebooks. This might even start before Gsoc
• Renovate kubeflow/dashboard dependencies, addressing CVEs.
• Implement architectural changes as needed.
• Adapt and improve scripts and CI/CD in kubeflow/manifests, including matrix calls to test multiple Kubernetes versions simultaneously.

Expected Outcomes:

• Successful migration of Kubeflow components.
• Hard multi-tenancy for the object storage
• Updated dependencies with resolved CVEs.
• Enhanced CI/CD pipeline supporting multiple Kubernetes versions.

Skills Required/Preferred:

• GitHub and GitHub Actions
• Containerfile and Kubernetes knowledge
• Experience with Python, Go and JavaScript frameworks

Possible Mentors:

• @juliusvonkohout
• @thesuperzapper are you interested?

Component: Kubeflow

Difficulty: Medium

Expected Size of the Project: 175/350 hours

Project Idea 2

Project Title: Maintain Kserve Models Web Application such that we have a proper UI for model serving.

Detailed Description:

• Clean up and merge 20 issues and 5 PRs.
• Implement a better CI/CD pipeline.
• Potentially migrate the application to /kubeflow/kserve-model-ui.
• Add features for editing, regression testing, and monitoring/metrics support.
• Synchronize with kserve 0.14+ changes.

Expected Outcomes:

• Resolved issues and merged PRs.
• less CVEs
• Improved CI/CD pipeline.
• New editing and regression testing features.
• Enhanced monitoring and metrics support.
• Application synchronized with kserve 0.14+ changes.

Skills Required/Preferred:

• GitHub Actions
• Containerfiles
• JavaScript frameworks

Possible Mentors:

• Julius von Kohout
• @varodrig do you want to help here?

Component: Kserve UI

Difficulty: Medium

Expected Size of the Project: 175+ hours

[juliusvonkohout]

@Ramesh I updated project idea one above for multi-tenancy, and seaweedfs

• Productionize the seaweedfs PoC as minio replacement https://github.com/kubeflow/manifests/tree/master/contrib/seaweedfs
• add multi tenancy to seweadfs similar to the approach in feat(backend): isolate artifacts per namespace/profile/user using only one bucket pipelines#7725

[mahdikhashan]

@rareddy Hi, I was a GSoC student last year, and also a new maintainer in Kubeflow. Benefit from the GSoC project a lot, I would like to apply for the mentor of training-operator and katib this year. I'm sure it will help more new contributors like me to get engaged in Kubeflow and the world of open source.

As for the project ideas, not yet. But I'll put them here once they are ready.

cc @kubeflow/wg-automl-leads @kubeflow/wg-training-leads

I'm new contributor to the project, trying to join the meetings and contribute to components. I'd like also to apply as a mentee. over the past few weeks @Electronic-Waste has been very helpful, and I would appreciate the opportunity to have them as my mentor, as I believe I can learn a lot from their experience.

[juliusvonkohout]

@kimwnasptd what do you think about

kubeflow/manifests#2676 (comment)

Project Idea 3

Project Title: Make our service mesh rootless by default and provide secure model inference by default.

Detailed Description:
Secure our service mesh with istio-cni by default kubeflow/manifests#2907 and an option for istio-ambient mesh kubeflow/manifests#2676 with zero overhead namespaces (single waypoint proxy deployment). Furthermore we need to enable a secure Kserve by default kubeflow/manifests#2811. A general plan is also available at
kubeflow/manifests#2528

Expected Outcomes:

• A secure cni/ambient mesh with waypoint proxies only in the istio-sytem namespace for zero overhead namespaces. Just the same as the detailed description.

Skills Required/Preferred:

• GitHub and GitHub Actions
• Kubernetes and networking
• Istio, Kustomize

Possible Mentors:

• @juliusvonkohout
• @kimwnasptd are you interested?

Component: Kubeflow

Difficulty: small
Expected Size of the Project: 175 hours

[kimwnasptd]

@juliusvonkohout I'm super interested in this! Although I'd suggest us to be a bit careful when defining the scope, to not end up shooting ourselves in the foot by committing to something that in the end might not be fully in our hand to implement.

Some gray areas I have in mind and worry me a bit:

1. If we need to update the AuthorizationPolicies of workloads
   • Since it looks like it requires targetRefs, for targeting the waypoint proxy
   • If this is the case, there are components in Kubeflow that need to be changed that are not within our control (i.e. Knative)
2. If we need to have HTTPRoute objects instead of VirtualService ones
   • For the same reason as above, regarding "third-party" components

In any case though, happy to be a mentor for that one and we can figure out a scope that could fit this effort. I'll also be looking at it with the Canonical team, so I'll have cycles to help on this as well.

[juliusvonkohout]

@juliusvonkohout I'm super interested in this! Although I'd suggest us to be a bit careful when defining the scope, to not end up shooting ourselves in the foot by committing to something that in the end might not be fully in our hand to implement.

Some gray areas I have in mind and worry me a bit:

1. If we need to update the AuthorizationPolicies of workloads
   • Since it looks like it requires targetRefs, for targeting the waypoint proxy
   • If this is the case, there are components in Kubeflow that need to be changed that are not within our control (i.e. Knative)
2. If we need to have HTTPRoute objects instead of VirtualService ones
   • For the same reason as above, regarding "third-party" components

In any case though, happy to be a mentor for that one and we can figure out a scope that could fit this effort. I'll also be looking at it with the Canonical team, so I'll have cycles to help on this as well.

I changed it to
"secure istio-cni by default and an option for istio-ambient mesh with zero overhead namespace (single waypoint proxy deployment)" maybe you have a better formulation for the targets.

[RameshOswal]

Interested in mentoring

Ramesh Oswal git-Id: rameshoswal

[rareddy]

@RameshOswal one of the requirements I am placing on mentors is, you either work with an existing lead on a component to come up with a project that you can be a mentor on. so please propose a project idea.