SOLO-2016
ClusterSetupFailedSoloError — Deployment
ClusterSetupFailedSoloError
| Code | SOLO-2016 |
| Category | Deployment |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo cluster-ref config setup cannot install the cluster-level shared infrastructure that deployments depend on — the solo-cluster-setup chart and its components (Prometheus, MinIO, metrics-server, and the cluster role). It wraps the underlying failure (cause.message), which is most often a failed Helm release (bad chart version or values), an image that cannot be pulled, missing RBAC permissions on the target cluster, or a cluster that lacks the CPU/memory to schedule the new pods.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- List installed Helm releases: helm list -A
- Inspect cluster pods: kubectl get pods -A
- Re-run cluster setup: solo cluster-ref config setup