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

Provide guidance regarding resource requests/limits in EKS #416

Open
rapphil opened this issue Nov 15, 2022 · 0 comments
Open

Provide guidance regarding resource requests/limits in EKS #416

rapphil opened this issue Nov 15, 2022 · 0 comments

Comments

@rapphil
Copy link
Contributor

rapphil commented Nov 15, 2022

The defaults for EKS running on EC2 and Fargate are different. If you don't specify resource requests/limits in a pod with EKS for Fargate, the default is to provide 0.25vCPU and 512MB of memory for a node. This might lead the collector to fail to fail to publish metrics in a timelly manner.

What I expect to consider this task done:

  • In the EKS sections of our documentation, point out that specifying the limits for Fargate are a good practice, otherwise the defaults of 0.25vCPU and 512MiB will apply.
  • Add section to help customers understand when the collector is failing to achieve the performance objectives.
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

No branches or pull requests

1 participant