Difference between revisions of "Kubernetes readiness"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
* <code>[[Readiness probe errored]]</code> | * <code>[[Readiness probe errored]]</code> | ||
* [[Liveness]] | * [[Liveness]] | ||
| + | * <code>[[curl --fail]]</code> | ||
== See also == | == See also == | ||
Revision as of 08:44, 25 October 2022
kubectl describe pods Warning Unhealthy 6m34s (x2 over 6m36s) kubelet Readiness probe failed: Get "http://192.168.66.98:3000/api/health": dial tcp 192.168.66.98:3000: connect: connection refused
Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
kubectl describe deployment | grep Readiness
Related
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
Advertising:
