This message was deleted.

Also from the harvester server itself (via command line) i’m able to route dns, etc to the kube url with no issue

harvester is running k8s under the hood, and will be using coredns for dns resolution for the k8s specific workloads like pods.. so that is what is is being passed to the cattle cluster agent

Thanks for the help here. The issue turned out to be with my consul setup. it was not forwarding one of our domains. Fixing the consul issue fixed the issue I was seeing in harvester.

👍