awslabs / awslabs/eks-node-viewer

fargate stats improvements

Open
#194 0 comments 4 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
1.6k
Forks
147
Avg merge
1h 4m
Merged PRs (30d)
3

Description

Right now the fargate stats are not correct because the provisioned instance is always bigger than the requested resources for the pod.

fargate-ip-10-8-137-244.eu-central-1.compute.internal cpu ████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 10% (1 pods) 0.25vCPU-1GB/$0.0118 Fargate - Ready
memory ███████████████░░░░░░░░░░░░░░░░░░░░ 42%

│ Non-terminated Pods: (1 in total) │
│ Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age │
│ --------- ---- ------------ ---------- --------------- ------------- --- │
│ karpenter karpenter-5fdbd5d978-6jqcn 200m (10%) 200m (10%) 768Mi (42%) 768Mi (42%) 31d

The cpu usage should be something like 80%, the memory usage should be 78%.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Fargate stats shown in the issue and compare the displayed provisioned capacity with the pod's requested CPU and memory. The work is done when the reported CPU and memory percentages are based on the requested pod resources rather than the larger provisioned instance.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.