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.
This ongoing “Sailing Downstream” project strives to transform the salient content from within the RISC-V Sail specification into a more accessible format, JSON, that downstream projects can easily and automatically transform into the content necessary to their project which is currently produced by manual effort. Project efforts and components span: - Adding to the RISC-V Sail specification information necessary for the various downstream projects. - Improving the RISC-V Sail specification so that the salient information can be easily identified and extracted. - Enhancing an existing Sail “JSON backend” to extract salient information completely and accurately and produce that information in a usable JSON format. As the end goal is to enable automatic adoption of changes, enhancements, and new content of the RISC-V ISA into downstream projects, efforts can be made to provide example implementations of such transformations to inform engagement with select downstream projects for adopting new automated processes.
Build an Envoy plugin to support authorisation based on Kyverno policies. Expected Outcome: Enable users to perform autorisation with similar concepts as kyverno and kyverno-JSON using policies.
Meshery UI lacks a permissions framework. The existing internal implementation is simple, fragile and must be completely rewritten. The approach to implemention a permmissions framework includes using React.js and CASL.js. Meshery UI's approach needs to be extensible given that this framework will be an extension point for Remote Providers to supply their own permissions. - Expected outcome: Definition of permissions and their enforcement in Meshery with an aim for deep granularity and extensibility with each user interface input component carrying a unique permission key id. Each key is then put into a group of keys in a keychain, keychains assigned to user roles, in turn, roles assigned to users. With users having the ability to create own custom roles, the framework will be dynamic based on the associated server-side permissions for the currently auth’ed user. - Upstream Issue (URL): https://github.com/meshery/meshery/issues/7436, https://github.com/meshery/meshery/issues/7382
Meshery the CNCF’s 10th fastest growing project. As a cloud native manager, Meshery [integrates with 250+ projects](https://meshery.io/integrations) and technologies. For each CNCF project integrated with Meshery, tutorials, sample designs, and deployment patterns with reference architectures need to be created. For the earnest, DevOps-minded intern, this internship represents a vast opportunity to learn, document, and publish tutorials and best practices not only around Meshery, but for any number of the other CNCF projects, too. You will use the [Meshery Playground](https://play.meshery.io) Expected Outcomes: - 25+ new design patterns published in Meshery Catalog and Artifact Hub. - 5 new Meshery tutorials published in Meshery Docs. - Bonus: Extend one or more of Meshery’s Learning Paths.
Meshery (https://meshery.io) is a self-service engineering platform, Meshery enables collaborative design and operation of cloud native infrastructure. The Meshery Design System is a flexible, scalable design system built on the foundations of accessibility, beautiful design, and consistent user experience. - 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.
A language server is what makes it possible to rich editing like to go to definition or code completions in source code editors. The Solang Solidity Compiler does have a language server, but it is very rudimentary. The aim of this mentorship is to make the language server much more complete, will make developing Solidity code using this language server will be a much greater developer experience. During this mentorship you will learn how language servers work, and you'll need to walk the parsed Solidity abstract syntax tree in various ways to for example find where a variable is defined (Go to definition), or to find all usages of a variable (Find all references), or find the type definition (Go to type definition). This means walking a complex data structure, and understanding how source code is represented as a abstract syntax tree, which is the result of parsing and semantic analysis, the first stage of an compiler.
cilium.io could benefit from SEO pillar pages that capture higher level problems that people will search for. Each page should deep dive into a comprehensive overview of the topic and contain high quality architectural images and diagrams that will also be discovered in search. These pages will capture high-intent search traffic and guide users from "Curious" to "Installed." Expected Outcome: 8 pillar pages with content and images deployed on the website
Up to four versions of Istio are supported at one time, and so the documentation for each must be available. Our current site search is outdated and needs to be replaced, so that the search content only exists in the site search, and only fresh content is available on google.com. Expected Outcome: Working site search on istio.io, which lets you search for content for the currently supported versions.
Drasi is a Data Change Processing platform that enables developers to detect and react to meaningful data changes using declarative Cypher queries. Drasi excels at complex change detection with unique features like `drasi.trueFor()` (detecting conditions that persist over time) and absence-of-change detection (alerting when expected events don't occur). However, it currently lacks native connectivity to IoT protocols. Drasi Lib provides Drasi's powerful graph-aware decision engine as an embeddable Rust library that can run completely offline on constrained hardware—enabling edge computing scenarios where logic runs directly on sensors and gateways. IoT applications fundamentally need to detect state transitions, but developers typically must write boilerplate code and manage state persistence manually. Drasi's diff-engine handles state management and change computation automatically, emitting events only when meaningful changes occur. MQTT (Message Queuing Telemetry Transport) is the de-facto standard protocol for IoT, used by AWS IoT Core, Azure IoT Hub, and virtually every IoT deployment. Adding MQTT support to Drasi Lib will unlock the entire IoT ecosystem for Drasi users. In this project, the mentee will build a suite of lightweight Rust crates that enable Drasi Lib to communicate with MQTT brokers. They will create connectors to ingest sensor data (MQTT Source), execute local actions (Shell Reaction), and close the control loop (MQTT Reaction).
Description: Elekto is a project for running preference elections for open source projects hosted by the CNCF. It is used for elections for the Kubernetes and Knative projects, and will soon be used by others. During the 2021 elections, a security audit identified several areas of improvement in both in the security and privacy of Elekto, and in the security of the Kubernetes deployment. The mentee for this project would be implementing those recommendations in order to make Elekto and Kubernetes elections more secure.
<p>[Kueue](https://github.com/kubernetes-sigs/kueue) is a Kubernetes-native job queueing system for managing batch workloads and resource sharing across clusters. This project builds a Headlamp plugin that adds a **Kueue** section to kubernetes-sigs/Headlamp, surfacing Kueue CRDs so operators can **view and manage queues, workloads, and resource allocation** from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and optional metrics embedding.</p><p>- Expected Outcome:</p><p> - Plugin exposes key Kueue CRDs: ClusterQueue, LocalQueue, Workload (and related queueing resources).</p><p> - List views, with summary columns (name, namespace, queue, priority, resources, status).</p><p> - Detail pages, showing config, status conditions, queue placement, admitted workloads, and basic actions (pause/resume workloads, inspect queue state).</p><p> - Relational navigation, clusterQueue → localQueues → workloads; workload → owning queue.</p><p> - Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements.</p><p> - Structured config display (collapsible sections/YAML toggle), humanized statuses, validated forms for mutating actions.</p><p> - README with prerequisites and limitations; blog post demoing usage.</p><p><br></p>
These pages on the web dashboard will help to perform different operations for Override policies, Resource Binding in karmada.
This project aims to systematically analyze and substantially improve KubeArmor's unit test coverage. It involves identifying untested code paths, designing and implementing new unit tests for crucial modules, and establishing a robust testing framework to boost code quality. Goals: 1. Measure Coverage: Accurately measure and report current unit test coverage for all Go packages. 2. Prioritized Test Implementation: Write new unit tests, prioritizing core modules like core, monitor, enforcer, log, and feeder, and addressing other packages with no test files. 3. Identify Untested Components: Pinpoint major untested functionalities and propose specific test scenarios. 4. Achieve Measurable Improvement: Submit pull requests that significantly increase overall unit test coverage. Expected Outcome: A detailed coverage report, a suite of new, effective unit tests, and a measurable improvement in test coverage, leading to enhanced code quality and reliability.
Description: Thanos is a distributed system that has a user interface written in React. Let's create a community instance with continuous integration for easy testing of how Thanos works. Also, it could serve as a testing ground for new React components. A server is provided by CNCF (https://github.com/cncf/cluster/issues/190).
Interested Interns: DO NOT apply through this platform. Due to a bug, it does not contact the Mentor. Please go to https://wiki.lfnetworking.org/x/EqsZB. nRead the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org nSelected interns will then apply here to finalize their paperwork. n nODL CI/CD toolchain, as most of the LFN ones, is based on Jenkins which has developed new key features around Kubernetes not yet implemented by ODL (more generally LFN). nAs part of ODL IT modernization, the proposal here is to update our system by switching from agents running on baremetal or on virtual machines to containers running on a Kubernetes cluster. nThe clear first benefit is to make sure that resources are used effectively when testing our patchsets and when building our distributions. nBut, as important, it also enforces clean isolation between jobs and increase the capability to troubleshot the continuous integration issues more easily. nIt should be noted that this topic was also discussed during LFN Events in Anuket tracks and many projects could be very interested in these actions.
KWOK (Kubernetes WithOut Kubelet) is a toolkit that enables setting up a cluster of thousands of Nodes in seconds. KWOK is currently being used by a number of projects for testing and performance. It is crucial that KWOK itself behaves consistently. The following tests are currently being considered: Unit Test, E2E Test, Edge Cases. Expected Outcome: Improved test coverage for KWOK.
Description: WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. WasmEdge is an official sandbox project hosted by the CNCF. WasmEdge is designed for the general purpose wasm runtime. However, when running rustpython, we found the performance is worse than other runtimes such as wasmtime, even after using the ahead-of-time compilation.
Meshery design is a common practice of both configuring and operating cloud native infrastructure functionality in a single, universal file. We are seeking to enhance Meshery's capabilities by supporting automatic versioning of Meshery designs based on user sessions. This functionality will enable users to track changes made to their designs by individuals, facilitating the ability to rollback changes at any time. Expected Outcomes: - Update Meshery server and pattern engine to support Meshery design versioning. - Update UI to allow users to perform actions related to design versioning. - Document changes made in pattern engine and server.
KubeEdge-Ianvs currently focuses on edge-cloud collaborative learning (training and inference) for a single modality of data. However, edge devices, such as those in autonomous vehicles, often capture multimodal data, including GPS, LIDAR, and Camera data. Single-modal learning can no longer meet the precise inference requirements of edge devices. Therefore, this project aims to integrate mainstream multimodal large model joint learning algorithms into KubeEdge-Ianvs edge-cloud collaborative learning, providing multimodal learning capabilities. Expected Outcome: A benchmark suite for multimodal large language models deployed at the edge using KubeEdge-Ianvs - Modify and adapt the existing edge-cloud data collection interface to meet the requirements of multimodal data collection - Implement a Multimodal Large Language Model (MLLM) benchmark suite based on Ianvs - Reproduce mainstream multimodal joint learning (training and inference) algorithms and integrate them into Ianvs single-task learning - (Advanced) Test the effectiveness of multimodal joint learning in at least one of Ianvs' advanced paradigms (lifelong learning, incremental learning, federated learning, etc.).
<p>OpenEverest is an open-source cloud-native database platform that helps developers deploy and manage PostgreSQL, MySQL, MongoDB, and other databases on Kubernetes. Currently, `everestctl` serves primarily as an installation tool for deploying and deleting OpenEverest itself. However, users increasingly need a powerful command-line interface to manage their databases, clusters, and integrations directly from the terminal. This project aims to transform `everestctl` from a basic deployment tool into a comprehensive CLI for managing OpenEverest resources. The mentee will design and implement a modern, user-friendly CLI experience that allows users to provision databases, manage Kubernetes clusters, interact with OpenEverest plugins, and automate database operations — all without leaving their terminal. The project will involve working with Go, Kubernetes APIs, OpenEverest's plugin architecture, and modern CLI frameworks like Cobra.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Core database management commands: `everestctl db list`, `create`, `delete`, `get`, `logs` for PostgreSQL, MySQL, and MongoDB</li><li>Cluster management: `everestctl cluster list`, `register`, `status` for managing Kubernetes clusters</li><li>Plugin integration: `everestctl plugin list`, `install`, `configure` for OpenEverest plugins</li><li>Shell completion scripts (bash, zsh, fish)</li><li>Unit and integration tests with >80% coverage</li><li>Comprehensive documentation with usage examples</li></ul>
In the latest release, KubeEdge has implemented the ability for image pre pull. However, each task execution only supports images from the same image repository currently. We hope to enhance this feature to support capabilities like overriding images and secrets, complete end-to-end tests for this feature. Expected Outcome: Support image and secret override in image pre pull feature. And E2e tests for this feature are added.
Meshery's MeshSync component acts as the real-time discovery engine, maintaining an up-to-date snapshot of all managed infrastructure. Currently, mapping the complex relationships between these resources (e.g., a Service selecting Pods which are mounted to PVCs) relies on relational or in-memory lookups that can become inefficient at scale. This project involves integrating a dedicated graph database (or an embedded graph processing library) into Meshery's architecture. The goal is to ingest discovered Kubernetes resources as "nodes" and their associations (OwnerReferences, Label Selectors, Annotations) as "edges." This shift will enable highly efficient traversal and querying of infrastructure data, powering more advanced capabilities like topology visualization, impact analysis, and dependency mapping. Expected Outcome: 1. Fully-functional datastores of discovered cluster data into a graph structure. 2. Benchmarks demonstrating improved performance for complex relationship queries compared to the existing relational implementation. 3. Successful rendering of the infrastructure topology in Meshery UI using data fetched from the new graph backend. 4. Comprehensive documentation covering the new graph schema and query patterns.
Kubescape can detect vulnerabilities in a container image. Some can automatically be remediated by changing the base image version (or other package information) inside the Dockerfile which created the image. This project is to automate this remediation. - Expected Outcome: An enhancement to Kubescape to generate a Dockerfile that proposes fixes for vulnerabilities found in a container image. This may be by integration with existing open source tools or developing something new.
Antrea currently relies on Github's Dependabot to automatically updated dependencies (Go modules / Github Actions) on the main branch. There is a key limitation with Dependabot, which is that it doesn't support automatically updating dependencies with security vulnerabilities in "active" release branches (for Antrea minor versions which are currently actively supported). This limitation means that maintainers have to manually backport Dependabot patches when they address security vulnerabilities, which has become a burden. Renovate (https://docs.renovatebot.com/) is an alternative tool for dependency management, and it seems that it offers richer configuration options and may not suffer from the same limitation as Dependabot. Expected Outcome: Migrate the Dependabot config to a Renovate config for the main Antrea repository (antrea-io/antrea), as well as for all other repositories (under the antrea-io organization) which currently use Dependabot. Dependencies that are currently updated as a group (e.g., golang.org/x modules) should remain that way. The Renovate config should include provisions to automatically perform security updates in active release branches. The change should not impact developer workflows and the Antrea release cycle; all experiments should be performed in a fork.