deleteLoadBalancerInstances
- Print
- PDF
deleteLoadBalancerInstances
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Deletes load balancer instances.
Request
Request header
| Header | Description |
|---|---|
| x-ncp-apigw-timestamp | It is the number of milliseconds that have elapsed since January 1, 1970 00:00:00 UTC. If the time difference with the API Gateway server is more than 5 minutes, the request is considered invalid. |
| x-ncp-apigw-api-key | API key issued by API Gateway (not used in the API v2.) |
| x-ncp-iam-access-key | API key issued by NAVER Cloud Platform or access key issued by IAM |
| x-ncp-apigw-signature-v2 | Signature used to encrypt the body with the “secret key” that maps with the “access key.” The HMAC encryption algorithm is HMAC SHA256. |
Request parameters
| Parameter | Required | Type | Limitations | Description |
|---|---|---|---|---|
| loadBalancerInstanceNoList.N | Y | String | Duplicates not allowed. | List of load balancer instance numbers to delete. Get available values by using the getLoadBalancerInstanceList action. Example)loadBalancerInstanceNoList.1=123&loadBalancerInstanceNoList.2=345 |
Response
Response body
Examples
Request example
GET {LOADBALANCER_API_URL}/loadbalancer/v2/deleteLoadBalancerInstances?loadBalancerInstanceNoList.1=1083108
Response example
<deleteLoadBalancerInstancesResponse>
<requestId>a66e857f-47d8-41b5-a322-bf16d9daa874</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<loadBalancerInstanceList>
<loadBalancerInstance>
<loadBalancerInstanceNo>1083108</loadBalancerInstanceNo>
<virtualIp>49.236.150.32,49.236.151.188</virtualIp>
<loadBalancerName>penguin</loadBalancerName>
<loadBalancerAlgorithmType>
<code>RR</code>
<codeName>Round Robin</codeName>
</loadBalancerAlgorithmType>
<loadBalancerDescription></loadBalancerDescription>
<createDate>2018-11-26T11:04:31+0900</createDate>
<domainName>slb-1083108.ncloudslb.com</domainName>
<loadBalancerInstanceStatusName>terminating</loadBalancerInstanceStatusName>
<loadBalancerInstanceStatus>
<code>USED</code>
<codeName>NET USED state</codeName>
</loadBalancerInstanceStatus>
<loadBalancerInstanceOperation>
<code>TERMT</code>
<codeName>NET TERMINATED OP</codeName>
</loadBalancerInstanceOperation>
<networkUsageType>
<code>PBLIP</code>
<codeName>Public</codeName>
</networkUsageType>
<isHttpKeepAlive>false</isHttpKeepAlive>
<connectionTimeout>60</connectionTimeout>
<certificateName></certificateName>
<loadBalancerRuleList>
<loadBalancerRule>
<protocolType>
<code>HTTP</code>
<codeName>http</codeName>
</protocolType>
<loadBalancerPort>80</loadBalancerPort>
<serverPort>80</serverPort>
<l7HealthCheckPath>/</l7HealthCheckPath>
<certificateName></certificateName>
<proxyProtocolUseYn>N</proxyProtocolUseYn>
<stickySessionUseYn>N</stickySessionUseYn>
<http2UseYn>N</http2UseYn>
</loadBalancerRule>
</loadBalancerRuleList>
<loadBalancedServerInstanceList/>
</loadBalancerInstance>
</loadBalancerInstanceList>
</deleteLoadBalancerInstancesResponse>
Error codes
Errors that may occur while using this action are listed below. For information on common errors, refer to NAVER Cloud Platform.
| HTTP response code | Return code | Return message |
|---|---|---|
| 400 | 10713 | Not found contract information. Please check your input parameter. |
| 400 | 24109 | The input parameter instance number is invalid |
| 400 | 24123 | The input parameter load balancer instance number is invalid. |
| 400 | 25026 | You may not delete since (other) user is operating the target load balance. |
| 400 | 25050 | (Other)Unable to operate load balancer since use is manipulating the applying server. |
Was this article helpful?