Difference between revisions of "Kubernetes readiness"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{k8s troubleshooting}} |
[[Category:K8s]] | [[Category:K8s]] | ||
Revision as of 16:43, 16 August 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
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:
