Skip to content
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.

support resource limit trait #462

Open
wonderflow opened this issue Nov 14, 2019 · 3 comments
Open

support resource limit trait #462

wonderflow opened this issue Nov 14, 2019 · 3 comments
Assignees
Labels
Type: Enhancement New feature or request

Comments

@wonderflow
Copy link
Member

Now we have resource minimum in Component definition, the operator may want to define resource limit. So we need resource limit as a Trait.

@wonderflow wonderflow added the Type: Enhancement New feature or request label Nov 14, 2019
@zhxu2
Copy link
Contributor

zhxu2 commented Dec 6, 2019

I can pick this one up and work on it

@wonderflow
Copy link
Member Author

cool!

@zhxu2
Copy link
Contributor

zhxu2 commented Feb 5, 2020

Now we have resource minimum in Component definition, the operator may want to define resource limit. So we need resource limit as a Trait.

I am wondering what's the conclusions we got from multiple oam-spec issues concerning "resource limit" trait. Have we decided to have both requests & limits made required for developers?

From the operator's point of view, it makes little sense to have a "default" config for every other applications.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants