Difference between revisions of "Healthz"
Jump to navigation
Jump to search
| (7 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
== Related == | == Related == | ||
* [[Readiness]] | * [[Readiness]] | ||
| + | * [[Liveness]] | ||
| + | * <code>[[curl --fail]]</code> | ||
| + | * [[Kubernetes services]] | ||
| + | * <code>[[service.beta.kubernetes.io/aws-load-balancer-healthcheck-path]]: "/[[healthz]]"</code> | ||
| + | * <code>[[op-node]]</code> | ||
| + | |||
| + | == See also == | ||
| + | * {{k8s troubleshooting}} | ||
| + | |||
| + | [[Category:K8s]] | ||
Latest revision as of 11:57, 7 October 2024
🤦 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[edit]
- Readiness
- Liveness
curl --fail- Kubernetes services
service.beta.kubernetes.io/aws-load-balancer-healthcheck-path: "/healthz"op-node
See also[edit]
- 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:
