openkruise/kruise-game

Game Servers Management on Kubernetes

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

openkruise/kruise-game has 1k+ stars and 150+ forks on GitHub, is written in Go, and was last pushed on Jul 24, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 52 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 22nd, 2022
Open Issues & Pull Requests: 49 (+0)
GitHub issues: Enabled
Number of forks: 175
Total Stargazers: 1,080 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.8 hours
Mean response time: 28.7 days
90th percentile: 60.1 days
Tracked items: 58

How this project is maintained

63% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Three people close 68% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 445 days
Stale 30+ days: 24
Stale 90+ days: 23

Recent activity

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

Top labels

  • good first issue (2)
  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kruise-Game is a Kubernetes workload specialized for managing game servers on cloud infrastructure.

The project addresses the mismatch between Kubernetes' standard pod lifecycle and the requirements of game server deployments. Game servers typically need hot updates and hot reloads to maintain player sessions without interruption, but Kubernetes' default behavior recreates pods when images change, causing player disconnections and network metadata shifts. Kruise-Game solves this by providing a custom workload designed specifically for game server scenarios, offering features like in-place updates that modify running containers without pod recreation, hot update capabilities, and management of individual game servers rather than treating them as interchangeable replicas.

Teams running multiplayer game servers on Kubernetes should consider this tool if they need to avoid player session disruption during updates or require fine-grained control over individual server instances. The project suits organizations performing cloud-native transformation of existing game server infrastructure and those building new game services on Kubernetes across single or multiple cloud providers. It integrates with external systems including matchmaking services, logging, monitoring, and delivery platforms like KubeVela, allowing teams to build complete release and operations platforms. The tool can be used through Kubernetes templates or APIs, supporting both low-code integration and custom development.

The project maintains active development with regular commits across its codebase. The maintainers respond to issues and pull requests consistently. Documentation is kept current in both English and Chinese, reflecting ongoing investment in accessibility for the user base. Test coverage is tracked and maintained as part of the development process.