Skip to content

Commit d869eb3

Browse files
committed
Add Werk #19275: Linux agent controller now available for ARM64 (aarch64)
CMK-28905 Change-Id: I4a0461d382abf6487b6e8e0e4d1a5070383e0146
1 parent 232c635 commit d869eb3

File tree

1 file changed

+48
-0
lines changed

1 file changed

+48
-0
lines changed

.werks/19275.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
[//]: # (werk v3)
2+
# Linux agent controller now available for ARM64 (aarch64)
3+
4+
key | value
5+
---------- | ---
6+
date | 2026-02-11T15:33:53+00:00
7+
version | 2.6.0b1
8+
class | feature
9+
edition | community
10+
component | checks
11+
level | 2
12+
compatible | no
13+
14+
The Checkmk agent controller is now available for Linux ARM64 (aarch64) systems.
15+
16+
Broader ARM support is one of the most popular requests in our community, this is the first step towards it. With this change, the full Checkmk agent feature set is now available on ARM64 Linux systems.
17+
18+
## What's in
19+
20+
### The ARM64 agent controller binary
21+
22+
The (gzipped) ARM64 agent controller is included in all Checkmk installations and can be found under `~/share/check_mk/agents/linux/cmk-agent-ctl-aarch64.gz` in your Checkmk site.
23+
24+
To install the Checkmk agent on ARM64 Linux, the recommended approach is to repackage the Checkmk agent `.rpm` or `.deb` package under `~/share/check_mk/agents/` and to place `cmk-agent-ctl-aarch64.gz` next to the already existing `cmk-agent-ctl.gz`.
25+
On agent installation, the setup scripts automatically detect the architecture and deploy the matching agent controller binary.
26+
27+
It's currently not included in the shipped packages to keep them lightweight.
28+
29+
### Agent bakery integration
30+
31+
If you use the Agent Bakery, there's a new option _Architecture of the systems where the agent will be deployed_ in the _Customize agent package (Linux)_ ruleset to control which agent controller architectures are included in baked packages:
32+
33+
* x86 64-bit only (default selected option)
34+
* ARM 64-bit only
35+
* x86 64-bit or ARM 64-bit
36+
37+
If both target architectures are selected, the installer will handle the deployment of the correct binary, as mentioned above.
38+
39+
## Scope of ARM support
40+
41+
Please note that there is a slight difference between _Building a package that's meant to run on ARM64_ and _Building an ARM64 package_.
42+
While the core agent features are now fully supported on ARM (Transport level encryption, Push agent, Compression, etc.), agent plugins are diverse, and we cannot guarantee that every packaged plugin is compatible with Linux ARM 64-bit.
43+
To help you build a clean ARM 64-bit packages, we have included the following checks in the Agent Bakery:
44+
45+
* If you choose only ARM 64-bit as the target architecture and you package an agent plugin that is unavailable for ARM, the Bakery will refuse to bake the package to prevent technical inconsistencies
46+
* If you choose both x86 64-bit and ARM 64-bit as target architectures and you package an agent plugin that is unavailable for ARM, a warning will be emitted during agent installation.
47+
48+
Please note that, while including both architectures in a single package is possible, we recommend keeping your ARM and x86 packages cleanly separated.

0 commit comments

Comments
 (0)