How can I understand `Nodes` in EKS Fargate?

1
votes

I deployed a EKS cluster and a fargate profile. Then I deployed a few application to this cluster. I can see these fargate instances are launched.

enter image description here

when I click each of this instance, it shows me some information like os, image etc. But it doesn't tell me the CPU and memory. When I look at fargate pricing: https://aws.amazon.com/fargate/pricing/. It is calculated based on CPU and Memory.

I have used ECS and it is very clear that I need to provision CPU/Memory in service/task level. But I can't find anything in EKS.

How do I know how much resources they are consuming?

1
amazon-web-serviceskubernetesamazon-eksaws-fargate
When you use Fargate with EKS, resources are provisioned based on pod's requests and limits. docs.aws.amazon.com/eks/latest/userguide/… – VASャ
@VASャ is correct. With ECS you pick the task size upfront. The way we do this in Kubernetes is by checking the requests in each container of a given pod and we calculate the pod size off of that (see the rule we use in the link VAS provided). – mreferre
One other thing I would add is, don't look at the node size (e.g. by describing the nodes via kubectl). They are unrelated to the actual size of the environment we configured (and that you are paying for). Check the size of the environment via the CapacityProvisioned annotation in the pod. – mreferre

1 Answers

1
votes

With Fargate you don`t have provision, configure or scale virtual machines to run your containers so that they become fundamental compute primitive.

This solution model is called serverless where you are being charged for only the compute resources and storage that are need to execute some piece of your code. It does not mean that there are not server involved in this, it just you don`t need to care about those.

To monitor there those you can use CloudWatch. Below documents describe how this can be achieved:

It is worth to mention that Fargate is just a launch type for ECS (Another one is EC2). Please have a look at the diagram in this document for clear image of how those are connected. The CloudWatch metrics are collected automatically for Fargate. If you are using the AKS with Fargate you can monitor them with usage of metrics-addon or prometheus inside your kubernetes cluster.

Here's an example of monitoring Fargate with Prometheus. Notice that it scrapes the metrics from CloudWatch.