On this page

Prerequisites
Procedure

Show all

Help Center/ CodeArts Deploy/ User Guide/ Creating and Deploying an Application with a Blank Template/ Configuring Deployment Actions for an CodeArts Deploy Application/ Configuring Deployment Actions for Containers/ Kubernetes Nginx-Ingress Grayscale Deployment (CCE Cluster)

Kubernetes Nginx-Ingress Grayscale Deployment (CCE Cluster)

Updated on 2025-02-08 GMT+08:00

View PDF

Grayscale deployment of CCE Kubernetes clusters based on the ingress-nginx component

Prerequisites

A CCE cluster is available.
The Nginx Ingress plug-in is installed in the CCE cluster.

Procedure

**Table 1** Parameters
Parameter	Description
Action Name	Name of an added deployment action. 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 the CCE cluster of the current tenant for release. Select Current. The current tenant must have the CCE cluster operation permission. If the current tenant does not have the CCE cluster operation permission, select IAM authorization for deployment. Other: The software package is deployed and published in the CCE cluster of another tenant in IAM authorization mode. If you select Other, you must select an authorized tenant to deploy the CCE cluster. NOTE: You are advised to configure the AK/SK of a member account that has the CCE cluster operation permission and not advised to configure the AK/SK of a tenant account.
IAM authorization	If you do not have the permission to execute an API, this parameter enables you to obtain the temporary AK/SK of the parent user to execute the CCE API through IAM.
Region	Select the region to be deployed.
Cluster Name	Select the Kubernetes cluster applied on CCE.
Namespace	Select the namespace of the Kubernetes cluster on CCE.
Workload	Select the target Deployment.
Service	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 to be deployed.
Image Tag	Select the tag of the image to be deployed.
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 ^....$. Grayscale traffic weight (%): Traffic can be customized. Cookie Cookie: Custom cookie content can be entered. Grayscale traffic weight (%): Traffic can be customized. NOTE: The values of Header and Cookie can contain a maximum of 500 characters.

Parent topic: Configuring Deployment Actions for Containers

Previous topic: Deploying an Application with a Custom Kubernetes Cluster

Next topic: Deploying with Helm3

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback

Log In and Submit Submit Cancel