Hi everyone,
I’ve been working on an issue related to the Reset Database workflow in Meshery.
I’ve documented the problem, the flow, and my proposed fix here:
https://docs.google.com/document/d/1DMzhSEr_tFBuKC5fFQge72Hy-pp_yPTKwP1EOEd9FAk/edit?usp=sharing
In short, after a hard reset the system still triggers resync, but since the Kubernetes context is removed, it results in a “no context found” error.
I’ve proposed skipping resync in this case, and I’d really appreciate feedback on whether this approach makes sense.
Thanks!
Omkar Ugalmugle