Gray Releasing an Application in Kubernetes (CCE Cluster) with Nginx-Ingress

Prerequisites

• A CCE cluster is available. You may be charged during the process. For details, see CCE Billing.
• The NGINX Ingress controller is installed in the CCE cluster.

Configuring Deployment Actions

1. Create an application by referring to Creating an Application.
2. On the Deployment Actions page, add this deployment action based on the service scenario.
3. Configure the action using the parameters described in the table below.

   Table 1 Parameters

   Parameter	Description
   Action Name	Custom action name. Enter 1 to 128 characters. Do not start or end with a space. Use letters, digits, spaces, and these special characters: -_,;:./()
   Tenant	Current: The software package is deployed in a CCE cluster of the current tenant for release. Select Current. The current tenant must have the CCE cluster operation permission. If not, enable IAM authorization to select an authorized user from the User drop-down list for deployment. Other: The software package is deployed and released in a CCE cluster of another tenant in IAM authorization mode. After selecting Other, select an authorized tenant. NOTE: You are advised to configure the AK/SK of a member account that has the CCE cluster operation permission. You are not advised to configure the AK/SK of a tenant account.
   IAM authorization	If you do not have the permission to call CCE APIs, enable this option to obtain the temporary AK/SK of an authorized user.
   Region	Select the region to be deployed.
   Cluster Name	Select the Kubernetes cluster applied for on CCE.
   Namespace	Select the namespace of the Kubernetes cluster on CCE.
   Workload	Select the target workload to be deployed.
   Service	Select the name of the Service bound to the target workload.
   Ingress	Select the name of the route bound to the target Service.
   Container	Select the name of the CCE container to be deployed.
   Image	Select the image for deployment.
   Image Tag	Select the tag of the image for deployment.
   Enable grayscale configuration	Grayscale release policy: Header Header-Key: You can enter the key of a custom header. Header-Value: You can enter a custom header value. The value can be a character string or a regular expression. The regular expression format is ^....$. Gray Traffic Weight (%): You can customize the traffic weight of each service version. Cookie Cookie: Enter custom cookie content. Gray Traffic Weight (%): You can customize the traffic weight of each service version. NOTE: The values of Header and Cookie can contain a maximum of 500 characters.