Cluster resync skipped on hard reset with empty k8scontextID
During a database reset, the Kubernetes context entry could be removed while resyncCluster still tried to use it, causing errors with the Layer5 provider. The hard-reset path now skips the resync and returns model.StatusProcessing.
Show release-note lines
- fix(resync): skip cluster resync when hardReset=true and k8scontextID is empty @Omkar-Ugal (#18038)github.com/meshery/meshery/releases/tag/v0.9.0