SOLO-2030

MirrorNodeClusterContextNotFoundSoloError

Description

Thrown when solo needs to act on a mirror node but cannot determine which cluster (kubeconfig context) it lives in; the message names the mirrorNodeId. solo maps each mirror node to a registered cluster reference to find the context for its operations, so this is raised when no such mapping resolves — typically because the mirror node is not associated with a registered cluster reference, or the referenced cluster is missing from the deployment configuration.

Troubleshooting Steps

1. List registered cluster references: solo cluster-ref config list
2. Verify the mirror node is associated with a registered cluster
3. Check deployment configuration: solo deployment config info