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

V1.52.0 stage #2857

Closed
wants to merge 18 commits into from
Closed

V1.52.0 stage #2857

wants to merge 18 commits into from

Conversation

fierlion
Copy link
Member

Summary

1.52.0 release staging

Implementation details

Executed as part of managed release process.

Description for the changelog

1.52.0 release stage

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

CHANGELOG.md Outdated Show resolved Hide resolved
sparrc and others added 18 commits April 28, 2021 18:44
we often receive context.Canceled errors when a container exits during
docker stats collection.

there is a benign race condition where if we process the error first
before processing that the context is "Done", then we will log this
canceled error as a warning message here:
https://github.com/aws/amazon-ecs-agent/blob/5be7aa08bed215a557f48c16d8201ad3db59a9be/agent/stats/container.go#L118-L122

this change ignores these context.Canceled errors so that we don't log
them. This will eliminate log messages that look like this when a
container exits:

level=warn time=2020-12-25T07:51:33Z msg="Error encountered processing metrics stream from docker, this may affect cloudwatch metric accuracy: DockerGoClient: Unable to decode stats for container REDACTED: context canceled" module=container.go
also replace gcr.io ref with a small public.ecr.aws image from ec2
This is to centralize grabbing our instance credential provider into a
single package. Previous to this change we grabbed instance credentials
in separate places for the ecs, ec2, ecr and ec2 metadata clients. With this
change, all of these clients will use the same instance credential
provider.

The reason for this is that if we want to add any non-default instance
credential providers to the credential chain, then we need to make sure
that all AWS clients are instantiated with the same provider.
add it into the instance credentials provider chain
When on-prem config is set:
1. Skip adding capabilities that aren't supported on-prem;
2. Add on prem capability;
3. Report cpu architecture as an attribute, obtained from Go runtime.
@fierlion fierlion added this to the 1.52.0 milestone Apr 28, 2021
@@ -1,5 +1,18 @@
# Changelog

## 1.52.0
* Enhancement: Support for ECS EXTERNAL launch type (ECS Anywhere) [#2849](https://github.com/aws/amazon-ecs-agent/pull/2849)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use - here to unify the format?

@fierlion fierlion closed this Apr 28, 2021
@fierlion fierlion deleted the v1.52.0-stage branch April 28, 2021 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants