Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container Insights EKS Fargate docs are lacking detail #2764

Open
marchchad opened this issue Jul 9, 2024 · 1 comment
Open

Container Insights EKS Fargate docs are lacking detail #2764

marchchad opened this issue Jul 9, 2024 · 1 comment
Labels

Comments

@marchchad
Copy link

marchchad commented Jul 9, 2024

Describe the question
I'm trying to follow this guide for configuring ADOT for EKS Fargate, however I have yet to be successful with getting the adot-collector-0 pod to successfully scrape the prometheus metrics and I've yet to see the CloudWatch Log Group get created.

Steps to reproduce if your question is related to an action
Follow the linked guide as is to stand up a cluster from scratch and I expect that it will not succeed.

What did you expect to see?
The prerequisites for this configuration are lacking in detail. For example, they refer to the AWS docs for creating a cluster using eksctl or the Management Console. The issue with referring to that is those docs have so many branch points on optional configuration that it's unclear which of those optional configurations are actually required to support the deployment of ADOT.

Additionally, the docs say any version of eks k8s above 1.21, however this is incorrect as there is definitely an upper limit to the supported version because 1.30 is not supported. Also the most recent test run of this add-on only covers up to 1.27 for fargate: #2429

If 1.27 is the upper limit for what is supported, that's fine, but it needs to be documented in the actual guides/documentation and not in a closed PR.

Environment
I've attempted to configure this for AWS EKS Fargate 1.29 and 1.30 and neither have succeeded.

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant