SOLO-9010

RemoteConfigContextUnavailableError

Description

Thrown when remote-configuration access needs a Kubernetes context to reach the cluster but none is available: no context was passed to the call and solo could not fall back to a default one (for example because the current kubeconfig has no current-context to resolve). Because callers are expected to supply or have already resolved a context by this point, reaching it indicates a broken internal assumption in solo rather than a user error.

Troubleshooting Steps

1. This is an internal Solo error. File a bug report: https://github.com/hiero-ledger/solo/issues