openkruise
/
kruise-game
mirror of https://github.com/openkruise/kruise-game.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update README (#3) 

Signed-off-by: ChrisLiu <chrisliu1995@163.com>

Signed-off-by: ChrisLiu <chrisliu1995@163.com>
This commit is contained in:
ChirsLiu 2022-09-23 10:35:53 +08:00 committed by GitHub
parent 6d1ba7469f
commit f1d292984b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -1,10 +1,16 @@
# kruise-game # kruise-game
## Introduction ## Introduction
`Kruise-Game` is an open source project based on OpenKruise, to solve the problem of game server landing in Kubernetes. Kruise-Game is a subproject of OpenKruise, to solve the problem of game server landing in Kubernetes.
<img width="250px" src="./docs/images/logo.jpg" alt="OpenKruiseGame logo"/> <img width="250px" src="./docs/images/logo.jpg" alt="OpenKruiseGame logo"/>
Kruise-Game utilizes the features of [Kruise](https://github.com/openkruise/kruise), including:
- In-Place Update
- Update sequence
- Ordinals reserve(skip)
- Pod probe marker
- …
## Why is Kruise-Game? ## Why is Kruise-Game?
Game servers are stateful services, and there are differences in the operation and maintenance of each game server, which also increases with time. In Kubernetes, general workloads manages a batch of game servers according to pod templates, which cannot take into account the differences in game server status. Batch management and directional management are in conflict in k8s. **Kruise-Game** was born to resolve that. Kruise-Game contains two CRDs, GameServer and GameServerSet: Game servers are stateful services, and there are differences in the operation and maintenance of each game server, which also increases with time. In Kubernetes, general workloads manages a batch of game servers according to pod templates, which cannot take into account the differences in game server status. Batch management and directional management are in conflict in k8s. **Kruise-Game** was born to resolve that. Kruise-Game contains two CRDs, GameServer and GameServerSet:

11
docs/getting_started/introduction.md
View File

@ -1,7 +1,16 @@
# Introduction # Introduction
## What is Kruise-Game? ## What is Kruise-Game?
Kruise-Game is an open source project based on OpenKruise, to solve the problem of game server landing in Kubernetes. Kruise-Game is a subproject of OpenKruise, to solve the problem of game server landing in Kubernetes.
<img width="250px" src="../images/logo.jpg" alt="OpenKruiseGame logo"/>
Kruise-Game utilizes the features of [Kruise](https://github.com/openkruise/kruise), including:
- In-Place Update
- Update sequence
- Ordinals reserve(skip)
- Pod probe marker
- …
## Why is Kruise-Game? ## Why is Kruise-Game?
Game servers are stateful services, and there are differences in the operation and maintenance of each game server, which also increases with time. In Kubernetes, general workloads manages a batch of game servers according to pod templates, which cannot take into account the differences in game server status. Batch management and directional management are in conflict in k8s. **Kruise-Game** was born to resolve that. Kruise-Game contains two CRDs, GameServer and GameServerSet: Game servers are stateful services, and there are differences in the operation and maintenance of each game server, which also increases with time. In Kubernetes, general workloads manages a batch of game servers according to pod templates, which cannot take into account the differences in game server status. Batch management and directional management are in conflict in k8s. **Kruise-Game** was born to resolve that. Kruise-Game contains two CRDs, GameServer and GameServerSet: