Difference between revisions of "Kubernetes readiness"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
== See also == | == See also == | ||
| + | * {{Kubernetes readiness}} | ||
* {{k8s troubleshooting}} | * {{k8s troubleshooting}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Revision as of 05:52, 18 July 2024
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" )
9m42s Warning Unhealthy pod/my-release-mariadb-0 Readiness probe failed: mysqladmin: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb-admin' instead...
kubectl describe deployment | grep Readiness
Related
kubectl describe deployment | grep LivenesshealthzReadiness probe errored- Liveness
curl --failreadinessProbe- Readiness probe failed: HTTP probe failed with statuscode: 500
See also
- Kubernetes readiness, Liveness
- 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:
