-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Darwin CLI should be built with CGO_ENABLE=1
and/or GODEBUG=netdns=cgo
#1079
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/lifecycle frozen |
This will make darwin to build with CGO_ENABLED to work fine with proxy and vpn Fix tektoncd#1079
This should be solved for "free" with go 1.20 fyi : |
We have done 0.33 release with go 1.20, closing this now |
Versions and Operating System
Kubernetes version: any
Tekton Pipeline version: any
Operating System: MacOS
Expected Behavior
When using a VPN on MacOS as many corporations do (especially in a remote environment),
tkn
is able to perform all functions against a Kubernetes cluster.Actual Behavior
When using a split-tunnel VPN with custom rules,
tkn
will fail to resolve the host.Additional Info
Because of how go's
netdns
resolver works, the go implementation doesn't necessarily work with Darwin's dns resolver chain. Instead, it would need to use thecgo
version as that uses the OS's resolvers which is how most VPNs configure their custom tunnel rules when there is a split tunnel. For reference, whenkubectl
distributes itself via homebrew, it compiles withCGO_ENABLE=1
: kubernetes/release#469I believe the fix here is to cross-compile with
cgo
enabled for the binary that is deployed to homebrew There are potential cross-compilation problems here so there is an alternative which is to force the issue and build the code usingGODEBUG=netdns=cgo
which will also force go to use the cgo dns resolver.The text was updated successfully, but these errors were encountered: