Querying Cluster Tags
Function
This API is used to query tag information of a cluster.
Calling Method
For details, see Calling APIs.
URI
GET /v1.0/{project_id}/clusters/{cluster_id}/tags
| 
         Parameter  | 
       
         Mandatory  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|---|
| 
         project_id  | 
       
         Yes  | 
       
         String  | 
       
         Definition Project ID. To obtain the value, see Obtaining a Project ID. Constraints N/A Range N/A Default Value N/A  | 
      
| 
         cluster_id  | 
       
         Yes  | 
       
         String  | 
       
         Definition Cluster ID. For details about how to obtain the value, see Obtaining the Cluster ID. Constraints N/A Range N/A Default Value N/A  | 
      
Request Parameters
None
Response Parameters
Status code: 200
| 
         Parameter  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|
| 
         tags  | 
       
         Array of ResourceTag objects  | 
       
         Definition Tag list. Range N/A  | 
      
Example Requests
GET https://{Endpoint}/v1.0/89cd04f168b84af6be287f71730fdb4b/clusters/4ca46bf1-5c61-48ff-b4f3-0ad4e5e3ba90/tags
  Example Responses
Status code: 200
Tag information of the cluster queried.
{
  "tags" : [ {
    "key" : "key",
    "value" : "value"
  } ]
}
  Status Codes
| 
         Status Code  | 
       
         Description  | 
      
|---|---|
| 
         200  | 
       
         Tag information of the cluster queried.  | 
      
| 
         400  | 
       
         Request error.  | 
      
| 
         401  | 
       
         Authentication failed.  | 
      
| 
         403  | 
       
         You do not have required permissions.  | 
      
| 
         404  | 
       
         No resources found.  | 
      
| 
         500  | 
       
         Internal server error.  | 
      
| 
         503  | 
       
         Service unavailable.  | 
      
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.