Enabling Kibana Public Access¶

Function¶

This API is used to enable Kibana public network access.

You can debug this API in . Automatic authentication is supported.

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

**Table 1** Path parameters¶
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details, see Obtaining a Project ID and Name.
cluster_id	Yes	String	ID of the cluster that you want to enable Kibana public access

**Table 2** Request body parameter¶
Parameter	Mandatory	Type	Description
eipSize	Yes	Integer	Bandwidth. Unit: Mbit/s
elbWhiteList	Yes	StartKibanaPublicReqElbWhitelist object	ELB whitelist

**Table 3** StartKibanaPublicReqElbWhitelist¶
Parameter	Mandatory	Type	Description
enableWhiteList	Yes	Boolean	Indicates whether to enable the whitelist. true: The whitelist is enabled. false: The whitelist is disabled.
whiteList	Yes	String	Whitelist

None

{
  "eipSize" : 5,
  "elbWhiteList" : {
    "enableWhiteList" : true,
    "whiteList" : "192.168.0.xx"
  },
  "isAutoPay" : 1
}

{
  "eipSize" : 5,
  "elbWhiteList" : {
    "enableWhiteList" : true,
    "whiteList" : "192.168.0.xx"
  }
}

None

Status Code	Description
200	The request is processed successfully.
400	Invalid request. Modify the request instead of retrying.
409	The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.
412	The server does not meet one of the requirements that the requester puts on the request.

last updated: 2024-11-13 14:01 UTC - commit: 57e9916704b2f9567fccd20431958ae350c64958