# LoadBalancer Service Stuck Pending | ZopNight

> No external address was ever assigned, so the service is unreachable from outside the cluster despite looking configured.

Source: https://zop.dev/zopnight/rules/loadbalancer-service-stuck-pending

---

_Reliability · Medium severity_

## LoadBalancer Service Stuck Pending

No external address was ever assigned, so the service is unreachable from outside the cluster despite looking configured.

- 3 — clouds covered
- Medium — severity
- Risk — where it shows up
- Manual — fix, change spelled out

Free to start. No card. The playground just needs your work email.

## Found, explained, handed over.

Exposure and fragility, security posture and single points of failure.

- 01. Detect — ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
- 02. Explain — Every finding says exactly what to change: Fix the LoadBalancer service stuck pending.
- 03. Fix — The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.

- applies_to_fallback: Any resource in the account
- where_it_appears: The Risk tab of Recommendations, with every affected resource listed.

## Related

- [Service Has externalIPs Set](https://zop.dev/zopnight/rules/service-has-externalips-set)
- [Service Type NodePort](https://zop.dev/zopnight/rules/service-type-nodeport)
- [Service Type LoadBalancer](https://zop.dev/zopnight/rules/service-type-loadbalancer)
- [Autoscaler at Max Capacity](https://zop.dev/zopnight/rules/autoscaler-at-max-capacity)
- [DaemonSet Not Fully Scheduled](https://zop.dev/zopnight/rules/daemonset-not-fully-scheduled)
- [Deployment Not Fully Ready](https://zop.dev/zopnight/rules/deployment-not-fully-ready)

## See the reliability findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

[object Object]