Querying the Kubernetes Cluster Event List
Function
This API is used to query the Kubernetes cluster event list.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.
URI
GET /v5/{project_id}/container/kubernetes/cluster/events
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
enterprise_project_id |
No |
String |
Specifies the ID of the enterprise project that the server belongs to. An enterprise project can be configured only after the enterprise project function is enabled. Enterprise project ID. The value 0 indicates the default enterprise project. To query servers in all enterprise projects, set this parameter to all_granted_eps. If you have only the permission on an enterprise project, you need to transfer the enterprise project ID to query the server in the enterprise project. Otherwise, an error is reported due to insufficient permission. |
|
cluster_id |
Yes |
String |
Cluster ID |
|
cluster_name |
No |
String |
Cluster name |
|
namespace |
No |
String |
Namespace for which the event is generated. |
|
event_name |
No |
String |
Event name |
|
event_type |
No |
String |
Event type. The options are as follows: |
|
resource_type |
No |
String |
Indicates the type of the resource for which the event is generated. |
|
resource_name |
No |
String |
Name of the resource where the event occurred. |
|
reason |
No |
String |
Cause of the event |
|
start_time |
Yes |
Long |
Minimum time for querying logs |
|
end_time |
Yes |
Long |
Maximum time for querying logs |
|
limit |
Yes |
Integer |
Number of records displayed on each page. The default value is 10. |
|
offset |
Yes |
Integer |
Offset, which specifies the start position of the record to be returned. The value must be a number no less than 0. The default value is 0. |
|
line_num |
No |
String |
Page number that needs to be transferred when the CCE cluster event is queried. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
total_num |
Integer |
Total number of logs |
|
data_list |
Array of ClusterEventLogResponseInfo objects |
Kubernetes cluster event logs |
|
Parameter |
Type |
Description |
|---|---|---|
|
cluster_name |
String |
Cluster name |
|
cluster_id |
String |
Cluster ID |
|
cluster_type |
String |
Cluster type. Its value can be: |
|
time |
Long |
Time when a log is generated |
|
namespace |
String |
Namespace of the triggered event. |
|
event_name |
String |
Event name |
|
event_type |
String |
Event type. |
|
resource_type |
String |
Resource type |
|
resource_name |
String |
Resource name. |
|
reason |
String |
Cause of the event |
|
line_num |
String |
Row number of the CCE cluster event. |
Example Requests
None
Example Responses
Status code: 200
Request succeeded.
{
"total_num" : 1,
"data_list" : [ {
"cluster_name" : "ywk-55555",
"cluster_id" : "b075094b-d21a-499a-9006-624089c94402",
"cluster_type" : "cce",
"time" : 1814080859608,
"namespace" : "kube-flannel",
"event_name" : "kube-flannel-ds-5qrl6.182493b545b889d7",
"event_type" : "Normal",
"resource_type" : "imagetag",
"resource_name" : "kube-flannel-ds-5qrl6",
"reason" : "Pulling image \"ghcr.io/flannel-io/flannel-cni-plugin:v1.6.2-flannel1\"",
"line_num" : 12345
} ]
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Request succeeded. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot