Skip to content

Detach Kubernetes LoadBalancer IP

DELETE
/tenant_clusters/{tenant_cluster_id}/lb-ips/{reserved_ip_id}/
curl --request DELETE \
--url 'https://api.e2enetworks.com/myaccount/api/v1/gpu/tenant_clusters/{tenant_cluster_id}/lb-ips/{reserved_ip_id}/?project_id=<PROJECT_ID>&location=<LOCATION>&apikey=<API_KEY>' \
--header 'Authorization: Bearer <API_TOKEN>'

Detaches one IP from the cluster’s LoadBalancer IP pool. The IP stays reserved in the project and becomes available for other services.

An IP that a Service in the cluster still uses cannot be detached: delete that Service first. If TIR cannot check whether the IP is in use, the call is refused; try again in a few minutes.

tenant_cluster_id
required
integer

Kubernetes cluster ID, as returned by List Kubernetes Clusters.

reserved_ip_id
required
integer

Reserved IP ID, as returned by List Kubernetes LoadBalancer IPs.

project_id
required
integer

Project ID

active_iam
integer

Active IAM ID (To access contact person account) Find your Active IAM ID here

location
required
string
Allowed values: Delhi Chennai

Location

The IP is detached.

Media typeapplication/json
object
code
integer
data
object
id
integer
ip_address
string
errors
object
message
string

Example

{
"code": 200,
"data": {
"id": 358,
"ip_address": "203.0.113.10"
},
"errors": {},
"message": "203.0.113.10 detached and returned to your reserved IPs."
}