Difference between revisions of "Kubectl get events"
Jump to navigation
Jump to search
(→Events) |
(→Events) |
||
Line 59: | Line 59: | ||
* <code>[[SuccessfulCreate]]</code> | * <code>[[SuccessfulCreate]]</code> | ||
* <code>[[SuccessfulDelete]]</code> | * <code>[[SuccessfulDelete]]</code> | ||
− | |||
* <code>[[FailedKillPod]]</code> | * <code>[[FailedKillPod]]</code> | ||
− | |||
* <code>[[NoPods]]</code> | * <code>[[NoPods]]</code> | ||
− | |||
− | |||
* <code>[[NodeHasNoDiskPressure]]</code> | * <code>[[NodeHasNoDiskPressure]]</code> | ||
Revision as of 07:51, 1 November 2022
kubectl get events
kubectl get events -A
kubectl get events -o yaml
kubectl get events --sort-by=.metadata.creationTimestamp
kubectl get events --sort-by=.metadata.creationTimestamp -A
kubectl get events --sort-by='.lastTimestamp
kubectl get events -A | grep Warning kubectl get events -A | grep Normal
Events examples
Warning
your_namespace 28s Warning FailedScheduling pod/kibana-kibana-654ccb45bd-pbp4r 0/2 nodes are available: 2 Insufficient cpu.
your_namespace 4m53s Warning ProbeWarning pod/metabase-prod-f8f4b765b-h4pgs Readiness probe warning:
your_namespace 30m Warning BackoffLimitExceeded job/your-job27740460 Job has reached the specified backoff limit
your_namespace 26m Warning Unhealthy pod/elasticsearch-master-1 Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )...
your_namespace 99s Warning BackOff pod/elasticsearch-master-0 Back-off restarting failed container your_namespace 108s Warning BackOff pod/elasticsearch-master-1 Back-off restarting failed container
your_namespace 12m Warning PresentError challenge/prod-admin-tls-cert-dzmbt-2545 Error presenting challenge: error getting clouddns service account: secret "clouddns-dns01-solver-svc-acct" not found
your_namespace 27m Warning OOMKilling node/gke-you-pool4 Memory cgroup out of memory: Killed process 2768158 (python) total-vm:5613088kB, anon-rss:3051580kB, file-rss:65400kB, shmem-rss:0kB, UID:0 pgtables:7028kB oom_score_adj:997
your_namespace 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition default 4m58s Normal ExternalProvisioning persistentvolumeclaim/myprometheus-alertmanager waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator Solution: Install aws-ebs-csi-driver
default 107s Warning ProvisioningFailed persistentvolumeclaim/myprometheus-server (combined from similar events): failed to provision volume with StorageClass "gp2": rpc error: code = Internal desc = Could not create volume "pvc-4e14416c-c9c2-4d39-b749-9ce0fa98d597": could not create volume in EC2: UnauthorizedOperation: You are not authorized to perform this operation. Encoded authorization failure message: Goz6E3qExxxxx.../...
Normal
default 4s Normal Provisioning persistentvolumeclaim/myprometheus-alertmanager External provisioner is provisioning volume for claim "default/myprometheus-alertmanager"
Related: kubectl get pvc
Events
BackOff
Completed
Created
FailedMount
FailedScheduling
Generated
PresentError
Pulled
Pulling
Requested
SawCompletedJob
Scheduled
Started
SuccessfulCreate
SuccessfulDelete
FailedKillPod
NoPods
NodeHasNoDiskPressure
Related
kubectl top
kubectl logs
FailedScheduling
kubectl get events --help
- job-controller
- kubelet
- GCP Node logs
- Events
gcloud logging read projects/yourproject/logs/kubelet
See also
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ]
,kubectl events, kubectl get events
:BackOff
,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity
,FailedScheduling, kubectl describe events, Unhealthy
,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded
- Kubectl information commands:
cluster-info
|view
|pods
|nodes
|services
|version
|describe | logs
- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod
, Liveness, Readiness,Kubernetes events
, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling
,errImagePull, ImagePullBackOff
, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising: