Difference between revisions of "UnAvailableLoadBalancer"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
[[kubectl describe nodes]] | grep [[KubeletReady]] | [[kubectl describe nodes]] | grep [[KubeletReady]] | ||
| − | ingress-nginx 53m Normal [[UpdatedLoadBalancer]] service/[[nginx-ingress-controller]] Updated load balancer with new hosts | + | [[ingress-nginx]] 53m Normal [[UpdatedLoadBalancer]] service/[[nginx-ingress-controller]] Updated load balancer with new hosts |
[[NodeNotReady]] | [[NodeNotReady]] | ||
Revision as of 17:29, 16 August 2023
kubectl get events -A | grep UnAvailableLoadBalancer ingress-nginx 28m Warning UnAvailableLoadBalancer service/nginx-ingress-controller There are no available nodes for LoadBalancer
Related
kubectl describe nodes | grep KubeletReady
ingress-nginx 53m Normal UpdatedLoadBalancer service/nginx-ingress-controller Updated load balancer with new hosts
NodeNotReady
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- 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:
