Skip to content

Add windows/arm64 to release binaries - #4218

Open
sAchin-680 wants to merge 1 commit into
kubernetes-sigs:mainfrom
sAchin-680:add-windows-arm64-release-binary
Open

Add windows/arm64 to release binaries#4218
sAchin-680 wants to merge 1 commit into
kubernetes-sigs:mainfrom
sAchin-680:add-windows-arm64-release-binary

Conversation

@sAchin-680

@sAchin-680 sAchin-680 commented Jul 20, 2026

Copy link
Copy Markdown

go install sigs.k8s.io/kind@latest already works on Windows ARM64 (confirmed in #3999), so this adds kind-windows-arm64 to the cross-compiled release binaries alongside the existing amd64 build, and updates the install docs (README, quick-start guide, RELEASE.md) accordingly.

Fixes #3999

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jul 20, 2026
@kubernetes-prow

kubernetes-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sAchin-680
Once this PR has been reviewed and has the lgtm label, please assign stmcginnis for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow
kubernetes-prow Bot requested review from aojea and stmcginnis July 20, 2026 11:15
@kubernetes-prow

kubernetes-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Welcome @sAchin-680!

It looks like this is your first PR to kubernetes-sigs/kind 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kind has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow kubernetes-prow Bot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 20, 2026
@kubernetes-prow

kubernetes-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Hi @sAchin-680. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 20, 2026
@stmcginnis

stmcginnis commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Thanks @sAchin-680. In case you didn't notice it in the set of bot posts, you need to update the commit text to remove the "Fixes" line from there. The Kubernetes policy is to not include those in the commit itself because it can cause issues with cherry-picks, so only the PR description should include the special tag for issue linkage.

You will need to amend the existing commit and force push the update to your branch. That will automatically refresh the PR and we can then proceed with reviews.

@sAchin-680
Add windows/arm64 to release binaries
95f0666 
Windows on ARM64 works with kind via `go install` already; this adds
kind-windows-arm64 to the cross-compiled release binaries and updates
install docs accordingly.

Signed-off-by: sAchin-680 <mrmister680@gmail.com>
@sAchin-680
sAchin-680 force-pushed the add-windows-arm64-release-binary branch from 07121b0 to 95f0666 Compare July 20, 2026 13:44
@kubernetes-prow kubernetes-prow Bot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jul 20, 2026
@sAchin-680

sAchin-680 commented Jul 20, 2026

Copy link
Copy Markdown
Author

Thanks @stmcginnis !! I'll remove the Fixes line from the commit message, amend the commit, and force push the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aojea aojea Awaiting requested review from aojea
@stmcginnis stmcginnis Awaiting requested review from stmcginnis

Assignees

No one assigned

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Kind for Windows ARM64

2 participants

@sAchin-680 @stmcginnis