Kustomize unable to produce windows and darwin ARM binaries

[natasha41575]

Related issues:

• Kustomize stuck on outdated goreleaser version #4542
• Goreleaser erroneously skipping darwin/arm64 and windows/arm64 under Go 1.20 goreleaser/goreleaser#3835

TL;DR the outdated version of goreleaser we are stuck on (see the above issue) does not let us build windows and darwin ARM bindaires with go 1.20+.

The solution here will most likely be to revamp the release process - I think we should see what does the rest of kubernetes do for releasing (maybe prow?) and follow a similar model.

[natasha41575]

If anyone is interested in picking this up, I think first steps would be to look around other k8s projects or talk to other k8s leads about how they do their releases and see if we can use similar tools. Then, leave your research findings here and we can try to converge on a decision.

[koba1t]

other k8s projects

• kubebuilder: using golereaser and using actions/upload-artifact for binary upload.
• kops: go build with their Makefile
• cluster-api: go build in docker for their Makefile
• kwok: go build command on their script

[natasha41575]

I think go build is okay for releasing kustomize.

We will also need to think about how we release the other modules (kyaml, api, cmd/config) and the published docker image.

The image needs to get pushed to a specific gcr registry managed by the k8s test-infra group (you can find the link on the releasing instructions page). If the current release infrastructure is not using goreleaser to release the docker image, then we can probably leave that the way it is.

Releasing folder: https://github.com/kubernetes-sigs/kustomize/tree/master/releasing

[koba1t]

/assign @koba1t

[koba1t]

The image needs to get pushed to a specific gcr registry managed by the k8s test-infra group (you can find the link on the releasing instructions page). If the current release infrastructure is not using goreleaser to release the docker image, then we can probably leave that the way it is.

In the container image build step, goreleaser is not executed and the artifacts built by goreleaser are not used.

[koba1t]

We will also need to think about how we release the other modules (kyaml, api, cmd/config) and the published docker image.

I plan to use the simple shell scripts for building binaries and using GitHub CLI for creating GitHub Releases with every module(kyaml, api, cmd/config, and kustomize).

[natasha41575]

Thanks @koba1t! Feel free to get started. Please also update the releasing instructions doc with your PR.

[koba1t]

@natasha41575

I update the the releasing doc, and I make ready for review this PR.
If you can, Please check this PR!

[pre]

Can we already start holding our breath?

[natasha41575]

I just approved #5239 (the bot will merge it), so I think we can consider this issue fixed. We're going to try out the new release process with the next release and I have my fingers crossed that we'll be able to ship the windows and darwin arm binaries.

[pre]

@natasha41575 when could we expect a new kustomize release? The latest MacOS release is a four-month-old 5.0.3 from May.

[samrocketman]

Any ETA on next release? Ideally, you'd cut a release just to create the arm binaries if nothing else. I see maintainers closed my and others' issues on this as dupes saying it will be in the next release but still no release.

(as an aside it feels odd to close an issue as solved but have no resolution for end users; i.e. binaries released)

[pre]

The current latest release for ARM is now 5 months old. 🤷🏼

[aaronromeo]

I recently ran into this. Turns out it was a PEBCAK. My GITHUB_TOKEN value was incorrect. The unfortunately, the error isn't clear as the value of releases (https://github.com/kubernetes-sigs/kustomize/blob/f3fedac42997470040e1fd574ad2518fad47f61a/hack/install_kustomize.sh#L141C5-L141C13) isn't being checked for this particular error.