openkruise/kruise-api

The canonical location of the Kruise API definition.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

openkruise/kruise-api has 30+ stars and 20+ forks on GitHub, is written in Go, and was last pushed on Dec 26, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 minute ago
Added to GitGenius on October 15th, 2026
Created on March 24th, 2020
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 23
Total Stargazers: 30 (+0)
Total Subscribers: 3 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kruise-api is a Go library that provides the canonical API type definitions and client for OpenKruise.

The library solves the problem of accessing and working with OpenKruise API types by centralizing the schema definitions in a single, versioned repository. It includes Go type definitions for the apps and policy packages, a clientset for interacting with the Kruise API, and OpenAPI schema documentation. Developers can import these types directly into their applications and serialize them to JSON without needing to maintain their own copies of the API definitions.

Teams building applications that interact with OpenKruise should use this library rather than copying API definitions manually. It suits any project that needs to programmatically create, update, or delete Kruise resources. The library follows semantic versioning aligned with Kruise releases, so a Kruise v1.x.y release corresponds to a kruise-api v1.x.z release, with patch versions incremented for bugfixes. The README provides an example demonstrating how to create, update, and delete CloneSet resources.

The project is maintained as a read-only mirror synced from the main Kruise repository, with all code changes made upstream and subsequently synchronized here. This architecture means the project does not accept direct pull requests but instead receives updates through automated synchronization from the source repository.