Repository navigation
Daemonset instead of sidecar for ECS Clusters #15
Description
I understand the reason to run it as a sidecar in Fargate, but could it be running in a DaemonSet and reporting all the tasks in the node for the ECS clusters?
Not sure if it would be enough to avoid incurring the ECS API rate limiting.
Reacted by Oleg Glushak and maxblaze
Activity
rakyll commentedon Sep 24, 2021
One limitation right now is the metadata server is being able from tasks. I think one of the potential things we can do is to either make this exposition format available from ecs-agent or the metadata server's itself so it doesn't have to be run as a sidecar. Would you be interested in filing an issue at https://github.com/aws/containers-roadmap/issues?