Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>KubeVela's workflow engine and config management layer have two long-standing production gaps that this mentorship will close together. First, the `request` workflow step has no native way to source HTTP headers (bearer tokens, API keys, basic auth) from Kubernetes Secrets — users wanting to call authenticated APIs are forced to hardcode credentials directly in the workflow definition, where they end up visible in `kubectl get` output and Git history. On top of that, attempts to interpolate values into the `header` map using Go templates or CUE string interpolation regularly conflict with native CUE syntax, producing un-rendered strings or silent execution failures. Second, KubeVela's Config Management today stores `ConfigTemplate`s as labeled ConfigMaps (`config-template-*` prefix) and `Config`s as labeled Secrets — there are no proper Kubernetes API types (`kubectl get configs` returns nothing meaningful), and all CUE schema and `validation.$returns` checks run client-side in the `vela` CLI. Configs created through any other path (workflow steps, VelaUX, direct `kubectl apply`) bypass validation entirely, so the same template enforces different rules depending on the entry point. The mentee will tackle both. The first deliverable extends the HTTP provider in `kubevela/workflow` with a `headerFromSecret` field that resolves values from Kubernetes Secrets natively in Go (mirroring how the same provider already handles Secrets for `tlsConfig`), and exposes it as a first-class CUE parameter — bypassing the templating layer entirely. The second introduces a proper Kubernetes API group, `config.oam.dev/v1alpha1`, with `ConfigTemplate` and `Config` CRDs, event-driven controllers built on controller-runtime, and validating admission webhooks that move CUE validation server-side. Sensitive properties never live in the CRD — they sit in a separate Secret referenced via `propertiesFrom.secretRef`. A dual-read controller preserves full backward compatibility: legacy ConfigMap templates, old CLI versions, and existing Secret-based configs continue to work without disruption. Together, the two deliverables harden KubeVela's HTTP integration surface and modernize its configuration layer into a Kubernetes-native, GitOps-friendly API.</p><p><br></p><p>Expected Outcome:</p><p> - New `HeaderFromSecret` field on the `Request` struct in `pkg/providers/http/http.go` (kubevela/workflow), with native Secret resolution inside `runHTTP()` mirroring the existing `getTransport()` TLS pattern</p><p> - Updated `request.cue` definition in kubevela/kubevela exposing `headerFromSecret` as a parameter, with namespace defaulting to `context.namespace`</p><p> - New `config.oam.dev/v1alpha1` API group with `ConfigTemplate` and `Config` CRDs, DeepCopy, and scheme registration</p><p> - `ConfigTemplateReconciler` that parses CUE templates and writes the generated OpenAPI schema to `status.schema`</p>
<p>*APPLICATIONS ONLY OPEN TO STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>The sonic-mgmt test framework is a critical component of PR validation and continuous integration. However, over time, several inefficiencies have accumulated:</p><ul><li>Some individual test scripts run longer than 30 minutes, and some individual test cases exceed 10 minutes, PR pipelines retry failed test scripts up to two additional times, amplifying runtime cost.</li><li>Long-running scripts disproportionately consume KVM CPU resources.</li><li>Excessive runtime increases PR turnaround time and reduces CI throughput.</li></ul><p><br></p><p>Currently, there is no formal runtime governance framework, no enforcement threshold, and limited visibility into runtime regressions across scripts, test cases, topology types, and branches.</p><p><br></p><p>As SONiC continues to scale, unmanaged test runtime growth will:</p><ul><li>Increase infrastructure cost</li><li>Slow down PR validation</li><li>Reduce contributor productivity</li><li>Impact overall CI system stability</li></ul><p>This project aims to establish a data-driven runtime governance and optimization framework for sonic-mgmt.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The mentee(s) will work on designing and implementing a structured runtime optimization initiative that includes:</p><ul><li>Refactor selected high-impact long-running test scripts</li><li>Propose test case optimization strategies:</li><li class="ql-indent-1">Reduce loop/iteration counts</li><li class="ql-indent-1">Reduce coverage where representative sampling is sufficient</li><li class="ql-indent-1">Optimize setup/teardown overhead</li><li class="ql-indent-1">Remove redundant waits</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>By the end of the mentorship program, the following deliverables are expected:</p><ul><li>Refactored high-impact test scripts demonstrating measurable improvement</li><li>A structured runtime dataset and analysis report</li><li>A documented SONiC Test Runtime Best Practices guide</li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><ul><li>Python programming skills</li><li>Familiarity with pytest framework</li><li>Basic understanding of CI/CD systems</li><li>Ability to analyze data (Kusto / SQL / Pandas experience preferred)</li><li>Understanding of networking fundamentals (basic SONiC knowledge preferred)</li></ul>
<p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Overview</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This proposal outlines a 12-week mentorship program focused on significantly enhancing the rule testing and Continuous Integration (CI) tooling for Minder's security policies. The project will primarily involve the go programming language, with secondary exposure to rego, python, and shell scripting. The successful completion of this project will provide Minder users with a robust, automated, and maintainable framework for ensuring the quality and correctness of custom security rules.</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This opportunity is open for a single mentee with some previous GitHub and medium-sized project experience.</span></p><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Goals</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">The primary goals of this 12-week engagement are to:</span></p><p><br></p><ol><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Improve Rule Testing Tools: Develop a standalone testing command for Minder rules.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Robust Testing: Allow for the definition and execution of multiple distinct test cases against a single rule.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Focus on Local Execution: Tests should be able to execute locally without requiring network access to external resources.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Support Diverse Data Ingestion: Design the framework to accommodate tests for rules covering all current data ingestion methods: REST API, Git repositories, and declared </span><a href="https://docs.mindersec.dev/understand/data_sources" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(31, 31, 31);">data sources</a><span style="background-color: transparent; color: rgb(31, 31, 31);">.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Provide Automated CI Tooling: Implement CI workflows to automatically detect and run tests.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Update Existing Rules: Migrate and update existing tests within the github.com/mindersec/minder-rules-and-profiles repository to utilize the new framework.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Documentation and UX: Create documentation for the new tooling and address potential client-side UX issues related to testing.</span></li></ol><p><br></p><p><br></p>