Difference between revisions of "Operation timeout: context deadline exceeded"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
* <code>[[FailedKillPod]]</code> | * <code>[[FailedKillPod]]</code> | ||
* <code>[[kubectl get events -A]] | grep [[Warning]]</code> | * <code>[[kubectl get events -A]] | grep [[Warning]]</code> | ||
| − | + | * <code>[[timed out waiting for the condition]]</code> | |
| − | + | * <code>[[FailedCreatePodSandBox]]</code> | |
== See also == | == See also == | ||
Revision as of 14:29, 22 November 2022
error killing pod: failed to "KillContainer" for "you-container" with KillContainerError: "rpc error: code = Unknown desc = operation timeout: context deadline exceeded"
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod "gitlab-runner-gitlab-runner-6577898d44-r88q6": operation timeout: context deadline exceeded
kube-system 42m Warning Unhealthy pod/tiller-deploy-68bb9fb75-kw5r5 Liveness probe failed: Get "http://10.32.0.15:44135/liveness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Related
kubectl top nodeFailedKillPodkubectl get events -A | grep Warningtimed out waiting for the conditionFailedCreatePodSandBox
See also
- 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 kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed
Advertising:
