Kubectl graph fails to resolve DNS names behind a VPN

[steveteuber]

When a VPN is being used then DNS lookups will fail:

$ GODEBUG=netdns=2 kubectl graph pods
go package net: built with netgo build tag; using Go's DNS resolver
go package net: hostLookupOrder(kubernetes.vpn.example.com) = files,dns
Unable to connect to the server: dial tcp: lookup kubernetes.vpn.example.com on X.X.X.X:53: no such host

For comparison, kubectl installed via homebrew is using the regular C resolution process:

$ GODEBUG=netdns=2 kubectl get pods
go package net: using cgo DNS resolver
go package net: hostLookupOrder(kubernetes.vpn.example.com) = cgo
NAME                             READY   STATUS    RESTARTS   AGE
example-application-77b7568d4b-csbnc   1/1     Running   0          6d5h
example-application-77b7568d4b-tl9v6   1/1     Running   0          6d5h
example-application-77b7568d4b-vsbtq   1/1     Running   0          6d5h

[steveteuber]

A solution already implemented in kubectl: kubernetes/release#469

[steveteuber]

In my opinion, the only valid solution is to build the binary for macOS with CGO_ENABLED=1.