Clean Up GSoC 2025 Project Formatting #4000

thesuperzapper · 2025-02-13T23:08:34Z

This PR improves the formatting and wording to the various GSoC 2025 projects to make the page readable.

It also removes the "Helm Chart" and "Kubeflow IDE" projects, as these have not been approved by the community at this time, so it would be unfair to have students spend time making proposals.

TIP: I recommend looking at the preview to see what the page looks like:

https://deploy-preview-4000--competent-brattain-de2d6d.netlify.app/events/gsoc-2025/#project-ideas

Signed-off-by: Mathew Wicks <[email protected]>

google-oss-prow · 2025-02-13T23:08:41Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from thesuperzapper. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/en/events/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

thesuperzapper · 2025-02-13T23:11:44Z

@andreyvelich @rareddy please review ASAP so we can get the GSoC 2025 page cleaned up, project mentors can update the page after we merge, now that it is consistent.

See preview site

andreyvelich · 2025-02-14T00:23:49Z

content/en/events/upcoming-events/gsoc-2025.md

- [Kale Donation to Kubeflow](https://github.com/kubeflow/community/issues/730)
-#### Expected Size of the Project
-350 Hours
-


Can we get confirmation from @StefanoFioravanzo @ederign @juliusvonkohout @kimwnasptd on removing these projects?

Just to be clear, we are talking about removing the following projects from the GSoC page, not that we will never do them:

"Helm Chart"

"Kubeflow IDE"

Also, once we agree as a community about the IDE one, and get a well scoped project for a student, we can add a new project before people start submitting applications.

I plan to resume the IDE WG discussion and discuss the next steps at next Tuesday's meeting. Can we hold off on removing GSoC until then?

I don't get the reason for removing this project. @thesuperzapper I'd appreciate you asked the project's requestors (me and Eder) confirmation and open the discussion before opening a PR that does so.

I don't get the reason for removing this project. @thesuperzapper I'd appreciate you asked the project's requestors (me and Eder) confirmation and open the discussion before opening a PR that does so.

@StefanoFioravanzo, we actually have been discussing it on the slack channel? Have you been seeing it?

But to summarize the problem, both of these projects aren't technically part of kubeflow, and may not be accepted by the community.

Not to say that they never will be, but right now the IDE working group does not exist and there is no agreement on an official Helm chart.

Trying to use GSoC to force these things through is problematic.

I don't think using GSoC to force a decision is problematic. These sorts of things can often be a good forcing function to make a decision.

juliusvonkohout · 2025-02-14T08:44:11Z

If you split it up, i could already merge the formatting improvements. For project removal i need to talk to other KSC members in the KSC meeting.

juliusvonkohout · 2025-02-14T20:16:52Z

/hold
@thesuperzapper the removal of the projects will probably not be accepted by the KSC.

thesuperzapper · 2025-02-14T20:30:33Z

/hold @thesuperzapper the removal of the projects will probably not be accepted by the KSC.

@juliusvonkohout I am quite concerned with having GSoC projects for things that are not yet approved.

In either case, any project that we list here needs to be reasonably scoped for a student so we can define if they "succeed", and currently both the "IDE" and "Helm" ones are more community proposals than projects.

However, I am most concerned about the helm chart project, this is a BIG change for Kubeflow, and I have not seen an approved KEP to make an official helm chart distribution.

As a compromise, if a specific component (not platform) wants help making a helm chart, we could add a project for that, but the working group for that component would need to be involved.

thesuperzapper · 2025-02-14T20:37:48Z

@andreyvelich I thought you were in agreement that we should not have GSoC projects for unapproved proposals.

Has your opinion changed?

andreyvelich · 2025-02-14T22:42:08Z

@andreyvelich I thought you were in agreement that we should not have GSoC projects for unapproved proposals.

Has your opinion changed?

No, I still have the same opinion. We discuss it today with @johnugeorge, @juliusvonkohout, and @franciscojavierarceo.
For the Helm Chart my proposal was that student will work on projects, that currently can be deployed in standalone mode, and doesn't require additional dependencies:

Kubeflow Trainer
Kubeflow Katib
Kubeflow Spark Operator
Potentially, Kubeflow Model Registry

Also, student could help us to explore on how we can improve multi-tenancy and auth for KFP and Kubeflow Notebooks to make them work as a micro-service. Which allows end-users to easily switch auth and multi-tenancy in a way they want to use it.

One of the option, is to explore how Argo projects are managing auth and multi-tenancy in their UIs.
Their Helm Charts are stored individually: https://github.com/argoproj/argo-helm/tree/main/charts

thesuperzapper · 2025-02-14T22:51:03Z

@andreyvelich I will update the PR to re-add a "helm chart" project with the more specific scope of "standalone component helm charts":

Some questions:

Do we have issues on those repos saying what their plan is for a helm chart so I can link them for students to read?
Won't we need mentors from each of those components to at least be involved, or it will be challenging for them to succeed?

Also regarding the IDE one, should we just leave it off for now, and allow them to re-add it if/when the IDE proposal gets finalized?

andreyvelich · 2025-02-14T23:01:34Z

Do we have issues on those repos saying what their plan is for a helm chart so I can link them for students to read?

Not yet, I hope mentors can drive it. We have one for Kubeflow Trainer: kubeflow/trainer#1197

Won't we need mentors from each of those components to at least be involved, or it will be challenging for them to succeed?

I don't think we need mentors for each projects since student can design re-usable script that work across different projects.

Also regarding the IDE one, should we just leave it off for now, and allow them to re-add it if/when the IDE proposal gets finalized?

I would like to hear @StefanoFioravanzo and @ederign suggestions here.

StefanoFioravanzo · 2025-02-15T17:56:28Z

I understand the concern about promoting a project tied to a WG that hasn't been officially approved. Our understanding is that there is no particular objection to finalize the WG proposal, @ederign will bring it up anyway in the next community meeting to push things forward. If we can hold off removing the project proposal until then, I'd appreciate.

juliusvonkohout · 2025-02-17T08:49:44Z

@andreyvelich I will update the PR to re-add a "helm chart" project with the more specific scope of "standalone component helm charts":

Some questions:
* Do we have issues on those repos saying what their plan is for a helm chart so I can link them for students to read?

* Won't we need mentors from each of those components to at least be involved, or it will be challenging for them to succeed?
Also regarding the IDE one, should we just leave it off for now, and allow them to re-add it if/when the IDE proposal gets finalized?

There was no vote on this yet and different opinions, so maybe separate it out for now if you want to have it merged sooner. Last exchange I saw was more or less the current Helm proposal.

Signed-off-by: Mathew Wicks <[email protected]>

thesuperzapper · 2025-02-18T01:26:39Z

@andreyvelich in the interest of getting this merged (because the current page is very hard to read), I have re-added the Helm/IDE projects.

As discussed in #4000 (comment) I have scoped the helm project down to making charts for standalone components of kubeflow, rather than the overall kubeflow platform.

I think this should be acceptable to merge now, and we can update/remove projects if things change in future PRs.

andreyvelich

I left a few comments.
For me changes looks good, but we need lgtm from other mentors.

andreyvelich · 2025-02-18T01:32:47Z

content/en/events/upcoming-events/gsoc-2025.md

-* Kubeflow Documentation: [Kubeflow.org](https://www.kubeflow.org/)  
-* Helm Documentation: Helm.sh
+- Work with Kubeflow components maintainers to support the creation of Helm charts for some Standalone Kubeflow components.
+- Investigate possible systems to automatically generate or maintain charts based on the existing kustomize manifests.


Should we say design and implement synchronization script between Helm and Kustomize to keep manifests up-to-date?
For example, @ChenYi015 already implemented one script for KFTrainer: https://github.com/kubeflow/trainer/blob/c0b1d7d26e7a7caea1ffd8b3111b79be6de24b78/hack/sync-manifests.sh

andreyvelich · 2025-02-18T01:34:10Z

content/en/events/upcoming-events/gsoc-2025.md

+- Pipelines: productionize the [SeaweedFS PoC](https://github.com/kubeflow/manifests/tree/master/contrib/seaweedfs) as secure minio replacement
+- Pipelines: isolate artifacts per namespace/profile/user using only one bucket ([`kubeflow/pipelines#4649`](https://github.com/kubeflow/pipelines/issues/4649))


Shouldn't this be a separate project since these are very complex tasks ?

I think the idea is that @juliusvonkohout and myself will only mentor 1-2 of these because there are too many to accept a project for all.

They also have very similar skill requirements, so it's not a big deal, as it lets the students apply to the area they want to focus on.

andreyvelich · 2025-02-18T01:37:26Z

content/en/events/upcoming-events/gsoc-2025.md

-350 hours
+- containers and Kubernetes knowledge
+- Helm (especially templating and chart creation)
+- Kustomize (not strictly required, but a plus)


I think, this skill is a requirement since we should design the sync scripts as well.

andreyvelich · 2025-02-18T01:39:36Z

content/en/events/upcoming-events/gsoc-2025.md

-#### Mentors: 
- Andrey Velichkevich, 
- Valentina Rodriguez Sosa
+### Project 8: Support JAX and TensorFlow Training Runtimes


You can link these issues created by @Electronic-Waste

Support TensorFlow Runtime trainer#2443

Support JAX Runtimes trainer#2442

andreyvelich · 2025-02-18T01:40:05Z

content/en/events/upcoming-events/gsoc-2025.md

 ---
+---
+
+### Project 9: Sidecars for Katib Metrics Collectors


Suggested change

### Project 9: Sidecars for Katib Metrics Collectors

### Project 9: Kubernetes-native Sidecars Containers for Katib Metrics Collector

rareddy · 2025-02-18T01:44:51Z

/lgtm +1

juliusvonkohout · 2025-02-18T15:42:10Z

/hold
/ do not merge for anything related to removing or altering the goals of projects without the mentors and or KSC agreeing

Clean Up GSoC 2025 Project Formatting

adfb1a3

Signed-off-by: Mathew Wicks <[email protected]>

google-oss-prow bot requested a review from akgraner February 13, 2025 23:08

google-oss-prow bot requested review from jbottum and varodrig February 13, 2025 23:08

google-oss-prow bot added the size/XL label Feb 13, 2025

andreyvelich reviewed Feb 14, 2025

View reviewed changes

google-oss-prow bot added the do-not-merge/hold label Feb 14, 2025

Re-add Helm + IDE Projects

d75908b

Signed-off-by: Mathew Wicks <[email protected]>

andreyvelich reviewed Feb 18, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Clean Up GSoC 2025 Project Formatting #4000

Clean Up GSoC 2025 Project Formatting #4000

thesuperzapper commented Feb 13, 2025 •

edited

Loading

google-oss-prow bot commented Feb 13, 2025

thesuperzapper commented Feb 13, 2025 •

edited

Loading

andreyvelich Feb 14, 2025

thesuperzapper Feb 14, 2025

ederign Feb 14, 2025

StefanoFioravanzo Feb 14, 2025

thesuperzapper Feb 14, 2025

franciscojavierarceo Feb 16, 2025

juliusvonkohout commented Feb 14, 2025 •

edited

Loading

juliusvonkohout commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025

andreyvelich commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025 •

edited

Loading

andreyvelich commented Feb 14, 2025

StefanoFioravanzo commented Feb 15, 2025

juliusvonkohout commented Feb 17, 2025 •

edited

Loading

thesuperzapper commented Feb 18, 2025

andreyvelich left a comment

andreyvelich Feb 18, 2025

andreyvelich Feb 18, 2025 •

edited

Loading

thesuperzapper Feb 18, 2025

andreyvelich Feb 18, 2025 •

edited

Loading

andreyvelich Feb 18, 2025

andreyvelich Feb 18, 2025

rareddy commented Feb 18, 2025

juliusvonkohout commented Feb 18, 2025 •

edited

Loading

		- Pipelines: productionize the [SeaweedFS PoC](https://github.com/kubeflow/manifests/tree/master/contrib/seaweedfs) as secure minio replacement
		- Pipelines: isolate artifacts per namespace/profile/user using only one bucket ([`kubeflow/pipelines#4649`](https://github.com/kubeflow/pipelines/issues/4649))

	### Project 9: Sidecars for Katib Metrics Collectors
	### Project 9: Kubernetes-native Sidecars Containers for Katib Metrics Collector

Clean Up GSoC 2025 Project Formatting #4000

Are you sure you want to change the base?

Clean Up GSoC 2025 Project Formatting #4000

Conversation

thesuperzapper commented Feb 13, 2025 • edited Loading

google-oss-prow bot commented Feb 13, 2025

thesuperzapper commented Feb 13, 2025 • edited Loading

See preview site

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

juliusvonkohout commented Feb 14, 2025 • edited Loading

juliusvonkohout commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025

andreyvelich commented Feb 14, 2025

thesuperzapper commented Feb 14, 2025 • edited Loading

andreyvelich commented Feb 14, 2025

StefanoFioravanzo commented Feb 15, 2025

juliusvonkohout commented Feb 17, 2025 • edited Loading

thesuperzapper commented Feb 18, 2025

andreyvelich left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

andreyvelich Feb 18, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

andreyvelich Feb 18, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rareddy commented Feb 18, 2025

juliusvonkohout commented Feb 18, 2025 • edited Loading

thesuperzapper commented Feb 13, 2025 •

edited

Loading

thesuperzapper commented Feb 13, 2025 •

edited

Loading

juliusvonkohout commented Feb 14, 2025 •

edited

Loading

thesuperzapper commented Feb 14, 2025 •

edited

Loading

juliusvonkohout commented Feb 17, 2025 •

edited

Loading

andreyvelich Feb 18, 2025 •

edited

Loading

andreyvelich Feb 18, 2025 •

edited

Loading

juliusvonkohout commented Feb 18, 2025 •

edited

Loading