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

ECS Fargate detection changes #2047

Closed
jtduffy opened this issue Sep 10, 2024 · 1 comment · Fixed by #2050
Closed

ECS Fargate detection changes #2047

jtduffy opened this issue Sep 10, 2024 · 1 comment · Fixed by #2050
Assignees
Labels
3 Story Point Estimate

Comments

@jtduffy
Copy link
Contributor

jtduffy commented Sep 10, 2024

The updated agent spec details the new requirements for reporting an ECS fargate docker id. Specifically:

  • The ECS fargate endpoint must be checked, even if a docker id was found using cgroups
  • If found, it must reported as a new vendor in the utilization payload (details in the spec)
  • Both the cgroup docker id and ECS fargate docker id will be reported if both are present

The metadata environment variables which specify the endpoints are unchanged, as is the order in which to check them (ie: check the v4 endpoint prior to checking the un-versioned endpoint). The response JSON is also unchanged.

@jtduffy jtduffy added the 3 Story Point Estimate label Sep 10, 2024
@workato-integration
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 Story Point Estimate
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants