Updated on 2024-10-17 GMT+08:00

Enabling Public Network Access

Function

This API is used to enable public network access.

Debugging

You can debug this API through automatic authentication in API Explorer.

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/public/open

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 whose public network access you want to enable.

Request Parameters

Table 2 Request body parameters

Parameter

Mandatory

Type

Description

eip

Yes

BindPublicReqEip object

EIP information.

isAutoPay

No

Integer

Indicates whether to enable automatic payment from your Huawei Cloud account. This parameter takes effect only for yearly/monthly clusters.

  • 1: Yes. (Discounts and coupons are automatically selected. The fee will be automatically deducted from your Huawei Cloud account.) If the automatic payment fails, an unpaid order will be generated, and you need to manually complete the payment. (During manual payment, you can still modify the discounts and coupons that were automatically selected.)

  • 0: No. (Customers need to manually pay for the bill. Discounts and coupons can be used.) The default value is 0.

Table 3 BindPublicReqEip

Parameter

Mandatory

Type

Description

bandWidth

Yes

BindPublicReqEipBandWidth object

Public network bandwidth.

Table 4 BindPublicReqEipBandWidth

Parameter

Mandatory

Type

Description

size

Yes

Integer

Bandwidth range. Unit: Mbit/s

Response Parameters

Status code: 200

Table 5 Response body parameters

Parameter

Type

Description

action

String

Operations. The fixed value is bindZone, indicating that the binding is successful.

Example Requests

{
  "eip" : {
    "bandWidth" : {
      "size" : 5
    }
  }
}

Example Responses

Status code: 200

Request succeeded.

{
  "action" : "bindZone"
}

Status Codes

Status Code

Description

200

Request succeeded.

400

Invalid request.

Modify the request before retry.

409

The request could not be completed due to a conflict with the current state of the resource.

The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.

412

The server did not meet one of the preconditions contained in the request.

Error Codes

See Error Codes.