Code change:
# These are "local" but are visible to and relied on by functions this # function calls.  They are effectively part of the calling API to # build_binaries_for_platform. <del> local goflags goldflags goasmflags gogcflags gotags </del> <ins> local goflags goldflags gogcflags gotags </ins> <del> # This is $(pwd) because we use run-in-gopath to build.  Once that is # excised, this can become ${KUBE_ROOT}. local trimroot # two lines to appease shellcheck SC2155 trimroot=$(pwd) goasmflags="all=-trimpath=${trimroot}" </del> <ins> goflags=() gogcflags="${GOGCFLAGS:-}" goldflags="all=$(kube::version::ldflags) ${GOLDFLAGS:-}" </ins> <del> gogcflags="all=-trimpath=${trimroot} ${GOGCFLAGS:-}" </del> if [[ "${DBG:-}" == 1 ]]; then # Debugging - disable optimizations and inlining and trimPath <del> gogcflags="${GOGCFLAGS:-} all=-N -l" goasmflags="" fi goldflags="all=$(kube::version::ldflags) ${GOLDFLAGS:-}" if [[ "${DBG:-}" != 1 ]]; then # Not debugging - disable symbols and DWARF. </del> <ins> gogcflags="${gogcflags} all=-N -l" else # Not debugging - disable symbols and DWARF, trim embedded paths </ins> goldflags="${goldflags} -s -w" <ins> goflags+=("-trimpath") </ins> fi # Extract tags if any specified in GOFLAGS

Related discussion:
text: So i built golang from source, peppered it with changes to track down where this is getting created and found that it is coming from: I don't know yet how to fix it. will dig more when i can (travelling for the next few days)
Would it work to override the , I see that they use the : Ref: https://reproducible- Edit: Probably not, we may make it configurable in golang :thinking:
this is so tricky :( will dig more when i get back from my event this week
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue with Mark this issue as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close not-planned [1]:
Closing this issue, marking it as "Not Planned".