Difference between revisions of "Kubectl get events"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
8m51s Warning [[FailedScheduling]] pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "[[VolumeBinding]]": binding volumes: [[timed out waiting for the condition]] | 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 | ||
Revision as of 06:08, 26 September 2022
kubectl -n gitlab-runner get events --field-selector type!=Normal
kubectl get events --sort-by=.metadata.creationTimestamp kubectl get events --sort-by=.metadata.creationTimestamp -A
Contents
Events examples
Warning
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
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
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
BackOff Completed Created FailedMount FailedScheduling Generated PresentError Pulled Pulling Requested SawCompletedJob Scheduled Started SuccessfulCreate SuccessfulDelete
FailedKillPod
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: