karmada-io/api

Karmada APIs

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

karmada-io/api has 10+ stars and 10+ forks on GitHub, is written in Go, and was last pushed on Mar 10, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on May 31st, 2021
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 13
Total Stargazers: 17 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 0.0 hours
90th percentile: 0.0 hours
Tracked items: 1

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

Karmada API is a Go library that defines the canonical API types served by Karmada, a multi-cluster Kubernetes orchestration system.

This repository solves the problem of providing a single source of truth for Karmada's API schema definitions. Rather than embedding API types directly in the main Karmada project, the API definitions are maintained separately and can be consumed as a dependency by client libraries and tools that need to interact with Karmada clusters. Developers work with Go types that can be serialized directly to JSON, enabling type-safe interactions with Karmada APIs.

The primary use case is as a dependency of client-go libraries. Developers building tools, controllers, or clients that communicate with Karmada should use the Go types provided by this repository. The repository maintains compatibility with the main Karmada project through synchronized branching and tagging, ensuring that versions align across both repositories.

The project operates as a read-only mirror of the API definitions maintained in the main Karmada repository. All code changes originate in the primary Karmada project, are merged there, and are subsequently synced to this repository. This one-way synchronization model means contributors should not attempt to make changes directly in this repository but instead submit modifications upstream to the canonical source.