Difference between revisions of "UnAvailableLoadBalancer"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | [[kubectl get events -A]] | grep UnAvailableLoadBalancer | |
[[ingress-nginx]] 28m Warning [[UnAvailableLoadBalancer]] service/nginx-ingress-controller There are no available nodes for LoadBalancer | [[ingress-nginx]] 28m Warning [[UnAvailableLoadBalancer]] service/nginx-ingress-controller There are no available nodes for LoadBalancer | ||
Revision as of 15:26, 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
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:
