Enhanced Rollouts features for application automation.
Go to file
xin gu 77e4b8dc2e
Update image_utils.go (#126)
Signed-off-by: xin gu <418294249@qq.com>
2023-03-21 13:39:31 +08:00
.github rolling deployment in partition-style (#115) 2023-02-10 10:57:55 +08:00
.license Add licenses and fix manifests generation (#21) 2022-03-10 19:55:42 +08:00
api/v1alpha1 rolling deployment in partition-style (#115) 2023-02-10 10:57:55 +08:00
config rolling deployment in partition-style (#115) 2023-02-10 10:57:55 +08:00
docs update README.md (#127) 2023-03-13 11:49:23 +08:00
hack rollout apis (#5) 2022-02-21 10:51:35 +08:00
lua_configuration/trafficrouting_ingress modify aliyun alb lua script (#123) 2023-02-27 11:00:11 +08:00
pkg rolling deployment in partition-style (#115) 2023-02-10 10:57:55 +08:00
scripts Code optimization (#25) 2022-04-20 20:22:38 +08:00
test Update image_utils.go (#126) 2023-03-21 13:39:31 +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
.golangci.yml Code optimization (#25) 2022-04-20 20:22:38 +08:00
.lift.toml Implementing a generic Ingress based on Lua And A/B Testing Release (#86) 2022-11-22 11:22:43 +08:00
CHANGELOG.md add v0.3.0 change log (#118) 2023-02-23 10:14:07 +08:00
Dockerfile Rewrite rollout controller code (#102) 2022-12-16 22:56:07 +08:00
Dockerfile_multiarch fix docker build arm64 failed (#117) 2023-02-13 09:45:58 +08:00
LICENSE Initial commit 2022-01-11 14:58:14 +08:00
Makefile dockerfile support multiarch(amd64,arm64) (#83) 2022-09-13 10:35:45 +08:00
OWNERS Add workflow actions and update Makefile (#20) 2022-03-10 19:28:49 +08:00
PROJECT rollout configs 2022-02-21 20:13:40 +08:00
README.md update README.md (#127) 2023-03-13 11:49:23 +08:00
go.mod trim off native deployment controller codes (#105) 2022-12-20 11:30:09 +08:00
go.sum Rewrite rollout controller code (#102) 2022-12-16 22:56:07 +08:00
main.go rolling deployment in partition-style (#115) 2023-02-10 10:57:55 +08:00

README.md

Rollouts

License

Introduction

Kruise Rollouts is a Bypass component that offers Advanced Progressive Delivery Features. Its support for canary, multi-batch, and A/B testing delivery modes can be helpful in achieving smooth and controlled rollouts of changes to your application, while its compatibility with Gateway API and various Ingress implementations makes it easier to integrate with your existing infrastructure. Overall, Kruise Rollouts is a valuable tool for Kubernetes users looking to optimize their deployment processes!

Why Kruise Rollouts?

  • Functionality

    • Supports canary and multi-batch delivery for various workloads, such as Deployment, CloneSet, and StatefulSet.
    • Supports Fine-grained traffic orchestration of application with Kubernetes Ingress and Gateway API.
  • Flexibility:

    • Handles both incremental and existing workloads with ease.
    • Be compatible with workload-referencing components like HPA, allowing for easy deployment and management of workloads.
    • Supports plug-and-play and hot-swapping, with immediate effect upon application, and the flexibility to be easily deleted at any stage, including during the rollout process.
  • Extensibility:

    • Extend to other workloads and traffic types easily with pluggable lua scripts.

Quick Start

Community

Active communication channels:

  • Slack: OpenKruise channel (English)
  • DingTalkSearch 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

  • The global idea is from both OpenKruise and KubeVela communities, and the basic code of rollout is inherited from the KubeVela Rollout.
  • This project is maintained by both contributors from OpenKruise and KubeVela.

License

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