Difference between revisions of "Healthz"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
* [[Readiness]] | * [[Readiness]] | ||
* [[Liveness]] | * [[Liveness]] | ||
| + | * <code>[[curl --fail]]</code> | ||
== See also == | == See also == | ||
| + | * {{k8s troubleshooting}} | ||
| − | [[Category: | + | [[Category:K8s]] |
Revision as of 08:43, 25 October 2022
🤦 Unable to restart cluster, will reset it: apiserver healthz: apiserver process never appeared
127.0.0.1 - - [27/Jul/2022:14:46:38 +0000] "GET /healthz HTTP/1.1" 200 2369 "-" "curl/7.74.0" "-"
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:
