EKS add-ons Advanced Configuration for ADOT (<v0.88.0-eksbuild.1)

IMPORTANT: The following documentation is for ADOT EKS add-on versions less than v0.88.0-eksbuild.1. If you are using a version greater than or equal to v0.88.0-eksbuild.1, then please refer to this updated Add-on Advanced Configuration documentation. Utilize the v0.88.0 Advanced configuration migration guide if you are upgrading from a pre v0.88.0 version.

EKS add-ons provides the ability to configure the installation of ADOT, during installation time. During add-on creation, or add-on updates, configurable values can be used to modify the add-on to your liking. Some examples include modifying resource requests or limits or adding tolerations to the deployed pod.

These configuration values are passed in as a JSON string to a --configuration-values option when creating or updating ADOT using EKS add-ons. you can either pass in a JSON string directly, or you can pass a file path to a JSON file as a parameter, see these docs for more information. For example, to set the cpu resource limit to 200m during add-on creation, the command would look like

Copy
aws eks create-addon \
    --cluster-name <YOUR-EKS-CLUSTER-NAME> \
    --addon-name adot \
    --configuration-values "{\"manager\":{\"resources\":{\"limits\":{\"cpu\":\"200m\"}}}}" \
    --resolve-conflicts=OVERWRITE

Note that, when passing in JSON directly, you must escape special characters, such as double quotes. This is reflected in the example above. Alternatively, you can pass in a file path as an argument to --configuration-values, reducing the need for special formatting. For example, the same command above using a file named configuration-values.json as a file path would look like

Copy
aws eks create-addon \
    --cluster-name <YOUR-EKS-CLUSTER-NAME> \
    --addon-name adot \
    --configuration-values file://configuration-values.json \
    --resolve-conflicts=OVERWRITE

Copy
// configuration-values.json
{
  "manager": {
    "resource": {
      "limits": {
        "cpu": "200m"
      }
    }
  }
}

Each EKS add-on version of ADOT will have it’s own definition of what values are configurable. They are very similar, if not identical, between most add-on versions. To see what configurable values are available for an add-on version, use the command

Copy
aws eks describe-addon-configuration --addon-name adot --addon-version <DESIRED-ADDON-VERSION>

An example list of all configurable values, along with descriptions and examples, for the add-on version v0.66.0-eksbuild.1 can be found below. Additionally, with the addition of configurable values for ADOT using EKS add-ons, it is possible to pass in configuration values to allow an ADOT Collector to be deployed during add-on creation or add-on updates. This will be discussed in an upcoming section.

*Note that in fargate, resource requests and limits must be equal, see this troubleshooting guide for more information.

Previous Topic: Installation

Next topics:

Add-on Advanced Configuration: Collector Deployment (<v0.88.0-eksbuild.1)

Collector Configuration Introduction

• Collector Configuration for Amazon Managed Prometheus

• Collector Configuration for Amazon CloudWatch

• Collector Configuration for AWS X-Ray

Deploy a sample app

Advanced Collector Configuration for Amazon Managed Prometheus