Difference between revisions of "UnAvailableLoadBalancer"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
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]] | ||
== See also == | == See also == |
Revision as of 16:51, 29 November 2022
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
Advertising: