This section describes how to edit grayscale release task settings.

Prerequisites

  • You need to join a project and have the Service Mesh Management permission in the project. For more information, see Project Members and Project Roles.

  • The KubeSphere Service Mesh extension must be installed and enabled on the KubeSphere platform.

Steps

  1. Log in to the KubeSphere web console with a user who has Service Mesh Management permissions and enter your workspace.

  2. Click Grayscale Release > Grayscale Release in the left navigation pane.

  3. On the Canary Release page, click Release Job, and then click the name of a canary release job to open its details page.

  4. In the Version area, click more in the upper-right corner of the new version, and then select Edit from the drop-down list.

  5. On the New Version Settings tab, click chevron-up/chevron-down to increase/decrease the number of pod replicas.

    Note

    Grayscale release does not support modifying the version number and container image of the new version.

  6. Click the Strategy Settings tab, configure the traffic routing strategy and release strategy for the grayscale release task, and then click OK.

    • For Blue-Green Deployment, click Take Over on the right side of the new or old version to forward all business traffic to that version.

    • For Canary Release tasks, you can choose to specify the traffic distribution ratio between the new and old versions, or forward requests to the new or old version based on request parameters.

      Parameter Description

      Specify Traffic Distribution

      Drag the slider to set the percentage of business traffic received by the new and old versions.

      Specify Request Parameters

      Forward requests with parameters meeting specific conditions to the new version, and other requests to the old version.
    Note

    Traffic Mirroring tasks send a copy of the business traffic to the new version for testing without actually exposing the new version, so there is no need to set a business traffic forwarding policy.

    • Strategy Settings > Release Strategy

      Parameter Description

      Immediate Switch

      Immediately switch all traffic to the corresponding version.

      Switch After Ready

      Automatically switch traffic after the corresponding version’s pods are ready.

      Pause Switch

      Actively pause traffic switching, maintaining the current traffic distribution state.