Changing the Subnet of a Cluster

Function

This API is used to bind a new subnet to newly added nodes after cluster creation, or in the case of a cluster subnet change.

By default, subnets with the same VPC are connected. Ensure that the new subnet can reach your service system. Note that a cluster with automatic IPv6 address creation enabled can only be switched to a new subnet that uses IPv6 addresses.

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/subnet/change

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.
cluster_id	Yes	String	ID of the cluster that you want to change the security group

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
-	Yes	Object

Response Parameters

None

Example Requests

Modify the subnet of a cluster.

POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/subnet/change

{
  "subnet_id" : "b1234567-1f77-4ae9-b64d-9af56e123456"
}

Example Responses

None

Status Codes

Status Code	Description
200	Request succeeded.
400	Invalid request. Modify the request and then retry.
403	Request rejected.The server has received the request and understood it, but refuses to respond to it. The client should not repeat the request without modifications.

Status Code

Description

200

Request succeeded.

400

Invalid request.

Modify the request and then retry.

403

Request rejected.The server has received the request and understood it, but refuses to respond to it. The client should not repeat the request without modifications.