Using Kubenet networking, moved Route Table to new resource group, seeing issues

[nnellanspdl]

I'm still using Kubenet networking (for now ... yes, I know its being deprecated).

I made the bone-headed decision to move the Route Table to a different Resource Group. Now, my cluster is exhibiting some strange behavior. I moved the Route Table back to its original location in hopes that the cluster would resolve itself, but that did not happen, unfortunately.

My nodes now have a taint saying network-unavailable and doing a kubectl describe node will show the following: NoRouteCreated - RouteController failed to create a route

Is there anything I can do to get out of this mess? Microsoft support is telling me to just rebuild the cluster, but that's not a good option for me right now.

[nnellanspdl]

Fixed by:

• Moving route table to its original location
• Re-adding RBAC contributor role on the Route Table for the cluster's managed identity (this disappeared through all of the moves, for some reason)