-
Notifications
You must be signed in to change notification settings - Fork 621
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: 守辰 <[email protected]>
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -389,3 +389,27 @@ Expected Outcome: Gadget developers have a way to run unit tests in different ke | |
- Florent Poinsard (@frouioui, [email protected]) | ||
- Matt Lord (@mattlord, [email protected]) | ||
- Upstream Issue: https://github.com/vitessio/website/issues/1798 | ||
|
||
### OpenKruise | ||
|
||
#### Visualize Kruise Rollout progress with kubectl plugin | ||
- Description: [Kruise Rollout](https://github.com/openkruise/rollouts) provide plugin-n-play progressive delivery for cloud native apps. The goal of this project is to develop a kubectl plugin so as to visualize rollout progress, e.g. the rollout steps, traffic status and involved pods. The kubectl plugin can leverage the existing [kruise kubectl plugin project](https://github.com/openkruise/kruise-tools), and can use the [Argo kubectl plugin](https://argo-rollouts.readthedocs.io/en/stable/features/kubectl-plugin/#visualizing-rollouts-and-experiments) as a reference. | ||
- Expected Outcome: | ||
* kruise-tools enhancement for kruise rollout visualization | ||
* Well-documented with clear usage instructions and examples | ||
- Mentor(s): | ||
- Zhang zhen (@furykerry, [email protected]) | ||
- Zhao Mingshan (@zmberg, [email protected]) | ||
- Recommended Skills: Kubernetes, GoLang | ||
- Upstream Issue: https://github.com/openkruise/kruise-tools/issues/94 | ||
|
||
#### Game operation and maintenance API | ||
- Description: kruise-game contains two CRDs GameServer and GameServerSet. Game servers can be managed by deploying or changing the corresponding CR. However, in actual production use, a release or operation and maintenance action is often a combination of a series of operations on CR. For example, set the GameServer image tag with ids 1, 7, and 10 to v0.3; adjust the update priority of GameServer with ids 5, 9, and 11 before updating the game server, etc. Therefore, a set of APIs with operation and maintenance semantics is needed, which users can directly use or integrate into their own operation and maintenance platform to facilitate operation and maintenance operations. | ||
- Expected Outcome: | ||
* A service component that includes multiple APIs | ||
- Recommended Skills: Golang, Kubernetes, RESTful API | ||
- Mentor(s): | ||
- Liu Zhongwei(@ringtail , [email protected]) | ||
- Liu Qiuyang (@chrisliu1995 , [email protected]) | ||
- Upstream Issue: https://github.com/openkruise/kruise-game/issues/166 | ||
|