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.
GitHub Actions provides detailed views of CI workflows at the repository level, but it can be difficult for maintainers to quickly track the overall status of recurring workflows, such as nightly tests, over time. Important information, like historical failures or trends, often requires manual inspection of individual workflow runs. This work aims to improve CI observability for `urunc` by creating a centralized dashboard that presents an aggregated view of its nightly (and other CI) test workflows. The dashboard will provide maintainers with a clear overview of recent runs, success and failure states, and relevant metadata in a single place. In addition to visualization, this work includes the design and implementation of a notification mechanism that alerts maintainers when tests fail. This will help ensure that regressions are noticed quickly and addressed in a timely manner, improving overall project reliability. - Expected Outcome: - Design and implementation of a dashboard summarizing nightly (and CI) test results. - Clear visualization of workflow status and execution history. - Implementation of a notification system for nightly test failures. - Documentation describing the dashboard, notification setup, and maintenance.
Based on existing datasets, the issue aims to build an advanced benchmark for edge-oriented domain-specific large models on KubeEdge-Ianvs. It aims to help all Edge AI application developers validate and select the best-matched domain-specific large models. For Edge AI service providers, it also helps identify which scenarios, edge nodes, or even locations could have the best performance or improvement for their models. Expected Outcome: 1. Domain-specific Large Model Benchmark for the edge, including test datasets, testing toolkits, and usage guidelines. 2. (Advanced) Design and implementation of specific evaluation metrics. 3. (Advanced) Survey and research reports.
conmon-rs is a container monitor written in Rust, used by CRI-O to monitor a container's lifecycle. Part of its responsibilities is log forwarding--taking the output of the container and writing that output to various places. Currently, conmon-rs supports one format: the one required by the Kubernetes CRI. The goal of this proposal is to add new log formats from the list of standardized ones, like JSON, Splunk, Journald. - Expected outcome: A JSON log driver and Journald log driver are added to conmon-rs. A stretch goal of adding a Splunk log driver is also within scope.
Hyperledger Iroha 1 has a great set of commands and queries, but some useful commands and queries are missing. Iroha 1 blockchain can be the core of banking systems because it supports transactions, multiple currencies, etc. Nevertheless, advanced filtering of transactions is only partially available in Iroha 1, and it's necessary for banking systems. Currently, to filter transactions, we need to return many of them and filter with our code - it is much heavier for both Iroha's node and client application. During the internship project, queries should be extended with optional arguments. The mentee will be able to learn the following: - the architecture of Iroha (1.x), - work in the true spirit of open-source, communicating with the Iroha community, joining calls, etc. - writing documentation, - following rules of the open-source code of Hyperledger Iroha - creating automatic tests of code Expected Outcome - Implementation according to description and plan of documentation and tests. - Added the possibility of running modified queries from Iroha's client libraries. - Present changes during the Iroha bi-weekly meeting at the end of the internship.
Ianvs serves as KubeEdge SIG AI distributed benchmark toolkit. As more and more contributors running, KubeEdge Ianvs now has 25 examples and the number is still increasing. KubeEdge Ianvs then faces mounting usability issues due to dependency evolution and validation mechanisms. As Python versions, third-party libraries, and Ianvs features advance, partial historical examples fail to execute. This has led to surging user-reported Issues from confused contributors, untested PRs breaking core functionality of legacy features, severely outdated documentation misaligning with actual capabilities. Without systematic intervention, the example risks becoming obsolete for edge-AI developers and especially newcomers. We then try to resurrect Ianvs’ usability with comprehensive example restoration. Expected Outcome: 1. Diagnose & fix bugs across examples, including dependency manifests, license scan and runtime configurations. 2. Documentation Modernization, including revamp tutorials with reproducible step-by-step guides, publish developer-focused debugging playbooks for common failures 3. Build a CI pipeline testing examples with GitHub Actions against multiple Python versions, critical Ianvs/upstream updates and block PRs that break validated examples
Integrate Litmus Chaos testing with Kyevrno.
In the existing Karmada architecture, each component should have its own unique certificates to ensure clear identity and security. Best practices dictate that each component's name be used as the Common Name (CN) in its certificate to facilitate identity differentiation. However, currently, all Karmada components share same identical certificate content, leading to confusion and potential security risks. The objective of this project is to enhance the compliance of the Karmada certificate system by ensuring that each component possesses distinct certificates that reflect its identity. This will improve system security, reduce management complexity, and align with industry standards. This project aims to achieve the following standards: 1. Utilize a single CA certificate for the entire Karmada system. 2. Issue individual server certificates for each server component, using the component name as the CN. 3. Issue individual client certificates for each client component, using the component name as the CN, same client can use consistent certificate for different servers. Expected Outcome: 1. Complete the issuance of different certificates for 8 server components and import the certificate content into the corresponding certificate Secrets. 2. Complete the issuance of different certificates for 11 client components and import the certificate content into the corresponding certificate Secrets or Config Secrets.
Currently tremor supports composition through composing pipelines together, through function composition and through allowing references to query operator definitions and constants in externalizable modules that can be loaded via a module path. It would be excellent if the modularity in tremor extended fully to the query language so that distinct subgraphs could be modularized and consumed by multiple queries to optimise for reuse of flow oriented logic in tremor. This would require extending module support in the tremor query language to support sub-graph definitions with parameters that can be declared and used as part of a higher level query. Modules in tremor-query in their current state: <https://docs.tremor.rs/tremor-query/modules/> This project idea involves designing the sub-graph module syntax and semantics and implementing changes to the lexer, grammar, optimizers and runtime. It is most suited to candidates who are interested in programming language evolution and design.
Now VTP as the VNF test platform can support OVP VNF compliance and validation test. It can manage and orchestrate different VNF testing scenario across different SUT environment like ONAP MANO, OpenStack Cloud, Vendor VNFM, SDN Controller, etc under one umbrella across different Test providers and partner labs. As the open source test platform, it should include standard test case from standard organization, so that it can support the testing for standard component which can accelerate OVP test and certification process for commercial products implemented by reference standards. VTP is going to support ETSI NFV APIs conformance test. The mentee will be required to make the technical research and develop related test cases and integrate with VTP under guide of our team.
Define and execute scalability tests for Kyverno on large Kubernetes clusters with several namespaces and resources. The candidate has to propose and execute a performance test plan and help optimize resource usage of Kyverno for different loads for large Kubernetes clusters.
Microcks is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project focuses on creating a validated and repeatable SaaS architecture for deploying Microcks on AWS, with the ultimate goal of listing it on the AWS Marketplace through the AWS Partner Network Co-Sell program. By addressing the community's frequent demand, this initiative will simplify Microcks' adoption while leveraging a complete suite of AWS services to ensure scalability, security, and ease of deployment. The core Microcks maintainers focus on features, security, and enhancements. The adopters are responsible for production setups. However, a shared repository of best practices can help users learn from one another in a true open-source spirit. Participants will contribute to the Microcks community repository by documenting the AWS Marketplace deployment. Expected Outcome: Enable Microcks adopters to confidently deploy production-ready setups on AWS, ensuring the scalability and reliability needed for enterprise environments. By integrating Microcks into the AWS Marketplace, the project will further enhance its visibility and adoption within the AWS ecosystem. - Designing and validating a SaaS architecture that is compliant with AWS Foundational Technical Review (FTR). - Utilizing AWS-native services such as EKS, Aurora (PostgreSQL), DocumentDB, API Gateway, IAM, and CloudFormation for an end-to-end deployment. - Streamlined deployment workflows
This project focuses on developing the UI components necessary for managing Binding Policies in KubeStellar. Users should be able to create, update, delete, and view policies via an intuitive interface while ensuring seamless integration with the backend API. Objectives: - Develop UI components for managing Binding Policies (CRUD operations). - Implement validation mechanisms to ensure policies comply with Kubernetes standards. - Provide real-time updates on policy status and binding information. - Improve UI design for a seamless user experience. Expected Outcomes: - A fully functional Binding Policy management UI. - Smooth user interaction with the backend API. - Modern UI with real-time validation and feedback.
SidecarSet is an advance workload for sidecar container injection and upgrade. Currently the sidecar container resource must be set explicitely in the sidecar template, however in the cases of traffic proxy, log collection and device emulation etc, it is desirable to to set the resources according to resource of app container. The goal is to support the adaptively setting for sidecar resources and provide best practice for typical use cases. Expected Outcome: 1. Implementation for adaptively resources setting for sidecar in SidecarSet workload 2. Unit and integration tests 3. Documentation for the function usage and typical use cases in the OpenKruise website
The Kyverno CLI should be flexible enough to perform real variable substitutions when CEL libraries are used in policies, in addition to static substitutions. This enhancement would enable comprehensive policy testing without requiring a real Kubernetes cluster, significantly speeding up development and CI/CD pipelines.
Cloud Native Buildpacks is a specification and set of tools that help you take source code and convert them into OCI images. Sound familiar? Maybe you've heard of Docker, Source-2-Image, Kaniko, etc. Well you are not alone. The goal of this project is to refactor our existing ["features" page](https://buildpacks.io/features/#comparison) to provide an easier to comprehend comparison across other similar solutions. Through this project, you'll research each alternative, learn how they compare and aim to provide that information to the users in an easy to digest format. This will include designing and implementing a better format to compare projects and their features side-by-side.
<p>Currently, urunc launches sandbox monitors, such as Firecracker and QEMU</p><p>through command-line invocations. This approach offers limited control over the</p><p>sandbox lifecycle once the process is started. On the other hand, most</p><p>monitors expose remote management interfaces, typically through a socket-based</p><p>API.</p><p><br></p><p>These interfaces provide access to the same operations currently performed via</p><p>CLI, but also enable further control over the sandbox lifecycle. In particular,</p><p>they allow more fine-grained lifecycle management of the sandbox, including</p><p>querying and monitoring its state, performing device hotplug and unplug</p><p>operations and interacting with the guest.</p><p><br></p><p>This project aims to extend urunc's sandbox integration layer to support remote</p><p>management interfaces and to explore each monitor's capabilities in order to</p><p>extend the functionalities of urunc sandboxed containers.</p><p><br></p><p>Expected Outcome:</p><p> - A design document describing the updated architecture and workflow for</p><p> spawning and managing sandbox monitors in urunc.</p><p> - Implementation of the necessary changes in urunc to manage sandbox monitors</p><p> through their respective APIs.</p>
The component-model proposal merges and supersedes the Module Linking and Interface Types proposals. With this feature, WasmEdge can execute multiple modules wasm with Module Linking and and more flexible types with Interface Type.
Meshery (https://meshery.io) is a self-service engineering platform, Meshery enables collaborative design and operation of cloud native infrastructure. [Meshery Catalog](https://meshery.io/catalog) content represents a schema-based description of cloud native infrastructure. Catalog content need to be portable between Meshery deployments as well as easily version-able in external repositories. - Expected outcome: Rebuild the Meshery Design System so that it provides the open source building blocks to design and implement consistent, accessible, and delightful product experiences.
This project aims to investigate and implement ideas for improving KubeStellar Core Helm chart reliance by contributing improvements to Helm project and reducing its reliance on initContainers for waiting/gathering/processing Kubernetes resources that are used by other containers (for example, KubeFlex Control Planes and their kubeconfigs). 1. Introduce an annotation that would make Helm wait for user- specified resources 2. Introduce priority/coordination of Helm resource creation 3. Introduce an alternative path for dependence chart override values 4. Introduce a mechanism for a chart to require a specified Helm min version or range 5. Introduce an alternative to kubectl initContainers Expected Outcome: 1. A comprehensive investigation of potential alternative methods and approaches 2. Contributions to Helm project to introduce new features that would allow to improve the quality of KubeStellar Core chart 3. A solution implementation that reduces the reliance on kubectl initContainers
Enhance Islet’s security by identifying vulnerabilities early using fuzz testing. This project integrates Cargo Fuzz tools with Islet’s CI pipeline, focusing on testing RMM interfaces (RMI and RSI) based on ARM’s RMM specification. Expected Outcome: Deliver a set of robust fuzz tests integrated into Islet’s CI, improving security and compliance with ARM standards.
A proof of concept to add buildkit support to pack in order to build multi-arch images. Pack is the reference implementation of a Cloud Native Buildpacks platform used to build application images from source code. Expected Outcome: Multi-arch support has been one of the most requested features for Cloud Native Buildpacks, and this would allow end-users/developers to build multi-arch images with the pack cli.
The idea is to define criteria to measure the resiliency score of a cluster after a set of chaos scenarios. Expected Outcome: - a page in our documentation website clearly explaining the scoring algorithm implemented and the best practices to leverage it on the user's environment - a set of functions in our API library to easily collect data and calculate the score - the implementation of the scoring method across all Krkn scenarios, and an update to our telemetry data structures to include the resiliency score to allow the collection by downstream observability systems
Currently, Kmesh metrics are only reported when a TCP connection is closed. In the case of long connections, it is not possible to know the status before the connection is closed. Therefore, we hope to add the capability to periodically report metrics for long connections. Expected Outcome: 1. proposal 2. code 3. user guide
<p>Agones is a Kubernetes-native platform for hosting, running, and scaling dedicated game servers. This project builds a Headlamp plugin that adds an **Agones** section to Headlamp, surfacing Agones CRDs so operators can **view and manage game servers, fleets, and allocations** from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and visibility into lifecycle and allocation state.</p><p><br></p><p>Expected Outcome:</p><p> - Plugin exposes key Agones CRDs: GameServer, Fleet, GameServerSet.</p><p> - List views, with summary columns (name, namespace, state, address, port, node, replicas).</p><p> - Detail pages, showing config, status conditions, lifecycle state, and sub-resources (game server pods).</p><p> - Relational navigation, fleet → game servers; game server → fleet.</p><p> - Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements.</p><p> - Structured config display (collapsible sections/YAML toggle), humanized lifecycle states (Ready, Allocated, Shutdown).</p><p> - README with prerequisites and limitations; blog post demoing usage.</p><p><br></p>