Jeff Lill
Jeff Lill
This is still a problem. I've used the divide-and-conquer technique and narrowed this down to **Neon.Kube.Setup**. The problem is that this project is referencing **Neon.Kube.Operator**. That assembly is only intended...
Actually **FIXED**
@marcusbooyah looked at this and it's a problem with cluster advice. He hacked around this for clusters with 10 nodes or less but we'll need to put some more effort...
info: https://stackoverflow.com/questions/72382966/rancher-node-nameserver-limits-were-exceeded-some-nameservers-have-been-omitte
Actually, I **cannot replicate this**. In my first attempt, I created a tiny hyper-v cluster using my cheats and then I tweaked the cluster definition and my cheat script and...
@marcusbooyah told me that the cluster login removed was for our headend cluster, which is not currently considered to be a NeonKUBE cluster (because it's pretty old). I tried deploying...
**NO-REPRO:** I wasn't able to reproduce this issue. I had the headend cluster in the config and then deployed a new Hyper-V cluster; the headend cluster was still there afterwards.
Looks like @marcusbooyah comitted this change
MSFT opened a new issue to track this: https://github.com/microsoft/WSL/issues/10006 This issue is **still open** and there doesn't seem to be a solution yet, other than folks claim that **enabling systemd...