npm install -g @hiero-ledger/solo@latest instead.
See System Readiness for full install instructions.SOLO-5078
ClusterUnreachableError
| Code | SOLO-5078 |
| Category | System |
| Ownership | Infrastructure |
| Retryable | Yes |
Description
Thrown when a Kubernetes API call against a remote cluster fails for any reason other than the resource being absent; the message names the kubeconfig context and the underlying failure, which is also wrapped in cause. solo reads and writes cluster state over the Kubernetes API for every deployment operation, so this means the call never produced a usable answer: the API server is down or unreachable over the network, the kubeconfig context points at a cluster that no longer exists, credentials have expired, or RBAC denied the request. Kind clusters are excluded — a local kind API failure is reported as a Kubernetes API invalid response instead. It is retryable because an API server that is restarting, or a transient network problem, often clears on a later attempt.
Troubleshooting Steps
- Verify the cluster is reachable: kubectl cluster-info –context
- Verify the kubeconfig context still exists: kubectl config get-contexts
- Verify your credentials and RBAC permissions for the namespace
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log