Modifying Cluster Specifications

project_id

Yes

String

Details:

Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI.

Constraints:

None

Options:

Project IDs of the account

Default value:

N/A

cluster_id

Yes

String

Details:

Cluster ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI.

Constraints:

None

Options:

Cluster IDs

Default value:

N/A

Content-Type

Yes

String

Details:

The request body type or format

Constraints:

The GET method is not verified.

Options:

• application/json

• application/json;charset=utf-8

• application/x-pem-file

• multipart/form-data (used when the FormData parameter is present)

Default value:

N/A

X-Auth-Token

Yes

String

Details:

Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token.

Constraints:

None

Options:

N/A

Default value:

N/A

flavorResize

Yes

String

Definition

The target flavor to be changed. You can only adjust the maximum number of worker nodes in a cluster. The number of control plane nodes is fixed and cannot be altered, and the cluster flavor cannot be downgraded. Suppose the original cluster flavor is cce.s2.medium. In that case, you can only upgrade it to cce.s2.large or higher, but you cannot downgrade it to cce.s2.small or cce.s1.medium.

Constraints

N/A

Range

• cce.s1.small: a small-scale CCE cluster with one control plane node and a maximum of 50 worker nodes

• cce.s1.medium: a medium-scale CCE cluster with one control plane node and a maximum of 200 worker nodes

• cce.s2.small: a small-scale CCE cluster with three control plane nodes and a maximum of 50 worker nodes

• cce.s2.medium: a medium-scale CCE cluster with three control plane nodes and a maximum of 200 worker nodes

• cce.s2.large: a large-scale CCE cluster with three control plane nodes and a maximum of 1,000 worker nodes

• cce.s2.xlarge: an ultra-large-scale CCE cluster with three control plane nodes and a maximum of 2,000 worker nodes

• cce.s3.small: a small-scale CCE cluster with five control plane nodes and a maximum of 50 worker nodes

• cce.s3.medium: a medium-scale CCE cluster with five control plane nodes and a maximum of 200 worker nodes

• cce.s3.large: a large-scale CCE cluster with five control plane nodes and a maximum of 1,000 worker nodes

• cce.s3.xlarge: an ultra-large-scale CCE cluster with five control plane nodes and a maximum of 2,000 worker nodes

Default Value

N/A

skippedTasks

No

Array of strings

Definition

Whether to skip some tasks during a cluster flavor change

Constraints

N/A

Range

• IngressChecker: The check of configuration consistency between the ingress and ELB is skipped during the cluster flavor change.

Default Value

An unavailable cluster includes IngressChecker by default.

extendParam

No

extendParam object

Definition

Extended field for changing cluster flavors

Constraints

N/A

decMasterFlavor

No

String

Definition

The flavors of the control plane nodes can be specified for a DeC CCE cluster.

Constraints

N/A

Range

N/A

Default Value

N/A

jobID

String

Definition

Job ID

Constraints

N/A

Range

N/A

Default Value

N/A

orderID

String

Definition

ID of the order for modifying the flavor of a yearly/monthly cluster

Constraints

N/A

Range

N/A

Default Value

N/A

201

The job for modifying the specifications of the pay-per-use cluster is delivered.