How OpenKruiseGame Enables Cloud‑Native Game Operations and Delivery

OpenKruiseGame (OKG) is a CNCF‑graduated OpenKruise extension that provides a game‑specific abstraction for running game workloads on Kubernetes. It adds multi‑cloud and hybrid‑cloud support via a Cloud Provider model and offers declarative integration with cloud services such as lossless networking, sub‑second elasticity, low‑cost resources, and full lifecycle observability.

Key Capabilities

Non‑intrusive declarative configuration of common game functions: hot‑updates, fixed IP/port allocation, server‑group management, and auto‑scaling.

Semantic APIs for matchmaking, room lifecycle, and state management.

Support for a wide range of game types (PvP, PvE, H5, MMORPG) and complex server architectures.

PvP (Session‑Based) Game Best Practices

Session‑based games require short, non‑continuous sessions, multiple players per room, low latency, and variable traffic peaks. An OKG‑based architecture should provide:

Direct network access with a unique public address for each game room.

Matchmaking service that pairs players and allocates rooms.

Automated state management for room lifecycle.

Elastic scaling that matches peak demand while controlling cost.

High‑efficiency delivery and operations automation.

Full guidance: https://openkruise.io/zh/kruisegame/best-practices/session-based-game

PvE Game Best Practices

PvE games run long‑lived server instances, often with configuration differences at launch, multiple processes per container, and the need for targeted resource, image, and merge management over time. Native Kubernetes workloads face several limitations:

Deployment : Pods lack sequential identifiers, preventing stateful service discovery, per‑server differentiation, and reliable restart handling.

StatefulSet : Ordered updates only support descending order and cannot address per‑server state differences.

Script‑based batch launches are procedural, lack persistent parameters, and are error‑prone.

GitOps generates large numbers of repetitive YAML files, complicating bulk releases.

Custom PaaS solutions require extensive development and tightly couple business logic, hindering iteration.

Full guidance: https://openkruise.io/zh/kruisegame/best-practices/pve-game

Cloud‑Native Game Delivery Workflow

Developers push code to a repository, triggering CI to build container images. ArgoCD automatically deploys the image to a test environment, enabling rapid verification without operations involvement and ensuring parity with production. For staging or gray releases, operators maintain a deployment repository containing GameServer YAML definitions; applying these manifests launches or updates game servers. The KubeSphere OKG Dashboard visualizes all server sets and individual servers, allowing targeted operational actions.

OKG Dashboard Features

The dashboard, built on KubeSphere 4.0 LuBan, provides white‑screen management of GameServerSet and GameServer objects. It displays overall server statistics, per‑set health, and individual server status, and supports state changes directly from the UI.

References

OpenKruiseGame official documentation: https://openkruise.io/zh/kruisegame/introduction

GitHub repository: https://github.com/openkruise/kruise-game

OKG Dashboard marketplace page: https://kubesphere.com.cn/marketplace/extensions/kruise-game-dashboard/