Fetching the latest programs, projects, and workspace data.
Native kubernetes configmap can reload dynamically but lack progressive rollout capability. OpenKruise community had comes up with the [design of new workload](https://github.com/openkruise/kruise/pull/1948) for configmap rolling update, and the [initial implementation](https://github.com/openkruise/kruise/pull/2149) has been running in one end user environment. However the current implementation is not generic enough and had many limitations. The goal is to complete the implementation in a more generic way and to support many configuration reloading strategies. - Expected Outcome: 1. The code for dynamic configmap rollout controller (ConfigMapSet) 2. Unit and integration tests 3. Documentation for the usage of ConfigMapSet
Showing 5 of 21 projects. Click any project card for scope, mentors, and proposal studio.
Implement fuzz testing for OpenKruise using a suitale tool like oss-fuzz. Generate a comprehensive input set to guide the fuzz testing, and identify features that accept complex user inputs for testing. Document the entire process for repeatability in future versions and integrate the fuzz testing into CI pipeline. Expected Outcomes: - Add a fuzz test that covers important features including workoadspread,uniteddeployment, sidecarset and resourcedistribution. - Enable continuous fuzzing using [OSS-Fuzz](https://github.com/google/oss-fuzz).
Native kubernetes configmap can reload dynamically but lack progressive rollout capability. OpenKruise community had comes up with the [design of new workload](https://github.com/openkruise/kruise/pull/1948) for configmap rolling update, and the [initial implementation](https://github.com/openkruise/kruise/pull/2149) has been running in one end user environment. However the current implementation is not generic enough and had many limitations. The goal is to complete the implementation in a more generic way and to support many configuration reloading strategies. - Expected Outcome: 1. The code for dynamic configmap rollout controller (ConfigMapSet) 2. Unit and integration tests 3. Documentation for the usage of ConfigMapSet
The OpenKruiseGame Dashboard is presently in its basic form, and we aim to significantly expand its functionality going forward. We plan to introduce features such as the ability to filter game servers and perform batch updates on them. Expected Outcome: new release Dashboard which supports searching, querying, updating objects in batch.
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.
<p>Dynamic volume mounting enables data persistence and sharing for pooled sandbox pods without relying on CSI plugins. This capability is essential for Agent workloads such as OpenClaw and Hermes, which need to save workspace data and share skills across sandboxes. Currently, OpenKruise Agents lacks support for open-source storage solutions like JuiceFS and Ceph, limiting adoption in on-premises environments. This project aims to integrate these storage backends by implementing CSI-plugin sidecars compatible with the Agent runtime and modifying the sandbox controller to support generic CSI volume mounting.</p><p><br></p><p>Expected Outcome:</p><p> - CSI-plugin sidecars for JuiceFS and Ceph that integrate seamlessly with the Agent runtime in OpenKruise Agents</p><p> - Sandbox controller enhancements to enable mounting of generic CSI volumes</p><p> - E2E tests covering core SandboxClaim flows involving JuiceFS and Ceph storage</p><p> - Comprehensive user-facing documentation published on the OpenKruise website and repository</p><p><br></p>