[9.2] (backport #9751) Add Windows/arm64 support for Agent #10388
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Save current work * add a platformpackage for windows/arm64 * Trying new image in observability-ci namespace * Updating packages spec * Package windows/arm64 * Update windows step keys * Change host image for windows/arm64 packaging * Update test and switch image settings for windows/arm * machineType -> instanceType * trigger a new build after container update * trigger a new build after container update * add go build -x * trigger a new build after container update * Bump version of winperfcounters to support arm * less noise please * set cgo_enabled for windows * trigger a new build after container update * trigger a new build after container update * trigger a new build after container update * trigger a new build after container update * Add arm64 to allowed archs for Zip * go mod tidy * Build elastic-agent-archive-root for windows/arm64 * Cleaning up comments and debug logs * Cleaning up * Cleaning up and setting agentbeat to all platforms * Agentbeat not yet in DRA for windows/arm64 * Beats DRA now published, so try agentbeat w/ all platforms * Cleaning up and linting * Temp trying new .package-version w/ windows/arm beats * Cleaning up code * Cleaning up log messages * Restoring previous comment * Adding in support for windows/arm in spec file for Endpoint * fixing spacing (cherry picked from commit 53d140d)
mergify
bot
requested review from
blakerouse and
kaanyalti
and removed request for
a team
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Contributor
💚 Build Succeeded
cc @dwhyrock |
cmacknz
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The goal of this PR is to get Elastic Agent building and packaging a Windows ARM artifact.
Both Beats and Endpoint are currently producing Windows/arm64 artifacts that can be packaged.
This is producing a valid Elastic Agent build that has Agentbeat, OsQuerybeat, and Endpoint components packaged with it: https://buildkite.com/elastic/elastic-agent/builds/27828#01999b48-3d7d-424d-b2b1-aa1c97d29b09
NOTE: There is currently no CI support for Windows/arm64, so testing in CI has not been added. Also, this support for Windows/arm64 is not fully supported for customer use, so there will be no changelog added since it won't be published on the download pages until it's fully vetted/tested/etc.
This PR does the following:
.buildkite/bk.integration.pipeline.ymlto reflect windows architecturepackaging-windows-arm64step to.buildkite/integration.pipeline.ymlwindows/arm64as aPLATFORMSlist item forbuild-dra-snapshot-armstep in.buildkite/pipeline.elastic-agent-binary-dra.ymlwindows/arm64as aPLATFORMSlist item topackage-elastic-agent-armstep in.buildkite/pipeline.elastic-agent-package.ymlwindows/arm64case for crossbuilding indev-tool/mage/crossbuild.gowindows/arm64entries to various structs indev-tools/mageanddev-tools/packagingwindows-arm64as validplatformsitem indev-tools/packaging/packages.ymlfleet-serverto support all the valid platforms, except the newwindows/arm64onepkg/to supportwindows/arm64and not error out when encountering itspecs/endpoint-security.spec.ymlto not error out ifwindows/arm64is the OS/archmagefile.goto supportwindows/arm64in building and packaging logicWhy is it important?
Getting lots of demand for the ability to run on Windows OS w/ arm64 architecture.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Relates Support Windows ARM64 #692
Relates https://github.com/elastic/endpoint-dev/issues/17084
Relates https://github.com/elastic/endpoint-dev/issues/16812
Questions to ask yourself
This is an automatic backport of pull request #9751 done by [Mergify](https://mergify.com).