- Newest
- Most votes
- Most comments
When installing the Amazon CloudWatch Observability EKS add-on, there isn't a direct way to specify or override the dcgm-exporter image tag during installation. The add-on versions come with pre-configured components, including the dcgm-exporter image.
You can verify the compatibility of the add-on with your cluster architecture by using the describe-addon-versions command:
aws eks describe-addon-versions --addon-name amazon-cloudwatch-observability --kubernetes-version <your-cluster-version>
In the output, you can check the "architecture" field to see if the add-on version supports both "amd64" and "arm64" architectures. The current version you mentioned (v4.2.1-eksbuild.1) should list both architectures in its compatibility information.
For the specific issue with dcgm-exporter supporting only amd64 in your mixed architecture cluster, you have a few options:
-
You could use node affinity or taints/tolerations to ensure the dcgm-exporter pods only run on amd64 nodes.
-
For a more customized setup, you might need to consider using the CloudWatch agent Helm chart instead of the EKS add-on, which might provide more flexibility for configuration.
-
For submitting a feature request to address this in future add-on releases, you can:
- Open an AWS Support case
- Submit feedback through your AWS account representative
- Post on the AWS re:Post community forums
Unfortunately, there's no direct way to override just the dcgm-exporter image tag while using the EKS add-on installation method.
Sources
Verify Amazon EKS add-on version compatibility with a cluster - Amazon EKS
Quick start with the Amazon CloudWatch Observability EKS add-on - Amazon CloudWatch
Monitor an Amazon EKS cluster with CloudWatch Observability | AWS re:Post
Install the CloudWatch agent with the Amazon CloudWatch Observability EKS add-on or the Helm chart - Amazon CloudWatch
Addons - Eksctl User Guide
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
