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.
KubeEdge, as a native edge computing platform built on the Kubernetes ecosystem, offers capabilities such as reliable cloud-edge communication, edge autonomy, and IoT device integration. However, its ability to support intelligent model execution at the edge has yet to be systematically validated and practiced in real-world scenarios. This research aims to explore the feasibility and performance of deploying and running small language models on edge nodes using KubeEdge Expected Outcome: 1. Verification of KubeEdge's model deployment capability at the edge. Deployment and testing of model engines such as vLLM and llama.cpp on edge nodes, along with providing practical examples and detailed documentation for deploying small language models. 2. Exploration of integration schemes between KubeEdge and the OPEA platform. Connecting KubeEdge with OPEA’s model registry and workflow orchestrator to support automated model distribution and deployment from the cloud to edge nodes.
Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. It has inbuilt support for creating IaC artifacts for replatforming to Kubernetes/OpenShift. The project is actively developed with new features and bug fixes being added and it is being actively used by many users. There is a need for a concrete test suite to test various components of Move2Kube and integrate it to the existing CI/CD pipeline. Expected Outcome: A test suite for Move2Kube
Implement default resource interpreters for Volcano Job and Notebook workloads in Karmada. Expected Outcome: This includes developing interpreter logic in Golang and Lua, ensuring correct scheduling and propagation of these workloads across member clusters. Additionally, create documentation on how to run Volcano Job and Notebook on Karmada, and introduce the integration and best practices to the Volcano and Kubeflow communities.
istio.io is a large application in and of itself: static content is available in three languages with multiple versions, and a large testing infrastructure acts as the end-to-end testing for the Istio project, validating that the project works as documented whenever an update is made to the docs or Istio itself. In this project, you will be mentored towards maintainership of the Istio documentation build pipeline, including completing recently started work on multi-version availability and its integration with search engines, bringing the tooling for the deployment pipeline up to date, and laying groundwork for large content changes as ambient mode moves towards the default. - Expected Outcome: - Clean builds and publishes, with no lingering warnings or errors - Updated documentation on contributing tests, such that a new user can easily contribute testable documentation - Published process for users to see old versions of the docs, where we no longer publish them on istio.io
More pages need to be designed & added to the dashboard which are required to make great use of the functionalities of the karmada project using the web ui client.
The Volcano project currently uses Hugo for building its official website. However, current Hugo version of the website is pretty old and lacks modern features and flexibility, especially it is difficult to extend styles such as secondary menus, and there are problems such as invalid rendering of new markdown syntax. Docusaurus is a modern documentation framework that provides better support for versioning, localization, and theming. This mentorship focuses on modernizing the Volcano website by migrating it to Docusaurus, improving documentation structure, maintainability, and overall user experience. The project will involve replicating and enhancing the existing theme, restructuring documentation, improving navigation, and aligning the site with CNCF documentation best practices. The mentorship will also explore long-term maintainability and contributor-friendliness of the documentation workflow, especially to ensure that the documentation in the Volcano website is automatically synchronized with the documentation in Volcano's other code repos, using some automated tools like agents to keep the Volcano website up-to-date. - Expected Outcome: - Successful migration of the Volcano website from Hugo to Docusaurus - Improved documentation structure, navigation, and UX - A maintainable and contributor-friendly documentation setup - Clear contribution guidelines for future documentation updates
The KubeSlice project consists of multiple repositories that work together to provide application connectivity and network services across Kubernetes clusters. Currently, our E2E tests are outdated and need significant improvement. This project aims to automate the E2E testing process by improving the current test suite and implementing new tests where necessary. This will ensure that the entire KubeSlice ecosystem works seamlessly together. Expected Outcome: 1. A comprehensive set of E2E tests covering all critical functionalities of KubeSlice. 2. Integration of the E2E tests into the CI/CD pipeline to run automatically. 3. Clear Documentation for running & extending the E2E tests.
Antrea's PacketCapture feature (https://github.com/antrea-io/antrea/blob/main/docs/packetcapture-guide.md) includes custom BPF code generation for packet filters defined in the PacketCapture CRD. The code is currently tested using manually-generated test cases, which is tedious, error-prone, and limits testing coverage. Given that the code attempts to mimic the BPF generation done by tcpdump, we should improve the testing approach by: 1) using AI to generate comprehensive test inputs, 2) using tcpdump to generate reference BPF code for the inputs, 3) comparing our generated BPF with the tcpdump reference, 4) analyzing any differences to determine if our BPF is incorrect or equivalent, 5) updating our BPF generation to match tcpdump when possible, and 6) committing all test cases to run in CI. Expected Outcome: A comprehensive test suite for the PacketCapture BPF generation code that uses tcpdump-generated BPF as a reference. The test suite should be integrated into CI and should increase testing coverage compared to the current manually-generated test cases. Any discrepancies between Antrea's BPF generation and tcpdump's should be analyzed and resolved, with the BPF generation code updated as needed to match tcpdump's output when appropriate.
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
Kthena already possesses an autoscaler, but lacks ecosystem integration with peripherals such as HPA and KEDA. Consequently, users may harbour reservations when employing it. Therefore, there is a desire to optimise Kthena's autoscaler. - Expected outcome: - 1.The ecological integration of HPA and KEDA. - 2.Scaling capability of replicas for servingGroup and role - 3.Transition of HPA configuration - 4.UserGuide and Proposal - 5.Unit test and e2e test for the new feature
<p>On the Kyverno website, we want to introduce and document a set of technical outcomes that users can achieve by adopting Kyverno. These outcomes should group together Kyverno’s policy capabilities (validate, mutate, generate, verify images, cleanup) into clear, high-level goals that resonate with platform engineers, security teams, and developers.</p><p><br></p><p>Rather than focusing on individual features, this work will highlight what teams can accomplish with Kyverno in real-world environments.</p><p><br></p><p>Proposed technical outcomes include:</p><p>* Secure-by-Default Kubernetes – Enforce security and compliance policies across clusters automatically</p><p>* Policy-Driven Platform Engineering – Enable golden paths and self-service infrastructure using policy as code</p><p>* Automated Governance & Compliance – Continuously audit, report, and enforce organizational standards</p><p>* Software Supply Chain Security – Verify images, enforce provenance, and reduce risk in CI/CD pipelines</p><p>* Kubernetes Configuration Automation – Use mutation and generation to reduce manual configuration overhead</p><p>* Multi-Cluster Policy Management – Apply consistent governance across distributed and multi-cloud environments</p><p>* AI & Agent Governance – Apply policy controls to AI workloads and agent-driven infrastructure workflows</p><p><br></p><p>Each outcome should connect Kyverno capabilities to real-world use cases, supported by artifacts from the community such as blog posts, talks, policy examples, and reference architectures.</p><p><br></p><p>Expected Outcome:</p><p> * A new section of the Kyverno website dedicated to Technical Outcomes, where each outcome includes:</p><p> * A clear description of the problem space and desired outcome</p><p> * Mapping to Kyverno capabilities and policy types</p><p> * Links to supporting resources (blogs, videos, talks, GitHub examples, policy libraries)</p><p> * Optional diagrams or visual flows illustrating how Kyverno enables the outcome</p><p><br></p><p>This section should serve as:</p><p>* A learning and onboarding resource for new users</p><p>* A messaging bridge between technical features and business value</p><p>* A foundation for future content, including case studies, solution briefs, and AI-driven policy generation experiences</p><p><br></p>
<p>Krkn-AI's [discover command](https://krkn-chaos.dev/docs/krkn_ai/discover/) connects to a Kubernetes/OpenShift cluster and generates a static configuration file by enumerating cluster components (namespaces, pods, services, PVCs, nodes). While useful, the generated config still requires significant manual work before it can actually be used. Health check URLs are commented-out placeholders, the fitness function defaults to a single hardcoded PromQL query, and scenario selection is static regardless of what exists in the cluster. This issue proposes enhancing discover to produce a dynamic, cluster-aware configuration that is closer to runnable out-of-the-box. By inspecting routes, ingresses, services, and available Prometheus metrics during discovery, we can auto-populate health check URLs, suggest relevant fitness function queries scoped to discovered namespaces, and intelligently enable only the scenarios that apply to the discovered infrastructure.</p><p><br></p><p>Expected Outcome: </p><p> - Auto-discover OpenShift Routes, Kubernetes Ingresses, and Services to populate health check URLs in the generated configuration.</p><p> - Query Prometheus for available metrics to suggest namespace-scoped fitness function queries instead of hardcoded defaults.</p><p> - Intelligently enable chaos scenarios based on discovered cluster components (e.g., PVC, VMI, network interfaces).</p><p><br></p>
Want to be a cloud hacker? In the cloud, answering the question "who has access to what" is surprisingly complex: we need to know what identities exist, what permission policies and controls apply to them, what resources (storage, compute, networking) exist, what permissions apply to those, and we need to tie those together. Cartography (https://github.com/cartography-cncf/cartography) is an ambitious open source project that aims to do just that. In this project, our goal is to model and map cloud IAM relationships in GCP and Azure so users can answer “who can access what resources” across multi-cloud environments. We previously did this in AWS as seen in “IAM: Whatever You Say I Am”(https://eng.lyft.com/iam-whatever-you-say-iam-febce59d1e3b), and we would love to complete our coverage of this across the major cloud providers. Expected Outcome: 1. Design and implement support for evaluating permission objects in GCP and Azure to draw paths such as (:GCPUser)- [:CAN_READ]->(:GCPBucket) or (:AzureServicePrincipal)- [:CAN_READ]->(:StorageAccount). 2. Bonus: opportunity to author or co-author a blog post or video demo
Description: Kyverno is a Kubernetes native policy engine that secures and automates Kubernetes configurations. This project improves security posture and processes for Kyverno. Improve OSSF Security Scorecard results, define security processes, and add best practice processes like publishing signed images and build attestations for SLSA compliance.
Description: UnitedDeployment in OpenKruise enable users to manage a set of k8s workloads in whole while be able to customize the topology and replicas of each workload. This project extends the customization capability to arbitary workload fields by adding common patch fields, so that each subset of UnitedDeployment can have different metadata, container configuration etc. Expected Outcome: Support generate patches for new creating pods of each subset workload while the users can rollout and scale the UnitedDeployment in whole.
Hyperledger Iroha has implemented set of commands and queries. In the internship's project for few Iroha's queries (GetAccountTransactions and GetAccountAssetTransactions and optionally GetPendingTransactions) should be added optional arguments e.g.: from and to to return transactions in the provided time range or in provided blocks range. Problem description Fetching transactions in Iroha can be from first account's transaction or from provided transaction hash. On the other bound transactions are limited by max number of transactions to fetch. So when it is necessarily to fetch transactions for a month: hash of first transaction needs to be stored in blockchain and number of transactions should be "guessed" -if too big it would take longer, if too small another query would be necessarily). It also requires few queries instead of one. The mentee will be able to learn: 1) architecture of Iroha (1.x) 2) work in true spirit of open-source, communicating with Iroha community, joining calls 3) writing documentation 4) following rules of open-source code of Hyperledger Iroha, creating automatic tests of code Expected Outcome Implementation according to description and plan of documentation and tests. Added possibility of running modified queries from iroha-python library.
Hosted at play.meshery.io, build a unique learning environment for learning modern application networking through Meshery's support of every service mesh, orchestration of Kubernetes, and integration with many other CNCF projects. Meshery's genesis is that of helping teach people about service mesh technology and enabling to operate this type of cloud native infrastructure confidently. The proposed project is aimed at furthering this mission with interactive API documentation connected to a cloud native playground (a running instance of Meshery).
Create the world’s service mesh playground. Meshery’s genesis is that of helping teach people about service mesh technology and enabling to operate this type of cloud native infrastructure confidently. The proposed project is aimed at furthering this mission with interactive API documentation connected to a service mesh learning playground (a running instance of Meshery).
Inspektor Gadget is an eBPF tool and systems inspection framework for Kubernetes, containers and Linux hosts. Previously, Inspektor Gadget had a set of built-in gadgets. We are now moving to image-based gadgets where users can develop their own gadgets in eBPF and host them in OCI registries. But we don't have a test framework to help gadget authors to test their gadgets. This project will focus on implementing such a framework, possibly taking inspiration from the existing framework for built-in gadgets. The documentation for gadget authors should be updated. This project has the opportunity to expand beyond testing, to work on the gadget development experience over all, for example by creating a github template for gadget development. Expected Outcome: Gadget authors can test their gadgets
EdgeApplication can be overrides deployment spec(i.e. replicas, image, commands and environments) via the node group, and pod traffics are closed-loop in a node group(Deployments managed by EdgeApplication share a Service). But in the real scenario, the scope of nodes that need batch operations is different from that of nodes that need to collaborate with each other. Therefore, we need to have a solution to decouple the node cooperation ability and batch management ability of the edgeapplication. Expected Outcome: - Proposal of this issue's solution. - Achieve that edgeapplication can be overridden via the node group or node label selector. - Fix the issue of closed-loop flow control.
The Iroha 2 blockchain explorer is a web-based UI that inspects the entire state of an Iroha v2-based blockchain. In the scope of this internship, the mentee shall learn how to construct a frontend service to a blockchain, organise the UI and cater to unique challenges associated with the specific needs of specific blockchain ledgers such as Hyperledger Iroha v2. Learning Objectives The mentee shall learn how to: - Build a web-based UI in Vue. - Connect said Web-based UI to a backend service. - Implement UTF-8-based encoding of public keys (optional). - Learn about UI/UX challenges associated with making things work cross-platform, cross-form-factor. Expected Outcome - The state of the Iroha v2 blockchain explorer shall be improved.
Introduction Endorsement policy controls the approval of a proposal to be executed at various granular levels. In other words, this is the primary entity which is validated before a transaction is committed. Endorsement policy can operate at two different granularities: Namespace level: They can be set for the whole namespace. This is the default approach in which endorsement policies are specified in the chaincode definition, which is agreed to by channel members and then committed to a channel Individual key level: They can be set for individual state keys called private data collections. You can also specify an endorsement policy at the private data collection level, which would override the chaincode level endorsement policy for any keys in the private data collection. This would further restrict which organizations can write to a private data collection. Problem Statement This becomes complex to handle when operating at scale. Some use cases 1. Complex endorsement policy resolving for namespace level ones 2. Tracking Endorsement policies on large quantity Private data collections each having different endorsement policies 3. Resolving policy for a given object combining namespace level with overriding individual key-level ones.
RISC-V Performance Modeling SIG is driving the development of Performance Modeling and Simulation Tools for use across RISCV membership to foster collaboration across the community. To that end, the SIG has developed a trace-driven performance model of an example RISC-V superscalar processor using C++ based on the Sparta simulation framework. The performance model, named Olympia, has been adopted by multiple organizations in both industry and academia. We have identified set of features for further development of Olympia: * Add support for execution-driven modeling - https://github.com/riscv-software-src/riscv-perf-model/issues/14 * Model state of art branch predictors along with decoupled frontend using branch-prediction API, with an example being the BOOM processor frontend documented at https://docs.boom-core.org/en/latest/sections/branch-prediction/index.html - https://github.com/riscv-software-src/riscv-perf-model/issues/143 - https://github.com/riscv-software-src/riscv-perf-model/issues/1 * Develop an API for Interconnect model and implement an example Interconnect microarchitecture. - https://github.com/riscv-software-src/riscv-perf-model/issues/60 * Use the API for data/instruction prefetcher and implement an example prefetcher microarchitecture - https://github.com/riscv-software-src/riscv-perf-model/issues/142 * Enhance the existing vector extension implementation Etc.
When using StatefulSets with Local Volumes on Ephemeral Nodes - the StatefulSet Pods will get stuck in pending state when the Node is taken out of the cluster. In such cases, manual steps are required to verify that Node is out of the cluster, remove the PV and PVC and delete the failed StatefulSet replica to trigger the re-creation of a new replica with a new PVC/PV on a new node. This enhancement request is to build a generic operator that is driven by a configuration to automate the manual steps.