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.
his project aims to develop AI/ML models for NFV-usecases. Any two of the following three problems can be considered. VNF/CNF resource/performance/failure prediction NFV log analysis with NLP Synthetic monitoring and logging data generation using GANs Learning Objectives ML Techniques: Deep_learning. ML model development AI/ML for Telco Usecases. Interested Interns: DO NOT apply through this platform. Due to a bug, please go to https://wiki.lfnetworking.org/x/EasZB. Read the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org
Description: Kruise Rollout enable progressive delivery of various workload ranging from stateless workload such as Deployment to stateful workload such as StatefulSet or customized operators. This project aims to bring progress delivery capability to daemon workload, which is run on each node of a k8s cluster. The project involves implementing common API of progressive delivery for OpenKruise Advance DaemonSet, and integrate with the Kruise Rollout framework. Expected Outcome: Support progressive delivery for OpenKruise Advance DaemonSet(along with supporting test cases and docs) , that is, update new version of daemon pods in batches with user defined pause strategy. Traffic scheduling is not required for this project.
The task will be to implement a visual blueprint frontend similar to Blockly, Scratch, or Unreal Engine Blueprints for the Iroha Special Instructions smart contract language. Iroha Special Instructions (or ISI) are a composable smart contract language for Iroha v2 providing an opportunity to execute logic on-chain. In their raw form they represent a syntactical tree, which is not very convenient to write. We think that the structure of the ISI will perfectly match a visual blueprint language and therefore make developing Iroha v2 smart contracts more comfortable for everyone. The app to be developed should allow the user to compose ISI, potentially validating the correspondent types of outputs of each of the blocks. After the program of blueprints is composed, the app should provide a way to transpile the blocks into the file of raw ISI in their byte format. Potentially the app can also act like a client and submit the ISI directly to a Hyperledger Iroha network to be executed right away.
Currently, OpenKruise depends solely on the PaaS or CLI to listing OpenKruise workload display and operations. The lack of a general purpose Web-UI greatly hinder the adoption among developer users. This project is about to build a simple Web-UI that can list OpenKruise workload along with the native K8s workload, and support enhanced operation such as container restart or workload rollout. The Web-UI can be served directly as a dashboard , or as an example of OpenKruise integration in PaaS. Expected Outcome: - simple Web-UI - integration of the Web-UI with existing PaaS such as KubeSphere (https://dev-guide.kubesphere.io/extension-dev-guide)
Description: This project will add new useful sample applications to the Certifier Framework including a secure messaging app and several key management applications. In addition, we plan to support more platforms, including client platforms like RISC-V, ARM, Raspberry Pi based implementations and potentially a "soft" platform like Android (which is not an "official" Confidential Computing platform but a simulated environment useful for interacting with "real" Confidential Computing platforms). Expected Outcome: The forgoing applications (using the certifier framework), some additional "shims" to support other programming environments like Java and additional support for new platforms.
A Chaos Engineering Platform for Kubernetes.
More and more workload is moving towards running on the edge. We saw experiments running Kubernetes on vehicles, fighter jets, 5G antenna and various far edge, near edge and fat edge environments. We would like to see what the challenges are when Knative is run in a resource limited environment. While there are multiple edge-friendly Kubernetes distributions, we would like to see [Microshift](https://github.com/openshift/microshift) used as the base platform. Knative consists of Serving and Eventing modules but focusing on Knative Serving as a first step should be more approachable. The project consists of 2 stages. First one is to run Knative on Microshift with minimal resources. This requires finding out problems here, solving them. A stretch goal is to find out what happens with architectures other than x86_64. - Expected outcome: Having Knative Serving with an ingress layer running on top of Microshift. Having a Hello-World Knative Service running on top. Finding issues blocking the edge setup, and possibly fixing them.
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
OPI project is aiming to expand the OpenShift DPU Operator to support NVIDIA, xSight, and/or Mangoboost hardware. The ideal candidate needs to be comfortable at the intersection of infrastructure software and hardware offloading. The expected skill set is a combination of low-level hardware abstraction skills and high-level Kubernetes operator patterns. Technical skills: Golang expertise Github, CI/CD, Linux Networking expertise (Strong understanding of SR-IOV, OVS-DPDK, and virtual functions (VFs)) Familiarity with the OPI APIs and how DPUs handle networking and storage offloading. Experience with developing Kubernetes Operators. Experience with operator-sdk or controller-runtime. They must understand Custom Resource Definitions (CRDs), Reconcile loops, and watch patterns. Understanding Vendor SDKs (ex: DOCA). Optional - Comprehensive knowledge of the OpenShift ecosystem
Chaos Mesh is a powerful chaos engineering platform for Kubernetes. There is a Katacoda playground as interactive tutorial, and we want to build more Katacoda scenarios as the minimum examples for each certain type of chaos experiment. The basic work would be to create new katacoda scenarios as referred to by https://github.com/chaos-mesh/chaos-mesh/tree/master/examples, and build small applications (with well-built observability) as the target of chaos experiment if required. This project will not require you to dive deep into the hard-core parts of Chaos Mesh, instead, it would be a tour of learning and exploring Chaos Mesh.
Jaeger-v1 has its own Kubernetes Operator (https://github.com/jaegertracing/jaeger-operator) which deploys Jaeger components according to the deployment strategy as well as the database or datastore. The goal of this project is to develop a new operator for [Jaeger-v2](https://github.com/jaegertracing/jaeger/issues/4843) that achieves feature parity with the v1 operator while introducing improvements and new capabilities. This new operator will leverage the [OpenTelemetry operator](https://github.com/open-telemetry/opentelemetry-operator) for Jaeger-v2 deployment while maintaining and enhancing the storage management features from the v1 operator. More details in the [upstream issue](https://github.com/jaegertracing/jaeger/issues/5766). Expected Outcome: By the end of this project, we aim to achieve full feature parity between the Jaeger v2 operator and the v1 operator, with the added benefits of OpenTelemetry integration. The new operator will provide a seamless experience for users, maintaining the robustness and flexibility of v1 while introducing the advantages of v2 and OpenTelemetry.
Kagent is an open-source framework for DevOps and platform engineers to run AI agents in Kubernetes, automating complex operations and troubleshooting tasks. We have a few agents for kagents (Kubernetes, Istio, Cilium, Argo, Prometheus, Grafana etc) and would love to build more agents for other CNCF graduated or incubation projects so users can use conversation style to chat with the agents to either learn or troubleshooting or operating these projects. - Expected Outcome: Able to build at least 2-3 agents for CNCF graduated or incubation projects. Able to write a blog for the work and produce associated docs as well. Upstream Issues: - https://github.com/kagent-dev/kagent/issues/662 - https://github.com/kagent-dev/kagent/issues/664
Creating applications for the Zowe Virtual Desktop requires a significant amount of programming that can be automated. The purpose of this project is to expand on an existing prototype to make stub application generation a breeze for new comers and future exploiters wanting to experiment with Zowe.
Description: Develop a system to reflect all Kyverno Policies in the community library on Artifact Hub Expected Outcome: All Kyverno policies searchable on Artifact Hub with an extensible system for future use
ADE - Add additional log support
Minifabric supports deploy Hyperledger Fabric in both docker and K8S environments, however, it currently does not support Hyperledger Fabric running as k8s operators. Making Minifabric deploying Hyperledger Fabric onto K8S and running as K8S operators will allow hyperledger fabric network nodes with taking advantages of K8S operator benefit. This work will involve the participators to develop K8S operators, deploying K8S operator controllers and managing K8S operator life cycles, at the same time, the participators will be able to learn Fabric and Fabric deployment model. This is a great opportunity for anyone who would like to know K8S and know Hyperledger Fabric.
This project intends to propose a solution to this real-world problem, and it is research-focused. The goal is to give a strong contribution to the Hyperledger ecosystem in terms of the state of the art in blockchain interoperability. Some questions that this project aims to answer are: How can we interoperate Hyperledger technologies with other blockchains?, How can Hyperledger initiatives position themselves to tackle blockchain interoperability?, What standards we require to define middleware between blockchains? What are the consequences of employing smart contracts with external processes and data (the external part means another connected blockchain)?, The key to the survivability of this technology? In other to try to answer those questions, in this project the mentee(s) will start by studying some of the most prominent blockchain interoperability solutions already available or being proposed, and how they can be used to promote and strengthen Hyperledger technologies. Then, the mentee will design and develop a framework for creating, deploying and maintaining services with several blockchains. The applicability of the solution to be proposed is to be demonstrated through the exploration of a use case, implementing several blockchains (including Hyperledger Fabric) to increase the dependability of blockchain-powered services administrated by several stakeholders, serving as a proof-of-concept.
- Description: In order to make sure Cortex doesn’t introduce performance regressions across releases and major changes, we would like to introduce an automated way to run some nightly macro/micro benchmarks for Cortex clusters. This project could potentially involve setting up Kubernetes clusters, Cortex components, and load generators. We’d love to keep track of performance metrics for each test run and visualize them through a UI. - Expected Outcome: An automated workflow that runs performance macro/micro benchmarks everyday or on demand and performance metrics can be visualized through a UI.
Harbor is a popular and widely adopted container registry. We have developed an initial CLI (https://github.com/goharbor/harbor-cli) that we would like to extend and implement additional functionality, and common workflows that are currently only present in the Web UI. We are seeking a Golangs experienced manatee who can work on the project independently. - Expected Outcome: Working Golang Harbor CLI which can be used in the CI/CD implementations that compliment the Web UI covering the typical workflows of Harbor administrators and users. Familiarity with Golang library spf13/cobra and REST/Open API. Well-documented CLI that users love to use, and with the corresponding architectural diagrams under the Harbor. Working CI/CD with GitHub actions that create multi architecture binaries and containers.
Create a version of the OMP COBOL Course that includes new modules to cover CICS COBOL programming basics. Additionally, to enable a version of the course that can be run on a laptop using the free version of Enterprise Developer for IBM Z.
kruise-game is being used by many game companies. It is imperative to build the stability of kruise-game components. With the rapid iteration of project functions, the current test coverage has not met expectations, so we need to add more UT and E2E use cases to ensure that there will be no problems with our basic functions. In addition, in a large-scale cluster environment, kruise-game also needs more indicators to reveal the performance of the current controller. Expected Outcome: 1. Expand End-to-End (E2E) Test Coverage 2. Improve Unit Test (UT) Coverage 3. Enhance Observability via Controller Metrics 4. Improve Logging Contextualization
<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN THE UNITED STATES*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link-State Protocol (BGP-LS) is a critical protocol for modern network management and SDN-style controller integration, enabling the distribution of network topology information. Currently, SONiC's BGP-LS implementation lacks comprehensive CLI tools for configuration and monitoring, making it difficult for network operators to effectively deploy and troubleshoot BGP-LS in production environments. Additionally, there is insufficient testing infrastructure to validate BGP-LS functionality in complex multi-node topologies.</p><p>This mentorship program aims to address these gaps by developing a complete CLI interface for BGP-LS operations and establishing a robust 7-node testing framework based on vSONiC instances. This will significantly improve SONiC's BGP-LS usability and reliability, making it production-ready for enterprises and service providers who rely on topology discovery for traffic engineering and network automation.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><ul><li>Develop a comprehensive CLI interface for BGP-LS configuration, monitoring, and troubleshooting in SONiC</li><li>Design and implement a 7-node test topology to validate BGP-LS functionality in complex network scenarios</li><li>Create automated test cases covering BGP-LS neighbor establishment, topology advertisement, and failure scenarios</li><li>Document CLI usage and testing procedures for community adoption and future development</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Complete BGP-LS sonic-cli implementation with commands for neighbor configuration, status checking, and topology visualization</li><li>Functional 7-node test environment with automated deployment scripts and topology configurations</li><li>Comprehensive test suite covering at least 15-20 BGP-LS scenarios including normal operations and edge cases</li><li>Technical documentation including CLI user guide, test topology design document, and contribution guidelines for future enhancements</li><li>Merge CLI codes into SONiC repo</li><li><strong>Program Length: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and/or C++ programming</li><li>Understanding of BGP routing protocols and network topology concepts</li><li>Familiarity with Linux CLI development and command-line interface design patterns</li><li>Experience with network testing frameworks (pytest, ansible Framework) or willingness to learn</li><li>Basic knowledge of SONiC architecture or similar network operating systems</li><li>Strong documentation and communication skills</li></ul>
TiKV is a distributed KV database. It support using clients in Rust, Golang, Java, C++ and Python, and the Node client is the last missing piece. This program is going to implement Node client on top of Rust client just like Python client and C++ client.
Following up on the previous projects that helped build the Cloud Foundry components and the CF Operator on Z. The Kube CF project will be incubated in the Cloud Foundry Foundation in 2020, and there are release integration efforts happening, that will allow us to plugin tests and builds specifically for s390x.