SOLO-1008

RemoteConfigMissingOnKindClusterError

Description

Thrown when the solo-remote-config ConfigMap that backs a deployment cannot be found and the deployment targets a local kind cluster. solo keeps the authoritative deployment state in that ConfigMap, so its absence means the deployment recorded in the local config no longer has anything backing it in the cluster; the usual causes are a kind cluster that was deleted and recreated, a namespace that was removed with kubectl, or a ConfigMap that was deleted by hand. A local kind cluster holds nothing worth preserving, so the recorded deployment cannot be resumed and the fix is to tear the leftover state down with solo one-shot single destroy and deploy again from a clean slate. solo one-shot single deploy detects this state up front and offers that teardown itself; every other command reports this error and stops. Deployments on non-kind clusters fail with the generic resource-not-found error instead, since their state may still be recoverable.

Troubleshooting Steps

1. Confirm the kind cluster and namespace still exist: kind get clusters && kubectl get namespaces
2. Inspect the remote config ConfigMap: kubectl get configmap solo-remote-config -n
3. Tear the leftover state down before deploying again: solo one-shot single destroy –deployment