openkruise
/
rollouts
mirror of https://github.com/openkruise/rollouts.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Enhanced Rollouts features for application automation.
11 Commits 8 Branches 16 Tags 14 MiB
Go 98.6%
Lua 1.1%
Makefile 0.3%
Go to file
berg 574b31d093
adjusting the rollout directory structure (#19) 
Signed-off-by: liheng.zms <liheng.zms@alibaba-inc.com>
 		2022-03-10 16:07:42 +08:00
api/v1alpha1 rollout controller (#6) 2022-03-10 13:59:42 +08:00
config adjusting the rollout directory structure (#19) 2022-03-10 16:07:42 +08:00
docs/images update readme (#7) 2022-02-22 10:39:35 +08:00
hack rollout apis (#5) 2022-02-21 10:51:35 +08:00
pkg adjusting the rollout directory structure (#19) 2022-03-10 16:07:42 +08:00
test batchrelease controller (#9) 2022-03-10 14:15:41 +08:00
.dockerignore init project (#1) 2022-01-14 13:38:36 +08:00
.gitignore rollout configs 2022-02-21 20:13:40 +08:00
Dockerfile adjusting the rollout directory structure (#19) 2022-03-10 16:07:42 +08:00
LICENSE Initial commit 2022-01-11 14:58:14 +08:00
Makefile rollout controller (#6) 2022-03-10 13:59:42 +08:00
OWNERS Add OWNERS 2022-02-21 10:48:57 +08:00
PROJECT rollout configs 2022-02-21 20:13:40 +08:00
README.md credit vela (#11) 2022-03-09 10:27:41 +08:00
go.mod batchrelease controller (#9) 2022-03-10 14:15:41 +08:00
go.sum rollout controller (#6) 2022-03-10 13:59:42 +08:00
main.go adjusting the rollout directory structure (#19) 2022-03-10 16:07:42 +08:00

README.md

Rollouts

License

Introduction

Kruise Rollouts is a Bypass component which provides advanced deployment capabilities such as canary, traffic routing, and progressive delivery features, for a series of Kubernetes workloads, such as Deployment and CloneSet.

arch

Why Kruise Rollouts?

  • Functionality：

    • Support multi-batch delivery for Deployment/CloneSet.
    • Support Nginx/ALB/Istio traffic routing control during rollout.

  • Flexibility:

    • Support scaling up/down to workloads during rollout.
    • Can be applied to newly-created or existing workload objects directly;
    • Can be ridden out of at any time when you needn't it without consideration of unavailable workloads and traffic problems.
    • Can cooperate with other native/third-part Kubernetes controllers/operators, such as HPA and WorkloadSpread.

  • Non-Invasion:

    • Does not invade native workload controllers.
    • Does not replace user-defined workload and traffic configurations.

  • Extensibility:

    • Easily extend to other traffic routing types, or workload types via plugin codes.

  • Easy-integration:

    • Easily integrate with classic or GitOps-style Kubernetes-based PaaS.

Documents

Coming soon ...

Community

Active communication channels:

  • Slack: OpenKruise channel (English)
  • DingTalk：Search GroupID 23330762 (Chinese)
  • WeChat: Search User openkruise and let the robot invite you (Chinese)
  • Bi-weekly Community Meeting (APAC, Chinese):
  • Bi-weekly Community Meeting (English): TODO

Acknowledge

  • Part of the codes of this project is powered by KubeVela Community.
  • This project will be maintained and improved by both the communities of OpenKruise and KubeVela.

License

Kruise rollouts is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.