Grayscale Release
This section describes how to use the grayscale release feature.
When a container version needs to be updated, directly releasing a new version without sufficient testing to the production environment may pose significant risks to the business. Using the grayscale release feature, the business traffic in the production environment is forwarded to the new version being tested, thereby fully exposing and promptly fixing potential issues in the new version before its official release.
KubeSphere supports the following grayscale release modes:
-
Blue-Green Deployment: Sends business traffic to the new version for testing. If the new version does not function normally, the business traffic can be immediately switched back to the old version.
-
Canary Release: Allocates business traffic to both the new and old versions according to a certain ratio, ensuring business continuity while testing the new version.
-
Traffic Mirroring: Sends a copy of the business traffic to the new version for testing without actually exposing the new version.
| Note |
|---|
Grayscale release only supports composed apps, not apps based on templates. |
Create Grayscale Release Tasks
Learn how to create a grayscale release task.
View Grayscale Release Task List
Learn how to view the grayscale release task list.
View Grayscale Release Task Details
Learn how to view the grayscale release task details.
Switch Online Version (Blue-Green Deployment)
Learn how to switch the online version for a blue-green deployment task.
Adjust Traffic Distribution Ratio (Canary Release)
Learn how to adjust the traffic distribution ratio for a canary release task.
Edit Grayscale Release Task Settings
Learn how to edit grayscale release task settings.
Delete Grayscale Release Tasks
Learn how to delete a grayscale release task.
Previous
