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.
Implement default resource interpreters for TFJob and PyTorchJob workloads in Karmada. Expected Outcome: This includes writing the interpreter logic in Golang and Lua, ensuring proper scheduling and propagation of these workloads across member clusters. Additionally, create documentation on how to run TFJob and PyTorchJob on Karmada, and introduce the integration and best practices to the Kubeflow community.
This project will focus on implementing the backend infrastructure necessary to manage Workload Description Space (WDS) operations. The backend will support UI functionalities such as workload deployment and visualization. Objectives: - Develop API endpoints for workload deployment to WDS. - Implement workload status tracking and log retrieval. - Ensure efficient workload resource retrieval. Expected Outcomes - A robust WDS backend to support UI functionalities. - Secure API integrations for workload management. - Efficient backend processes for workload deployment and tracking.
Flux has several integration points with hyper-scaler platforms e.g., AWS. In general it is tricky to test these satisfactorily, because it requires running in the platform and thereby incurring usage costs. GCP donate credits that are used to test there; and now the Flux project has been generously granted credits to use for testing in AWS, and we can create conformance tests for AWS specifically too. Expected outcome: A suite of conformance tests for AWS integrations in Flux.
<p>In a standard container setup, the container shares the network namespace with</p><p>its host environment, meaning localhost inside the container refers to the same</p><p>loopback interface as the host's network namespace. Many CNI plugins and</p><p>container networking services rely on this assumption. For instance, Docker</p><p>sets up an internal DNS server listening on localhost within each container's</p><p>network namespace and configures `/etc/resolv.conf` accordingly. Similarly,</p><p>service meshes (e.g., Istio, Linkerd) inject sidecar proxies that listen on</p><p>localhost, and certain CNI plugins expose health checks or metrics endpoints on</p><p>the loopback interface.</p><p><br></p><p> In urunc, however, workloads execute inside a sandboxed environment</p><p>with its own isolated network stack. As a result,</p><p>localhost inside the sandbox does not refer to the host's network namespace</p><p>loopback interface but to the sandbox's own. This breaks any service that</p><p>relies on localhost-based communication between the container and host-level</p><p>components.</p><p><br></p><p>This project aims to investigate and implement mechanisms to bridge localhost</p><p>communication between the host network namespace and the sandbox. The mentee</p><p>will survey the landscape of CNI plugins and networking services that rely on</p><p>localhost, categorize the different communication patterns, and design a</p><p>solution that restores compatibility while preserving the</p><p>isolation guarantees that urunc provides.</p><p><br></p><p>- Expected Outcome:</p><p> - A survey and categorization of CNI plugins and networking services that</p><p> rely on localhost communication, documenting the specific patterns and</p><p> assumptions each makes.</p><p> - A design proposal of one or more mechanisms to bridge localhost traffic</p><p> between the host network namespace and the sandbox.</p><p> - Implementation of the proposed solution in urunc, with DNS resolution as</p><p> the primary use case.</p><p> - Evaluation of the new mechanism.</p><p><br></p>
Polycephaly is an open source project written in Groovy, which enables building z/OS source code using Jenkins and Git
The Meshery documentation docs.meshery.io (https://docs.meshery.io/) is a critical resource for users and contributors. Currently built using Jekyll, the site faces limitations in build speed, scalability, and long-term maintainability. Hugo, a modern static site generator, offers significantly faster build times, better content organization, and an improved developer experience. This internship focuses on migrating the entire docs.meshery.io (https://docs.meshery.io/) site from Jekyll to the Hugo framework, using docs.layer5.io (already implemented in Hugo) as a reference architecture. The migration will involve porting all documentation content, assets, layouts, and configuration while preserving URLs, SEO, contributor workflows, and existing auto-generated documentation files. Expected Outcome: i. Revamp of documentation set information architecture. Alignment with Diataxis framework. ii. Updated contributor docs. iii. All self-documenting aspects accounted for: a. Compatibility tests of Meshery Adapters. b. End-to-end tests of Meshery UI. c. Integration of Meshery Catalog and all designs. d. Publication of community discussion forum activity per category. e. Integration of Meshery Models (Integrations)
Currently, OpenDaylight project relies on Robot Framework to run CSIT (Continuous System and Integration Test). This has proven to be very stable and scalable framework for 10+ years, however times have changed and developers working in agile mode usually write system and integration code along with writing new features. In the new paradigm, Robot framework is more an obstacle than a help since developers have to ramp up in a new language that soon find very limiting compared to python or other language. The work in this internship is to look up modern open source test framework (python based) that are well supported and maintained (e.g. pytest, nosetest , etc), select one and write the core test libraries (e.g. REST, SSH, install ODL, etc) so that developers can start using this framework in addition to the existing Robot Framework. Interested Interns: DO NOT apply through this platform. Due to a bug, please go to https://wiki.lfnetworking.org/x/CKsZB Read the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org
PipeCD v1 - the new version based on a plugin architecture (ref: [PipeCD plugin-arch overview blog](https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/)), has released an alpha version, and we are rapidly adding features supported in v0. With a better architecture, support for multi-cluster Kubernetes deployments is a natural extension. This project will focus on developing the Piped v1 plugin to support multi-cluster Kubernetes deployments. - Expected Outcome: - Multi-cluster Kubernetes plugin for PipeCD - Possible update plugin SDK while develop the plugin - Possible update docs how to develop PipeCD plugin - Blog about how to develop a PipeCD plugin on [https://pipecd.dev/blog/](https://pipecd.dev/blog/)
When a large Prometheus is running in HA mode (i.e. 2 identical Prometheus scraping same targets) and it needs to be restarted (for upgrades, etc), there can be a temporary gap in queries when the second Prometheus is restarting. This is because the first Prometheus did not scrape any metrics when it was restarting (this is the gap), and when second Prometheus is restarting, only the first Prometheus is serving queries. To mitigate this, we want to start scraping targets as soon as Prometheus starts up, without waiting for it to complete the WAL replay and restore the old in-memory state. However, querying is still only enabled after WAL replay is over, but there won't be gaps in scraped data anymore. This project includes careful designing of low level technical challenges, including ensuring the correct handling of WAL records and seamlessly stitching together the new scraped data and the data restored from WAL without a lot of memory overhead. - Expected Outcome: - Design the correct handling of WAL records where the series information lines up between the old WAL and newly scraped data. - Design a low overhead method to stitch together the scraped data and the data restored from WAL. - Production ready PR with comprehensive test coverage. Ideally we will do the review iterations and merge the PR within this timeline.
Assist in development of the initial GenevaERS demo system, including building views, test processes, procedures to allow initial users to download and use GenevaERS successfully.
This Developer Relations project aims to accelerate KubeStellar UI adoption by building a vibrant community around this multi-cluster Kubernetes management interface. The mentee will establish KubeStellar's online presence across key platforms, create technical content showcasing multi-cluster management capabilities, produce regular demo livestreams, improve documentation for contributors, implement community feedback mechanisms, and represent the project at CNCF events. Expected Outcome: Established social media presence for KubeStellar, daily technical blog series, weekly/bi-weekly livestream demos, improved contributor documentation, active GitHub Discussions, community feedback system with analytics, and at least one CNCF talk submission.
KubeVela is a modern application delivery platform based on Kubernetes. It is currently a CNCF Sandbox project. In KubeVela, a CUE-based query mechanism is developed to satisfy the demands of advanced queries behind Kubernetes resources, which is called VelaQL. This project aims to make extensions to this mechanism and support monitoring Kubernetes resources through VelaQL. For example, monitoring the logs of pods in KubeVela Application behind Grafana.
This project aims to ease the transition and implementation of Posits, an alternative numerical representation, for RISC-V systems. By creating a robust hardware abstraction layer (HAL), developers need not know if the target RISC-V platform has a hardware Posits implementation or requires a software implementation. This new POSIX-compliant C++ library (with ports planned eventually) will help make available the option to transition between IEEE Float / Doubles to Posits and should make the machine-specific selection and configuration seamless. The lack of such a HAL is a roadblock in Posit adoption and Posits represent a serious opportunity for free and open source silicon (FOSSi) systems. We will also update the existing posit implementations to the current standard and add consistent unit testing. Initial focus will be directed toward HPC support, where numerical computation efficiency may be best observed. Additionally, we will be conducting benchmarking studies to evaluate the performance of the HAL, identifying bottlenecks, and iterating on the design based on empirical data. The testing framework will also be part of the mentee's deliverables.
This internship involves improving the existing Katacoda scenario and adding new scenarios to further include aspects of contributing such as spinning up a kind cluster with the changes made and testing those changes out. Through the course of this internship, you will also learn how one can contribute to other projects of the Kubernetes community such as the Kubernetes website, and document these processes as Katacoda scenarios to help new contributors get started in their contribution journey.
The kubeslice-cli repository currently lacks comprehensive unit and integration tests making it hard to test the changes. This project aims to implement a robust testing framework to ensure the reliability and stability of the CLI tool. The Mentee will write unit tests for existing functions & integration tests for the CLI commands & also set up a continuous integration pipeline to run these tests automatically on every commit and pull request. Expected Outcome: 1. A fully configured testing framework for kubeslice-cli with unit and integration tests covering all critical functionalities. 2. A CI/CD pipeline configuration (e.g., GitHub Actions) that automatically runs the tests on every pull request. 3. Documentation on how to run these tests & add new ones.
Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. Microcks depends on community contributions to address installation, setup, and infrastructure maintenance topics that fall outside the scope of the core project. This project aims to enhance the [Microcks Community Repository](https://github.com/microcks/community/tree/main/install) by providing detailed guides to help users with advanced and production-grade setups. Expected Outcome: - Fostering community members to share their technical knowledge on those topics, - Making contributions easy and straightforward - easily gathering this knowledge - Promoting contributed content with new access from the documentation, improved integration with our social communications, etc...
Implement default resource interpreters for RayCluster and RayJob workloads in Karmada. Expected Outcome: This includes interpreter development, validation, and comprehensive documentation on deploying and managing Ray workloads with Karmada. Present the integration and usage guide to the KubeRay community.
Hyperledger is a big project hosting different frameworks and tools. In Iroha team we've been working for some time now on integrating other projects into Iroha and Iroha into other projects. During that process, we've received good feedback and an important question: what can Iroha give other projects? To answer that, we've decided to mentor this project, including some research of different projects to create the most interoperable API solution and practical work with C++ code. We will try to derive a common subset of data model and executor interfaces from different HL projects in order to make the most compatible solution. Decoupling data model (commands and queries) will allow both reuse of it in different projects and easier work in case someone decides to change something in Iroha code itself (to customise it for their own project, for example, by easily plugging a new data model piece in). Some of the features might only be needed to some users, but not everyone.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: 1. A multitude of new relationships defined both intra and inter AWS services. 2. Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
<p>This project explores how AI PCs can be integrated into the KubeEdge ecosystem as a new type of edge node. With built-in heterogeneous computing capabilities such as CPUs, GPUs, and NPUs, AI PCs are becoming suitable platforms for local AI inference, privacy-sensitive applications, and low-latency intelligent services.</p><p>The mentee will connect one or more AI PCs to KubeEdge, deploy representative AI workloads, and explore resource monitoring and workload orchestration patterns for AI PC environments.</p><p>The project will summarize practical experience and provide reference documentation for using KubeEdge to manage AI PCs as edge computing infrastructure.</p><p><br></p><p>Expected Outcome:</p><p> - Connect one or more AI PCs to KubeEdge as edge nodes and verify their basic management capabilities.</p><p> - Deploy and run representative AI workloads on AI PCs through KubeEdge, such as lightweight large model inference, vision models, or multimodal services.</p><p> - Explore monitoring methods for local resources and AI-related metrics on AI PCs, such as CPU/GPU/NPU utilization, memory usage, and inference service health status.</p><p> - Summarize best practices for workload deployment, resource management, and edge-cloud collaboration for AI PCs.</p><p> - Fix issues discovered during validation, and submit PRs to KubeEdge, example repositories, or related documentation when necessary.</p><p> - Publish a blog or document to kubeedge/website introducing how to use AI PCs together with KubeEdge.</p><p> - Optional: explore an example scenario combining cloud-side collaboration and device-side inference, focusing on low-latency or privacy-sensitive tasks.</p><p><br></p>
This is a Project Management mentorship (product management for open source) for the project Inspektor Gadget (IG). Inspektor Gadget (https://github.com/cncf/mentoring/blob/main/programs/lfx-mentorship/2025/02-Jun-Aug/inspektor-gadget.io) is a powerful observability tool that enables security, monitoring and troubleshooting on Linux and Kubernetes. The framework uses a concept called “gadgets” which uses a technology called eBPF to enable us to drive valuable insights from the Linux kernel. Today, we have a very powerful gadget called Traceloop (https://inspektor-gadget.io/docs/latest/gadgets/traceloop/). However, as you can see the documentation around it is quite minimal and we need a strategy around how to bring this gadget to market in a big way. With Traceloop users can debug crashing applications as demonstrated here (https://www.youtube.com/watch?v=IoiDvzIZ3ok&list=PLnfCaIV4aZe9oQ7REBuP0PWwp-NEbFlGR&index=31). Our goal is to make community members aware of traceloop and therefore Inspektor Gadget to a) decrease time to resolution for developers debugging their applications b) drive adoption of the project . Expected Outcome: Increased awareness of the gadget Traceloop and Inspektor Gadget, and also a repeatable framework is established that can be easily scaled to other gadgets
To enhance code quality, maintainability, and developer experience, Fluid plans to migrate its unit testing framework from Testify to Ginkgo + Gomega—a more expressive and behavior-driven testing stack widely adopted in the Go ecosystem. Concurrently, we aim to significantly improve unit test (UT) coverage, raising it from the current 57% to at least 75%, thereby reducing regression risks and strengthening overall system reliability Expected Outcome: 1. Deliver comprehensive migration guidelines, coding best practices, and hands-on team training for Ginkgo + Gomega adoption. 2. Achieve a measurable increase in unit test coverage—from 57% to 75%—across core modules of the Fluid codebase.
Option 1: General Junior DevRel Mentorship This mentorship is designed for a junior Developer Relations or community-focused contributor who wants hands-on experience supporting a fast-growing open source project in the cloud native ecosystem. The mentee will work closely with the Kyverno maintainers and community to improve the overall developer and end-user experience through better documentation, tutorials, example content, and community-facing resources. The mentee will contribute upstream to Kyverno by helping create clear getting-started guides, improving existing documentation, supporting educational content such as blogs or walkthroughs, and assisting with community enablement initiatives. The mentorship focuses on foundational DevRel skills including technical communication, open source contribution workflows, user empathy, and translating complex technical concepts into approachable learning materials, while building a visible portfolio of real-world open source contributions. Option 2: Concise Version of the CEL-Focused Mentorship (1–2 Paragraphs) This mentorship offers a junior DevRel contributor the opportunity to work directly with the Kyverno community to support the adoption of Kyverno’s new CEL-based policy capabilities. The mentee will help create and refine documentation, tutorials, and example content that make it easier for new users to get started with CEL policies and for existing users to migrate from traditional policy types to CEL policie
<p>Kubescape evaluates compliance controls using OPA/Rego today, while Kubernetes has shipped native `ValidatingAdmissionPolicy` / `MutatingAdmissionPolicy` resources that use CEL expressions. The [`kubescape/cel-admission-library`](<a href="https://github.com/kubescape/cel-admission-library" rel="noopener noreferrer" target="_blank">https://github.com/kubescape/cel-admission-library</a>) project already ships a growing set of Kubescape controls as VAP resources, but Kubescape cannot evaluate them locally — so a resource passing `kubescape scan` may still fail the cluster's admission controller. This project adds a native CEL evaluation engine to Kubescape (running alongside Rego), using the same `ValidatingAdmissionPolicy` YAML format and `google/cel-go` library that Kubernetes uses internally. With the same rule expression evaluated in both places, Kubescape becomes directly comparable to — and competitive with — Kyverno for teams wanting a single policy language across CI, runtime scanning, and admission enforcement. A sample of existing Rego controls are then converted to CEL as proof-of-concept, validating the conversion pattern end-to-end.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>New `CELLanguage` rule type dispatched from the existing `runOPAOnSingleRule()` extension point in `core/pkg/opaprocessor/processorhandler.go`.</li><li>runCELOnK8s()` implementation: loads `ValidatingAdmissionPolicy` YAML from `cel-admission-library`, evaluates with `google/cel-go` in a VAP-compatible environment (`object`, `params`, stubbed `request`), maps violations to `reporthandling.RuleResponse`.</li><li>Equivalence guarantee documented: for `object`-scoped rules, `kubescape scan` and the cluster admission controller produce identical results. Known gap (`authorizer`, `request.userInfo`) documented.</li><li>10–20 existing regolibrary (Rego) controls converted to CEL and contributed to `cel-admission-library` as `ValidatingAdmissionPolicy` resources, with a conversion guide for future contributors.</li><li>Unit and integration tests; end-to-end verification showing a converted control evaluated identically by Kubescape and a live VAP on a real cluster.</li></ul>