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

Define requestedStorage per AppDefinition and not per Operator #82

Open
iyannsch opened this issue Nov 27, 2024 · 0 comments
Open

Define requestedStorage per AppDefinition and not per Operator #82

iyannsch opened this issue Nov 27, 2024 · 0 comments

Comments

@iyannsch
Copy link
Contributor

The amount of allocated storage for persistent workspaces is configurable via operator.requestedStorage to be passed to the K8s PVC resource. Thus, every workspace regardless of its running AppDefinition will have the same amount of storage available.

But does every app have the same requirements in regard to storage?
We don't think so! While CPU, RAM, and even network usage are configurable on a AppDefinition level, the storage isn't.

***Proposal
Add requestedStorage to the parameters of an AppDefinition so that configurations like this become feasible:

requestsStorage: 250M

requestsMemory: 4800M
requestsCpu: 1000m
limitsMemory: 4800M
limitsCpu: "4"
downlinkLimit: 30000
uplinkLimit: 30000
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