All Products
Search
Document Center

Container Service for Kubernetes:CreateClusterDiagnosis

Last Updated:Dec 13, 2024

Starts a cluster diagnostic.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
cs:CreateClusterDiagnosiscreate
*Cluster
acs:cs:{#regionId}:{#accountId}:cluster/{#ClusterId}
    none
none

Request syntax

POST /clusters/{cluster_id}/diagnosis HTTP/1.1

Request parameters

ParameterTypeRequiredDescriptionExample
cluster_idstringNo

The cluster ID.

ce0da5a1d627e4e9e9f96cae8ad07****
bodyobjectNo

The request body.

typestringNo

The type of the diagnostic.

Valid values:

  • node
  • ingress
  • cluster
  • memory
  • pod
  • service
  • network
node
targetobjectNo

The parameter used to specify the diagnostic object. Examples of parameters for different types of diagnostic objects:

node:

{"name": "cn-shanghai.10.10.10.107"}

pod

{"namespace": "kube-system", "name": "csi-plugin-2cg9f"}

network

{"src": "10.10.10.108", "dst": "10.11.247.16", "dport": "80"}

ingress

{"url": "https://example.com"}

memory

{"node":"cn-hangzhou.172.16.9.240"}

service

{"namespace": "kube-system", "name": "nginx-ingress-lb"}
{"namespace": "kube-system", "name": "csi-plugin-2cg9f"}

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

cluster_idstring

The cluster ID.

c5cdf7e3938bc4f8eb0e44b21a80f****
diagnosis_idstring

The diagnostic ID.

6f719f23098240818eb26fe3a37d****
request_idstring

The request ID.

687C5BAA-D103-4993-884B-C35E4314****

Examples

Sample success responses

JSONformat

{
  "cluster_id": "c5cdf7e3938bc4f8eb0e44b21a80f****",
  "diagnosis_id": "6f719f23098240818eb26fe3a37d****",
  "request_id": "687C5BAA-D103-4993-884B-C35E4314****"
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history