gsoc: Add project details for KServe Models Web Application, Helm and Security

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

@@ -129,9 +129,7 @@ The GSoC contributor is building the bedrock layer that these future innovations
 - Infrastructure (Terraform, Docker, Kubernetes)
 - Communication (Ability to document architectural decisions clearly) 
 
----
-
-## Project 3: OptimizationJob CRD for Hyperparameter Optimization
+### Project 2: OptimizationJob CRD for Hyperparameter Optimization
 
 **Components:** [kubeflow/katib](https://www.github.com/kubeflow/katib), [kubeflow/sdk](https://www.github.com/kubeflow/sdk), [kubeflow/trainer](https://www.github.com/kubeflow/trainer)
 
@@ -162,4 +160,100 @@ Tracking issue: [kubeflow/katib#2605](https://github.com/kubeflow/katib/issues/2
 * Python
 * Familiarity with Kubernetes controllers, CRDs
 * Basic understanding of machine learning training workflows
-* Experience with HPO frameworks
+* Experience with HPO frameworks
+
+### Project 3: KServe Models Web Application
+
+**Components:** Kserve, Kubeflow Common Library, Kubeflow Dashboard
+
+**Mentors:** [Griffin Sullivan](https://github.com/Griffin-Sullivan), [Harshit Nayan](https://github.com/LogicalGuy77), [Dhanisha Phadate](https://github.com/dhanishaphadate)
+
+**Contributor:** 
+
+**Details:** The project includes improving test coverage and cleanup, adding end-to-end and deployment-level testing, and validating the application through full deployment workflows. It also migrates the repository from KServe to Kubeflow and extends the UI to support KServe v0.16/0.17 features, including [LLMInferenceService](https://kserve.github.io/website/docs/model-serving/generative-inference/llmisvc/llmisvc-overview) and [InferenceGraph](https://kserve.github.io/website/docs/model-serving/inferencegraph/overview).
+
+This project modernizes the KServe Models Web Application by upgrading Angular from v14 to v16+. The Kubeflow common library will be upgraded first, followed by updates to Dockerfiles, Makefiles, workflows and documentation.
+
+**Difficulty:** Hard
+
+**Size:** 350 hours
+
+**Skills Required/Preferred:**
+
+- Angular & TypeScript
+- Kubernetes and CRDs
+- Docker and CI/CD
+- Kubeflow / KServe (preferred)
+
+### Project 4: Platform Scalability and Security
+
+**Components:** Kubeflow Manifests, Kubeflow Pipelines, Kubeflow Training Operator
+
+**Mentors:** [Julius von Kohout](https://github.com/juliusvonkohout)
+
+**Contributor:** 
+
+**Details:** As Kubeflow scales to environments with 1,000+ namespaces, core bottlenecks emerge. This project focuses on optimizing CRD controllers, improving multi-tenancy security, and hardening the platform. Key work areas include: refactoring the Profile Controller to use Metacontroller for a cleaner plugin system, migrating from Istio Gateway to the Kubernetes Gateway API and enabling Model Registry by default. Many CRD controllers are written inefficiently and struggle with the reconciliation load or block the Kubernetes API server with too many requests.
+Using "Kubernetes user namespaces" for PSS baseline in the level in PSS restricted will also be an explorative task.
+
+**Difficulty:** Hard
+
+**Size:** 350 hours
+
+**Related Issues/PR:**
+
+- [Rootless Kubeflow](https://github.com/kubeflow/manifests/issues/2528)
+- [Enable model-registry with UI by default](https://github.com/kubeflow/manifests/pull/3318)
+- [Update kserve/kserve manifests from v0.16.0](https://github.com/kubeflow/manifests/pull/3290)
+- [Fix kustomize warnings](https://github.com/kubeflow/manifests/pull/3268)
+- [Migrate to gateway API](https://github.com/kubeflow/manifests/pull/3094)
+- ["zero-trust" security / networking for training jobs](https://github.com/kubeflow/trainer/issues/2341)
+- [fix: variable namespaces for networkpolicies](https://github.com/kubeflow/manifests/pull/3319)
+- [Recurring Runs Queue Throughput Optimization](https://github.com/kubeflow/pipelines/pull/12610)
+- [Add securityContext support for container components](https://github.com/kubeflow/pipelines/pull/12577)
+- [add gRPC metrics to api-server (RPS/latency), optimize execution spec reporting](https://github.com/kubeflow/pipelines/pull/12010)
+- [ConfigMap-based plugin system for profile controller](https://github.com/kubeflow/dashboard/pull/177)
+- [fix(frontend): Prevent Unauthorized Cross-Namespace Artifact Access](https://github.com/kubeflow/pipelines/pull/12550)
+- [Kubeflow platform pull requests](https://github.com/kubeflow/manifests/pulls)
+
+**Skills Required/Preferred:**
+
+- Go
+- Kubernetes
+- Python
+- Istio
+- Networking
+- Linux Security
+
+### Project 5: Helm Charts
+
+**Components:** Kubeflow Manifests, Kubeflow Pipelines, Kubeflow Katib
+
+**Mentors:** [Julius von Kohout](https://github.com/juliusvonkohout), [Humair Khan](https://github.com/HumairAK), [Dhanisha Phadate](https://github.com/dhanishaphadate)
+
+**Contributor:** 
+
+**Details:** This project continues the KSC-approved initiative to provide Kubeflow platform and standalone components via Helm. The goal is to move beyond Kustomize-only deployments to offer minimalistic, maintainable Helm charts that reflect Kustomize defaults 1:1. Key tasks include: developing and testing Helm charts for KFP and Katib, implementing CI/CD testing infrastructure for Helm-based deployments and coordinating with component maintainers to ensure cross-project consistency.
+
+This project will touch most components and continue the helm chart initiative started by Kunal Dugar who also helped a lot with the testing infrastructure.
+This will therefore also include working with maintainers of other components such as KFP maintainersfor the KFP helm charts, security and scalability topic or Katib maintainers for Katib helm charts. Some have already open PRs and there was a formal vote by the KSC (Kubeflow steering Committee) that we are moving forward with offering Kubeflow platform and standalone components as helm charts. Therefore it is not just the technical part, but also the coordination effort. The goal is to make minimalistic helm charts that are easy to maintain next to kustomize and only expose sensible settings relevant to most users. For the time being the rendered chart default values must replicate kustomize 1:1. The testing infrastructure has already been set up in the GSOC 2025 efforts in kubeflow/manifests where we already have a few helm charts.
+
+**Difficulty:** Hard
+
+**Size:** 350 hours
+
+**Related Issues/PR:**
+
+- [Pipeline Helm Charts](https://github.com/kubeflow/manifests/pull/3237)
+- [Helm Chart Templates For Katib](https://github.com/kubeflow/katib/pull/2553)
+- [Helm charts (KEP 831)](https://github.com/kubeflow/manifests/issues/2730)
+- [Fix the remaining Kustomize 5 warnings](https://github.com/kubeflow/manifests/issues/2991)
+
+**Skills Required/Preferred:**
+
+- Helm
+- Kustomize
+- Kubernetes
+- GitHub Actions
+- Bash
+- Community Coordination