SOLO-3063
TlsKeySecretCreationFailedSoloError — Component
TlsKeySecretCreationFailedSoloError
| Code | SOLO-3063 |
| Category | Component |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo cannot store a generated TLS key as a Kubernetes secret; when available the underlying failure is wrapped in cause. solo persists TLS keys in cluster secrets so components can mount them, so this means the secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- Check existing secrets: kubectl get secrets -n
- Verify RBAC permissions allow secret creation in the namespace
- Re-run node setup: solo consensus node setup