Epic: Control internet egress per workspace hour
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Summary
(To be defined) After a given upload limit, we want the workspace to either (1) have significantly reduced internet bandwidth, or (2) pay for the extra consumption.
Context
Currently, we don't control how much GBs a workspace can upload to the internet, which leads to abuse and high infrastructure costs.
Relates to https://github.com/gitpod-io/gitpod/issues/10756 and https://github.com/gitpod-io/gitpod/issues/10651.
Value
- Protect Gitpod from extraordinarily high infrastructure costs
- Reduce abuse opportunities
Acceptance Criteria
- Workspace instances are unable to use more than an average of X GBs per hour
Measurement
N/A
Growth Area
No response
Persona(s)
No response
Hypothesis
No response
In scope
No response
Out of scope
No response
Complexities
No response
Press release
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reading this epic alongside issues #10756 and #10651, then clarify the missing bandwidth threshold and implementation scope. Done would mean workspace instances cannot exceed an agreed average of X GB per hour, but X is not defined here.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100