[meta] Tracker for container insight arm64 support

[pingleig]

This is a tracker to direct discussion of existing issues into one place. There is no detailed timeline (yet). Please leave feedback if you are planning to use it or have concern for breaking changes (if any).

Background

EKS Graviton support is GA and cloudwatch-agent already has an arm64 build (not containerized). Fludentd has arm64 dameonset build.

Related Issues

• Arm64 support, including multi-arch amazon/cloudwatch-agent
• EKS: ARM64 support for "Container Insights"
• Added NodeSelector to prevent it from running on windows Nodes We are likely to update label selector because fluentd daemonset does not use multi arch image.

Not related issues

• #104 Raspberry pi we are not creating new arm build

Design

• Provide a multi arch image on dockerhub like xray-dameon
  • Existing manifest should still work in theory i.e. pull amd64 on amd64 host, haven't tested it with dockerhub though.
• Provide new repo/tag that contains arm64 amd64 for people using registry/runtime that does not support multi arch image NOTE: Amazon ECR supports it

TODO

• provide full snippet for workaround
• official arm64 image
• Update related manifest in We recommend users to use fluent-bit which has a multi-arch image, for fluentd users need update the image tag manually since the official daemonset image is x86 only.
  • this repo
  • example
  • doc

Workaround

It is possible to build arm image by yourself from official arm64 packages. Running docker buildx or creating an ARM instance on ec2 as a builder box should both work.

You need to modify example manifests to make sure you are

• Using arm64 version of fluentd image
• Using node selector arch=arm64 if your eks cluster is mixing amd64 and arm64 node groups. Even if you build a mult-arch image for cloudwatch-agent, fluentd is still specifying arch using image tag.

[pingleig]

The arm64 image is out on dockerhub and public ECR

[pingleig]

The public doc is updated (somehow it seems it is out of sync w/ the github repo). If you are using the agent only, there is no need to change anything, the docker image is multi arch so it works out of box. If you use fluentd, you need to update the image tag to match the arch See install fluentd. The recommended approach is using fluent-bit.

Related links

• Amazon CloudWatch Container Insights now available on AWS Graviton2