argoproj / argoproj/argo-workflows

Report estimated resource usages as well as requested resources

Open
#3,106 0 comments 17 reactions 0 assignees View on GitHub
area/controller
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

We currently report how much resource you requested * how long a your pod ran. This indicates the cost of your workflow. We should be able to use the metrics API to estimate how much you actually used.

# Motivation

Cost reduction. See #2972, #3089, #2934 .

# Proposal

See #2579

---

**Message from the maintainers**:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Contributor guide

Open the contributing guide

Research direction

Start by reading the metrics API context and the proposal in issue #2579, along with the related cost-reduction issues #2972, #3089, and #2934. Done means workflow reporting includes estimated actual pod resource usage in addition to requested resources and runtime-based usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
backend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.